UFS raid degraded - help please

[berrick]

Hi all,

Using FreeNAS-9.1.1-RELEASE-x64 (a752d35) on a AMD 64 dual core 5200+ 2GB of ram.

This NAS started out as a test box to see how FreeNAS would perform usingbare min hardware requirements. I have to say it has proven very good thus far.This weekend I was planning on upgrading the hardware and doing away with the UFS raid after backing up data which was added the last few weeks. Unfortunately the NAS unexpectedly rebooted and now the UFS raid is degraded.

Long story short, one of the SATA leads, the end connecting to one of the disks was cracked and it was not connecting properly. This lead has now been replaced. However, I thought as the data on the disk and the disk where functional that after a reboot everything would be back to normal. This isn't the case.

I'm not really sure what I'm doing so could really do with guidance please.

• I don't appear to be seeing errors at boot
• If I issue graid3 status at cli it shows 2 of the 3 disks as active, raid degraded
• If I issue camcontrol devlist at cli all three disks that where part of this array are listed

Do I just add the disk back manually. IF so how? Obviously I want to keep the data in tack so I can back it up.
Kind regards

 

[cyberjock]

Yeah.. I'm one of the guys for ZFS recovery. But for UFS, you'll have to find the UFS wizard. I won't call him out by name, but I'm betting he'll be here at some point...

My advice: Do nothing! ABSOLUTELY NOTHING! Wait for him.

 

[Dusan]

Do I just add the disk back manually. IF so how?

If it didn't pick up the missing device after a reboot the graid3 metadata probably got corrupted on that one disk. To insert the device back into the raid run:
[PANEL]graid3 insert <raid_name> <the_missing_device>[/PANEL]So, if the missing device is /dev/ada2 and your UFS raid volume is UFS_raid you would run "graid3 insert UFS_raid /dev/ada2". The "new" device should start synchronizing immediately. You can check the progress by running "graid3 status". However, as this is not ZFS it will have to synchronize the entire disk including empty space.

 

[cyberjock]

And he answered :D

 

[berrick]

Thank you both for the replies.

I ran the command Dusan suggested and the disk was successfully added to the array. I had a brown trouser moment when I couldn't access the data on it but thankfully it was down to Directory and CIFS services not being started.

As far as the checks I have made go everything is OK, thanks again :)

 

[Babycrusher69]

I just wanted to say thanks to Dusan. This got my Raid3 back going and started showing the status back up immediately in the Volume Status page after running the above command. Thanks guys.