So, my newly setup FreeNAS 9.3 server started becoming unresponsive to the web GUI and ssh login attempts. This was after I'd invested the time setting it up, adding all the users, moving the data across, configuring Crashplan, etc.
When I looked a the local output the error messages were scrolling were "CAM status: CCB request completed with an error" and the email I received was titled 'Critical Alerts' with the following text 'The boot volume state is ONLINE: One or more devices are faulted in response to IO failures.'
Searching the forum showed that the boot USB was failing. There was only one USB boot drive and since this was a new server I hadn't backed up the setup data......
I was forced to cycle the power (after closing all open documents on the clients) as I couldn't get a response from the management interfaces even thought the AFP and SMB shares were still working normally. I was concerned about cycling the power but in my case I didn't loose any data and the volume reported 'No know data errors' on the restart.
What it did to get back up and running was -
Now when I look at System --> Boot --> Status the failing USB drive status is 'Faulted' and I have the option to replace it.
I've order the replacement USB Stick for under $10 and backed up the config database (System --> Advanced --> Backup (located at the bottom of the page))
If you're running 9.3 using only one USB boot drive I would HIGHLY recommend spending $10 on a second and use the instructions at http://doc.freenas.org/9.3/freenas_system.html#mirroring-the-boot-device to install it and then setup the system email account if you haven't already done so.
There may be a better approach than mine but I couldn't find it so if anyone knows of something let me know or if the more experienced of you identify something that's risky in my approach let me know.
Cheers
When I looked a the local output the error messages were scrolling were "CAM status: CCB request completed with an error" and the email I received was titled 'Critical Alerts' with the following text 'The boot volume state is ONLINE: One or more devices are faulted in response to IO failures.'
Searching the forum showed that the boot USB was failing. There was only one USB boot drive and since this was a new server I hadn't backed up the setup data......
I was forced to cycle the power (after closing all open documents on the clients) as I couldn't get a response from the management interfaces even thought the AFP and SMB shares were still working normally. I was concerned about cycling the power but in my case I didn't loose any data and the volume reported 'No know data errors' on the restart.
What it did to get back up and running was -
- Leave the failing drive in the server
- Insert a second blank USB drive into the server and the installation USB.
- Start the installation process and pick both the new and failing USB drives for the installation.
- Choose 'Upgrade Install' .
- Set the root password and continue the normal installation.
Now when I look at System --> Boot --> Status the failing USB drive status is 'Faulted' and I have the option to replace it.
I've order the replacement USB Stick for under $10 and backed up the config database (System --> Advanced --> Backup (located at the bottom of the page))
If you're running 9.3 using only one USB boot drive I would HIGHLY recommend spending $10 on a second and use the instructions at http://doc.freenas.org/9.3/freenas_system.html#mirroring-the-boot-device to install it and then setup the system email account if you haven't already done so.
There may be a better approach than mine but I couldn't find it so if anyone knows of something let me know or if the more experienced of you identify something that's risky in my approach let me know.
Cheers