OpenSuse suddenly stops booting correctly
1 Attachment(s)
Out of nowhere, when choosing Slackware from grub, I get opensuse, but it freezes once it hits the GUI, and when choosing opensuse I get the following-- shown in screenshot. After a while of messing around and unplugging and replugging things in and renaming sdf to sdg and visa versa, Slackware got fixed but Opensuse still gives me what is shown in the screenshot, and, when choosing opensuse from grub, it seems to freeze, so I hit the right arrow and I get what you see in the screenshot, and I cant even type to choose yes or no. If the only answer is formatting and then reinstalling, please tell me the possibilities that could have caused this, so I don't do it again.
|
please a little explination on the bootloader.
Grub Legacy, or Grub 2? Is this chainloading or not? How did you install grub? Was it while installing Opensuse? Where is the boot loader installed too; the mbr or the root of a partition? As a quick guess, (I'm assuming it's grub2, installed with Opensuse) have you tried booting Slackware, mounting and chrooting into Opensuse and running the command, Code:
grub2-mkconfig -o /boot/grub2/grub.cfg |
It's grub 2, installed with ubuntu, slackware getting messed up was just a side effect. What do you mean by chainloading, and it is installed to the mbr of the fist disk in my bios. There are other installations as well, and I can list them if needed.
|
An example of a chainload entry for Grub2 below, booting sda12 partition:
Quote:
|
Quote:
Do you even still have Ubuntu installed? Chainloading is when your bootloader boots up and instead of proceeding to boot up an os, it boots up another bootloader which then boots up the operating system. It sounds dumb but if you've a lot of operating systems on your computer, it can really help with maintenance. I chainload. When my laptop boots up, it boots up Grub legacy, which displays a choice of five operating systems. It boots up Debian by default after 3 seconds. Instead of booting up Debian though, it actually boots up Grub2 which is installed onto the root of my Debian partition, which then after 2 seconds, boots up my Debian Wheezy operating system. If i don't want to boot Debian, and want to boot up my Slackware partition instead: when the computer boots up Grub Legacy, if i select Slackware, it boots up lilo (The bootloader installed by default on Slackware) which then boots Slackware. This setup is convenient because it means i never have to worry about messing up a bootloader on one of my operating systems and not being able to boot; because if that were to ever happen, everything is contained to it's own partition, and the other operating systems aren't dependent on each other. (Sorry about that horribly long sentence) |
Then, I do not chainload, and I have run sudo update-grub several times, and I have even tried using rescueatux previously, but could I possibly use parted magic to fix this?
|
Can someone tell me how to set up chainloading, as it may help. I have grub2 on the MBR of a hard disk.
|
If you are talking about chainloading from one grub to another, have a look at this.
http://richardfearn.wordpress.com/20...ub-to-another/ |
Quote:
Just out of curiosity, are you sure that your Opensuse partition isn't full? |
If you are booting with Grub2 in the mbr, you can just edit the grub.cfg file (that's the one that says do not edit this file at the top) by placing an entry similar to the example I posted above. You will need to change the drive/partition number to fit your specific system bearing in mind that Grub2 counts physical hard drives from zero and partitions from one. After making the change, do not run update-grub but reboot to test it. If it works, you will need to put that entry in the Ubuntu /etc/grub.d/40_custom file. Just copy it there.
If that doesn't work, you should google 'bootinfoscript' and go its site, read the instructions, download and run it and post the output, a results.txt file with a lot of information on drives/partitions, boot files and uuids. |
Back to my original question, can I fix this?
|
13stein.j, post the whole error message. It says 'trying to manually resume', but we can't tell why it's trying to, and it may be a valuable clue to helping you. Also post these things; your /etc/fstab file from your Opensuse partition and the output of these commands:
(Do these commands from within Ubuntu) Code:
blkid /dev/sda2 Code:
cat /etc/boot/grub.cfg | grep UUID |
Quote:
|
Quote:
Code:
/dev/sda2 swap swap defaults 0 0 Quote:
Code:
root@13stein:~# blkid /dev/sde1 Quote:
Code:
linux /boot/vmlinuz-3.9.3-030903-generic root=UUID=5c5441f0-8678-4790-969c-d2efbb88573c ro quiet splash $vt_handoff |
I forgot that Opensuse uses the /dev/disk/by-id method of identifying partitions, before when i was asking for info, but have just remembered when i checked my Opensuse partitions fstab. Your fstab is set up very basically instead though. I'm not very familiar with the /dev/disk-id method, so try making a new fstab file using UUID instead.
mount your Opensuse partiton and change the name of the fstab file (assuming it's mounted in mnt); Code:
sudo mv /mnt/etc/fstab /mnt/etc/fstab.org Code:
# <file system> <mount point> <type> <options> <dump> <pass> Code:
sudo umount /dev/sda2 |
All times are GMT -5. The time now is 04:40 PM. |