New build, ran into issue

Status
Not open for further replies.

berlin

Dabbler
Joined
Jul 1, 2014
Messages
11
Hi All,

First off, thanks for the great site and for FreeNAS itself. Here is my build for a home NAS:
  • Supermicro X10SLM-F-O motherboard
  • Intel Xeon E3-1230 v3 processor
  • 16 GB (8x2) Crucial DDR3-1600 ECC RAM
  • Seasonic 450W Power Supply
  • 4 Seagate NAS HDD 3 TB
  • 2 Seagate Barracuda 3TB (already had these)
  • Team C12G 8GB USB 2.0 Flash Drive
  • Cyberpower CP1000AVRLCD UPS connected via USB
I am using version 9.2.1.6-RC2 and running 6 HDD in a RaidZ2. I had the plugin for Plex setup and running, but hadn't done anything with it yet. I'm still very much in a test and play with FreeNAS mode.

So here is the problem I ran into. I created multiple datasets. I had setup a CIFS share for one of them and had begun copying a ton of files over from my Mac. I had also started a copy from a Windows laptop as well. While this was going on, I was creating CIFS shares for my other datasets, when all of a sudden, the system reboots.

I'm still learning, so I apologize as I probably don't have everything needed, but here is what I found in /var/log/messages before the reboot

Code:
Jun 30 22:35:53 freenas notifier: Reloading smbd.                                                                                 
Jun 30 22:35:53 freenas notifier: Reloading winbindd.                                                                             
Jun 30 22:36:05 freenas kernel: (da0:umass-sim0:0:0:0): WRITE(10). CDB: 2a 00 00 05 24 0f 00 00 08 00                             
Jun 30 22:36:05 freenas kernel: (da0:umass-sim0:0:0:0): CAM status: CCB request completed with an error                           
Jun 30 22:36:05 freenas kernel: (da0:umass-sim0:0:0:0): Retrying command                                                           
Jun 30 22:36:11 freenas kernel: (da0:umass-sim0:0:0:0): WRITE(10). CDB: 2a 00 00 05 24 0f 00 00 08 00                             
Jun 30 22:36:11 freenas kernel: (da0:umass-sim0:0:0:0): CAM status: CCB request completed with an error                           
Jun 30 22:36:11 freenas kernel: (da0:umass-sim0:0:0:0): Retrying command                                                           
Jun 30 22:36:16 freenas kernel: (da0:umass-sim0:0:0:0): WRITE(10). CDB: 2a 00 00 05 24 0f 00 00 08 00                             
Jun 30 22:36:16 freenas kernel: (da0:umass-sim0:0:0:0): CAM status: CCB request completed with an error                           
Jun 30 22:36:16 freenas kernel: (da0:umass-sim0:0:0:0): Retrying command                                                           
Jun 30 22:36:22 freenas kernel: (da0:umass-sim0:0:0:0): WRITE(10). CDB: 2a 00 00 05 24 0f 00 00 08 00                             
Jun 30 22:36:22 freenas kernel: (da0:umass-sim0:0:0:0): CAM status: CCB request completed with an error                           
Jun 30 22:36:22 freenas kernel: (da0:umass-sim0:0:0:0): Retrying command                                                           
Jun 30 22:36:00 freenas root: Unknown USB device: vendor 0x0764 product 0x0501 bus uhub2                                           
Jun 30 22:36:27 freenas kernel: (da0:umass-sim0:0:0:0): WRITE(10). CDB: 2a 00 00 05 24 0f 00 00 08 00                             
Jun 30 22:36:27 freenas kernel: (da0:umass-sim0:0:0:0): CAM status: CCB request completed with an error
Jun 30 22:36:27 freenas kernel: g_vfs_done():ufs/FreeNASs1a[WRITE(offset=172470272, length=4096)]error = 5                          
Jun 30 22:36:27 freenas kernel: g_vfs_done():ufs/FreeNASs1a[WRITE(offset=172507136, length=4096)]error = 5                          
Jun 30 22:36:27 freenas kernel: g_vfs_done():ufs/FreeNASs1a[WRITE(offset=172511232, length=4096)]error = 5


Now, when I first looked at this, I thought maybe the issue was that I didn't realize it was restarting smbd when I setup those other shares. I guess I should have figured that and that copying files while doing that was probably not the best idea. But I look at this and it appears the failure is really to write to the flash drive?

When the system came back up, I tried to access my share again from the Mac and it failed. When I went into the FreeNAS shell, I typed smbd and voila, the share was accessible again. Also, ran a scrub and found no issues with the pool and hard drives.

Anyway, I haven't had it happen since, I guess I 'm just looking for some advice to test or fix. Maybe just replace that flash drive with something else? Anyway to give the flash drive a good test? Don't create shares while copying files to another share?

Thanks!
 
D

dlavigne

Guest
It actually looks like a problem with the USB stick. What type and size? It might be worth saving a copy of your current config and burning the OS image to a different stick.
 

berlin

Dabbler
Joined
Jul 1, 2014
Messages
11
Thanks for the response. My current USB flash drive is this:
  • Team C12G 8GB USB 2.0 Flash Drive
I will look at buying a Sandisk or Kingston, something a little more common. The problem hasn't occurred since, but I'm sure it will again if it happened once. Thanks again!
 

Ericloewe

Server Wrangler
Moderator
Joined
Feb 15, 2014
Messages
20,194
Thanks for the response. My current USB flash drive is this:
  • Team C12G 8GB USB 2.0 Flash Drive
I will look at buying a Sandisk or Kingston, something a little more common. The problem hasn't occurred since, but I'm sure it will again if it happened once. Thanks again!

Avoid Kingston, they've been pulling shady moves lately.
 

berlin

Dabbler
Joined
Jul 1, 2014
Messages
11

robirt55

Cadet
Joined
Jan 8, 2014
Messages
8
Hello All,

I know this is a pretty old form but I had an issue today where the system was giving me a very similar issue. I cloned the flash drive to a new flash drive and the system came right up.
 

Sakuru

Guru
Joined
Nov 20, 2015
Messages
527
Status
Not open for further replies.
Top