[opensuse] My first 'Update' 10.3-11.0 - Won't boot - damn disk-by-id problem - help?
List, After only doing fresh installs since 8.0, I tried my first 'Update' on a 10.3 box going to 11.0. Looks like the update succeeded, but it left me unable to boot. Grub is installed on the right partition, but after booting 11.0, it gets to the place where it is: waiting on required device /dev/long-string-of-id-stuff-part2 and then bombs. '/' is /dev/sda2, '/home' is /dev/sda3 with swap on sda1. I have tried using the rescue disk and: mount /dev/md1 /mnt mount /dev/md0 /mnt/boot mount /dev/md2 /mnt/home mount -o bind /dev /mnt/dev mount -o bind /proc /mnt/proc mount -o bind /sys /mnt/sys cd /mnt chroot /mnt use Yast boot loader config and save, then it bombs again at the same place, I have also tried editing the grub entry at the first boot screen and changing the disk-by-id string to /dev/sda2. Boot dies at the same place: waiting on required device /dev/sda2 So I'm sort of stumped. I recall a rash of problems with disk-by-id, but I didn't save the solution. I'm committed to make this update work. Can anyone share the fix with me? Thanks! -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
David C. Rankin wrote: bad example before, should be: mount /dev/sda2 /mnt mount /dev/sda3 /mnt/home mount -o bind /dev /mnt/dev mount -o bind /proc /mnt/proc mount -o bind /sys /mnt/sys cd /mnt chroot /mnt -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
David C. Rankin wrote:
David C. Rankin wrote:
bad example before, should be:
mount /dev/sda2 /mnt mount /dev/sda3 /mnt/home mount -o bind /dev /mnt/dev mount -o bind /proc /mnt/proc mount -o bind /sys /mnt/sys cd /mnt chroot /mnt
The boot issue may become moot. I am updating the install right now and it looks like it is removing 1/2 my system. We may be looking at a format and reinstall :-( Is this normal on the first update after a 'Update' between versions? -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 2009/01/21 18:27 (GMT-0600) David C. Rankin composed:
Is this normal on the first update after a 'Update' between versions?
Inability to boot after install is rather common in recent distros' recent versions. It seems worse with RAID. I created two new RAID1 systems recently, resulting in filing https://bugzilla.novell.com/show_bug.cgi?id=463033 . Both of those systems have no problem booting, because I first fully partitioned prior to beginning installations, and put Grub on the first disk partitions non-RAID, and do not mount the real boot partition on any installed system's /boot. I maintain menu.lst on that partition manually. http://fm.no-ip.com/tmp/Linux/f965-02.txt is the partitioning I used on both (made prior to completion of the first install). I installed 11.0 from the boxed DVD on both. On one I also installed 11.1 from HTTP. The other is waiting till my 11.1 DVD box shows up. I use labels on all partitions, mount all important partitions by LABEL, and use root=LABEL= in Grub. -- "Train a child in the way he should go, and when he is old he will not turn from it." Proverbs 22:6 NIV Team OS/2 ** Reg. Linux User #211409 Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Felix Miata wrote:
On 2009/01/21 18:27 (GMT-0600) David C. Rankin composed:
Is this normal on the first update after a 'Update' between versions?
Inability to boot after install is rather common in recent distros' recent versions. It seems worse with RAID. I created two new RAID1 systems recently, resulting in filing https://bugzilla.novell.com/show_bug.cgi?id=463033 .
Both of those systems have no problem booting, because I first fully partitioned prior to beginning installations, and put Grub on the first disk partitions non-RAID, and do not mount the real boot partition on any installed system's /boot. I maintain menu.lst on that partition manually. http://fm.no-ip.com/tmp/Linux/f965-02.txt is the partitioning I used on both (made prior to completion of the first install). I installed 11.0 from the boxed DVD on both. On one I also installed 11.1 from HTTP. The other is waiting till my 11.1 DVD box shows up. I use labels on all partitions, mount all important partitions by LABEL, and use root=LABEL= in Grub.
Other than booting, things were going fine until the first update where after update removed zypper and went to install the new kernel and kernel-source a post install script bombed cratering my system. Screw this update business! mount -o loop -t iso9660 /home/samba/computer/linux/openSuSE/iso/suse11.0/openSUSE-11.0-DVD-i386.iso /usr/local/inst/suse110i386/ rcnfsserver start exportfs (confirmed exported) Throw in the DVD and F4 choose nfs and reformat /dev/sda2 I humbly remain a man with 0 successful update... :-( -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
David C. Rankin wrote:
Screw this update business!
mount -o loop -t iso9660 /home/samba/computer/linux/openSuSE/iso/suse11.0/openSUSE-11.0-DVD-i386.iso /usr/local/inst/suse110i386/
rcnfsserver start
exportfs (confirmed exported)
Throw in the DVD and F4 choose nfs and reformat /dev/sda2
I humbly remain a man with 0 successful update... :-(
nfs install time w/update and atheros wireless configuration -- A whole lot less time than I spent jacking with an 'update' -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
David C. Rankin wrote:
Is this normal on the first update after a 'Update' between versions?
Well, at least I did the same (update a long-used 10.3 to 11.0 using the update mechanism of the install DVD) and it went amazingly smooth. Some small issues because some methods I had used to manually fine tune my system had changed, but that was expected (sort of). Doesn't help you much, I know. Was just for the record... Pit -- Dr. Peter "Pit" Suetterlin http://www.astro.su.se/~pit Institute for Solar Physics Tel.: +34 922 405 590 (Spain) P.Suetterlin@royac.iac.es +46 8 5537 8507 (Sweden) Peter.Suetterlin@astro.su.se -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wednesday January 21 2009, David C. Rankin wrote:
List,
After only doing fresh installs since 8.0, I tried my first 'Update' on a 10.3 box going to 11.0. Looks like the update succeeded, but it left me unable to boot.
Grub is installed on the right partition, but after booting 11.0, it gets to the place where it is:
waiting on required device /dev/long-string-of-id-stuff-part2
and then bombs. '/' is /dev/sda2, '/home' is /dev/sda3 with swap on sda1.
I experienced something very much like this when I installed a clean 11.1 using partitions entirely separate from those of the 10.0 installation. And while the 11.1 would boot fine, the 10.0 boot entry it put in the boot menu failed in the same way you describe. The problem has to do with a discrepancy between the way the old system assigned drives to /dev/sda, /dev/sdb, /dev/sdc, etc. I managed, by using the rescue boot, to modify the menu.lst file of the older installation (10.0, in my case) into a state in which it would boot (which took a few tries, by the way). But I have to admit it was half staring at the correspondence between the /dev/sdX names in the two systems and what I recognized by partition complement and disk sizes to be my various hard drives (four in all). What you have to think about is that the menu.lst of all the systems presented in the boot menu (not, obviously, the DVD one, but rather the local hard-drive one) is interpreted by the GRUB of the new system (the one whose boot loader is in control when you make menu selections before initiating a boot process) and its device assignment, not those of the old system. So I can't give you an algorithm or analytic means to resolve your impasse, only that it can be accomplished by "realigning" the device designations used in the old system's menu.lst file.
...
-- David C. Rankin
Randall Schulz -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wednesday January 21 2009, Randall R Schulz wrote:
...
I managed, by using the rescue boot, to modify the menu.lst file of the older installation (10.0, in my case) into a state in which it would boot (which took a few tries, by the way). But I have to admit it was half staring at the correspondence between the /dev/sdX names in the two systems and what I recognized by partition complement and disk sizes to be my various hard drives (four in all).
D'Oh! Stupid run-on sentences... The other half was sheer trial and error. RRS -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (4)
-
David C. Rankin -
Felix Miata -
Pit Suetterlin -
Randall R Schulz