Missing Hard Drive

[MCC]

Hello,

I have Freenas 9.2.0 with 2 1TB hard drives in Raid 1.
This is a UFS volume.

Yesterday I got an email saying my Volume is degraded, but when I went to check freenas I saw that only ada1 which is my stand-by hard drive and ada2 which is one half of my raid. ada0 is not showing up in the view disks, if ada0 has failed how do i replace the hard drive if there is no button that will let me swap ada0 to ada1?

Also the Volume status is empty, as has no information at all.


Thanks

 

[SweetAndLow]

With ufs you are going to have to rebuild using the features of your raid card. I'm not sure how to do that since you didn't provide any information on your system.

 

[MCC]

Here is the specs on my system, I should say that when the Raid 1 configuration was set up using FreeNAS 8.0.4.

Computer Specs:
Dell GX280
Intel Pentium 4 2.8 GHz
RAM 4 GB DDR2
SAMSUNG CD-ROM SC-148A B403 is IDE
40 GB Western Digital SATA Hard Drive <- FreeNAS 9.2.0 installed; ada3
Fasttrak TX4310 PCI Raid Card
- 2 Seagate 1TB SATA hard drives in Raid 1(same model number); ada0 and ada2

 

[pschatz100]

Your system doesn't meet the specs for FreeNAS 9. Furthermore, FreeNAS 9.3 doesn't support UFS. If you want to stay with FreeNAS, it is time for you to upgrade your hardware. If you can get at your data in the degraded array, I'd back it up and build a new system. If you want to stay on this hardware, you should look into another system.

Good Luck.

 

[Ericloewe]

Well, technically it's the bare minimum for UFS.

If it's hardware RAID or fake RAID, rebuild it there.
If it's UFS voodoo, follow the manual's instructions on how to replace disks.

 

[MCC]

The manual doesn't help, the part on how to replace a drive doesn't apply to my situation.

If I go to Storage


View Disk

You can see that ada1 (spare) and ada2 but ada0 is missing and there is no replace button.

Volume Status

Volume Status is blank.

So how do I replace the drive?

 

[Ericloewe]

Well, I'm out of suggestions. UFS knowledge is in short supply around here...

It could be a GUI bug, but don't expect any fixes, now that UFS has been dumped.
Or it could be something else entirely.