LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Newbie (https://www.linuxquestions.org/questions/linux-newbie-8/)
-   -   Error after rebooting (https://www.linuxquestions.org/questions/linux-newbie-8/error-after-rebooting-4175519458/)

snowkitty 09-19-2014 04:30 PM

Error after rebooting
 
http://i.imgur.com/8r8R89jh.jpg

The above link is the exact error and what I'm getting after having rebooted. I haven't changed any hardware at all. The root, including grub, is installed onto a hardware pci-e raid controller card, so hardware-wise, for me to get that message, everything is working. I really have no idea what to do here. From this screen, input fr om neither of my keyboards is working, and I haven't changed anything to modify bootup (that I'm aware of).

Any help would be great because I have no clue where to begin.

suicidaleggroll 09-19-2014 04:40 PM

Does the BIOS still see the drive? If you boot a live CD/USB can you mount the drive?
Did you perform a system/kernel update and maybe you need to recompile the raid card's kernel module?

snowkitty 09-19-2014 04:58 PM

Well.. BIOS has to see it, if it's being booted to. And yes, I can access the RAID drive from a live enviro. The thing is /dev/sda1 for my root, but I always see errors from grub (installed on the raid) related to being unable to to find the raid device by UUID. I actually have to turn off all my other drives in order to get past that problem with grub, but now the error is occuring when trying to boot into the system, which means that it is loading off the raid and nothing is wrong with my raid.

suicidaleggroll 09-19-2014 05:03 PM

Maybe the UUID has changed? That kind of defeats the purpose of using UUID, but it might explain your problems. You should be able to use blkid from a live CD or from the recovery shell to see what it is, and change /etc/fstab if necessary. If the UUID is inconsistent you could use a label instead.

snowkitty 09-19-2014 06:15 PM

fstab is usig /dev/sda1 though

snowkitty 09-20-2014 07:48 AM

Issue was resolved now by changing kernel.


All times are GMT -5. The time now is 02:04 PM.