Amahi Forums

I recently had a major power failure and I believe one of my drives packed it in. That's OK since I use greyhole and I have 5 drives so I'm not worried about loss of files. However, my Amahi HDA will not boot back up.

I had imagined that in the event of a disk failure the system would reboot, but indicate a drive failure. What is happening (I believe) is Fedora is stopping during the boot process when checking disks. I only believe this since my HDA is truly headless. It has only a PCIe 4x slot and no onboard video so I created the system on another computer, transferred the HD into the server and have been running for almost a year. Now, all I know is it fails to boot. When I take the OS HD out and put it back into a regular computer, Fedora reports failing fsk check and that I can enter my root password to get to a recover console. It lists that it can not find the UUID of all my drives referred to in my fstab. I can only imagine that is what is going on when the OS is back in the server box and cannot boot the one failed sata drive.

Should I edit my fstab in that console to not look for the offending failed sata drive? Thoughts? Thanks.

So my journey continues. I took the OS drive out and put it in another case. Then booted up. It stopped during boot up ("An error occured during the file system check"). It let me enter my root password for maintenance. However, it would not let me edit my fstab since it was in read only. I then searched and found this command "mount -o remount,rw /" After that I edited my fstab to read:

#Added for the eSata case
#Top Drive - Currently Seagate 2TB
UUID=bb1890a0-fe80-4d42-8bfa-5f11bc0b7872 /var/hda/files/drives/drive4 ext4 defaults 1 2
#Second Drive - Currently Seagate 2TB
UUID=2b06fb21-88c7-4f6a-8212-baafaad3bbb3 /var/hda/files/drives/drive3 ext4 defaults 1 2
#Third Drive from the top - Currently a WD 500GB
UUID=5b7a813b-0843-4178-9956-715ae3f1a3cc /var/hda/files/drives/drive5 ext4 defaults 1 2
#Fourth Drive from the top - Currently a WD 500GB
#Edited due to possible drive failure
#UUID=fd2322d6-2962-4e8b-9f6a-3743885acfed /var/hda/files/drives/drive6 ext4 defaults 1 2

Now my HDA boots up! But I am unclear what to do next. How do I let Greyhole know that last drive is gone for good? Any other checks? Tweaks? Commands I should run on the box now that it is back up? Thanks.