March 15, 201016 yr So I was having problems with unmenu and the /boot drive errors here. http://lime-technology.com/forum/index.php?topic=5568.60 I tried to do a powerdown and the system locked on me. When I rebooted, I see to have "lost" 2 of my drives? Here is the current output: root@Serenity:~# df Filesystem 1K-blocks Used Available Use% Mounted on /dev/sda1 1957600 69728 1887872 4% /boot /dev/md3 1953454928 539574484 1413880444 28% /mnt/disk3 /dev/md1 1953454928 32840 1953422088 1% /mnt/disk1 root@Serenity:~# It says that disk2 and disk4 are still mounting and it has been "starting" for quite some time now. What do I do? Do I wait until it finishes rebuilding parity and starting? ETA: Looks like disk2 finally came up, I still don't see disk4 yet/
March 15, 201016 yr So I was having problems with unmenu and the /boot drive errors here. http://lime-technology.com/forum/index.php?topic=5568.60 I tried to do a powerdown and the system locked on me. When I rebooted, I see to have "lost" 2 of my drives? Here is the current output: root@Serenity:~# df Filesystem 1K-blocks Used Available Use% Mounted on /dev/sda1 1957600 69728 1887872 4% /boot /dev/md3 1953454928 539574484 1413880444 28% /mnt/disk3 /dev/md1 1953454928 32840 1953422088 1% /mnt/disk1 root@Serenity:~# It says that disk2 and disk4 are still mounting and it has been "starting" for quite some time now. What do I do? Do I wait until it finishes rebuilding parity and starting? ETA: Looks like disk2 finally came up, I still don't see disk4 yet/ Yes... you wait ... and DO NOT press the format button if you see it... and DO NOT press "Restore" Because the clean shutdown could not be recorded, it could take 5 or minutes for the drives to get mounted. And then you are faced with a full parity check. I hope you captured a syslog for analysis before the powerdown. regardless, if the array does not start you'll want to post a current syslog too. Joe L.
March 15, 201016 yr Author Ok, I'll wait for it to finish then. I see all of the drives now including the /boot drive. I didn't realize it could be up to 5-6 minutes before it showed. Scared the heck out of me. I guess I'll wait until tomorrow then since it is rebuilding right now. I don't think the syslog was saved as the last one I see doesn't have the errors I posted about the /boot being MIA .
March 15, 201016 yr Ok, I'll wait for it to finish then. I see all of the drives now including the /boot drive. I didn't realize it could be up to 5-6 minutes before it showed. Scared the heck out of me. I guess I'll wait until tomorrow then since it is rebuilding right now. I don't think the syslog was saved as the last one I see doesn't have the errors I posted about the /boot being MIA . Since /boot was none-existent, the syslog could not be saved to it by the powerdown command. I did suggest you grab a copy before you reboot. I guess you did not care to figure out what led to /boot being missing. Too late now. Joe L.
March 15, 201016 yr Author Ok, I'll wait for it to finish then. I see all of the drives now including the /boot drive. I didn't realize it could be up to 5-6 minutes before it showed. Scared the heck out of me. I guess I'll wait until tomorrow then since it is rebuilding right now. I don't think the syslog was saved as the last one I see doesn't have the errors I posted about the /boot being MIA . Since /boot was none-existent, the syslog could not be saved to it by the powerdown command. I did suggest you grab a copy before you reboot. I guess you did not care to figure out what led to /boot being missing. Too late now. Joe L. I did care, but I didn't realize it wouldn't save a copy .
March 15, 201016 yr Author The array rebuilt fine and my /boot drive is still there. I assume the only thing I can do is monitor and if it happens again, grab the syslog immediately?
Archived
This topic is now archived and is closed to further replies.