Bug 758570

I dug around a bit for chroot, and I came across the --bind stuff, 

so in the 12.1/x86 dvd, i booted rescue, then i first mounted

mount /dev/sda5 /mnt  (my /, first parititon in extended)
then i 

mount --bind /dev /mnt/dev

(at a later point mkinitrd complained with some perl bootloader module script or so could access or find /sys, so i did --bind for /sys as well

mount --bind /sys /mnt/sys

then

mount /dev/sda2 /mnt/boot     (my /boot) 
mount /dev/sda6 /mnt/var
mount /dev/sda7 /mnt/opt


than i did

chroot /mnt

then

mount /proc


according to some blog:
http://nwrickert2.wordpress.com/2011/10/24/rescuing-susie/


anyways, so only with the additional --bind /sys did mkinitrd continue a bit further, but at the very end I am getting very familiar perl-bootloader .... grub grubdev2unixdev or similar errors... then my /dev/disk/by-id/ata-SAMSUNG_xxxxxxx...... harddiskpathname and an additional "with 2" after that....

five times this error line. always "with 2"... 

odd thing is, that the dev-disk-by-id-ata-samsung.... stuff doesnt contain the   "-part1"... or "-partX" at the end at all. all these lines only have the main disk name without mentioning any partition.


I already reported some serious bug about perlbootloader module and also with this grubdev2unixdev stuff some weeks back, but not much has happened, that bug hosed my whole system right from the start when i actually made the switch to opensuse 12.1 in the first place.....


sigh :(((( what now? what on earth is wrong here. HALP!

the mkinitrd part goes very far, right to features and bootsplash with two resolutions displaying and then giving those five times the perl-boot-loader error with no parititon found in that line as well...

inside the chroot i could run yast2 bootloader and i deleted all entries there and made him propose new configuration.


that one was defective as well, as it selected root=tmpfs for both standard and failsafe entries next to the floppy and the memtest.

so i swichted to root=/dev/disk/by-id/ata-SAMSUNG_____whatever-part5 .... 

here and now this darn system boots up again using the updated kernel 3.1.10

sigh...... this whole boot process, bootloader installation, boot dependability, updating kernel packages initrd, bootloader areas and whatever, needs to be made MUCH MUCH MUCH more robust and dependable.


please suse folks and fellow participants. this is really a huge pain :(((

thanks in advance.

this is my other bug about serious perl-bootloader troubles
https://bugzilla.novell.com/show_bug.cgi?id=748988

yay, or better NAY.... 

I just zypper ref zypper up-ed my other test system with 12.2 milestone3 x86-64 installed a few days ago via iso/usb-key.

I added the oss/nonoss/debug repos from factory to this system, did a zypper ref, and zypper up.

it installed 1100+ packages. it also installed a kernel-desktop package.

the machine "rebooted". NO. actually not. it sits the same way at "GRUB " and the blinking cursor as described in this bug here with the production machine on 12.1/x86.


there is something seriously messed up with the kernel updates, grub and bootloaders.


the 12.2/milestone3 -> factory machine is the one from this bug:
https://bugzilla.novell.com/show_bug.cgi?id=758499

so this machine has very simple default proposed partition layout. i booted the milestone3 usb-key/iso and it offered me to partition the single sata harddisk existing in this machine as 


/swap
/
/home

all with ext4 i think is the default proposal. nothing else.
no other operating systems, no dualboot, no fancy stuff, no nothing. linux testing machine. one hard disk. very simple.


so the bootloaders, scripts, grub and kernel-package updates even mess up this very simple partition layout so that grub doesnt do anything at all any more and refuses to boot the kernel-package upgraded system.


:(((

sorry I dont have a usable rescue system available right now, as I just found out in 

https://bugzilla.novell.com/show_bug.cgi?id=759074


so I cannot check this 12.2/milestone3/x86-64 testing system at all any more what is wrong with it or provide logs from it what it did to the kernel/bootloader/grub  parts that caused the mess.

Created attachment 488035 [details]
various configfiles and infos about the 12.2/m3/x86-64 box

various configfiles and infos about the 12.2/m3/x86-64 box

this machine is also hanging at "GRUB " and doing nothing any more after vanilly milestone3 installation and adding once the oss/nonoss/debug factory repositories and zypper ref zypper dup.

kernel package amongst many others (1158 patches total I think) get installed, machine needs reboot. then never comes back alive again. hangs with "GRUB " and blinking cursor....

Created attachment 488036 [details]
whole /var/log/ directory from the 12.2/m3/x86-64 broken machine

please dig through the /var/log content attached here as there might be or hopefully should be the hint what goes wrong with the kernel update packages recently.

this is from 12.2/m3, but I started this bug originally on a normally working 12.1/x86, and the kernel update from earlier this week or end of last week killed my machine it probably the very same ways as this milestone3 machine here.

they are/were both hanging at the "GRUB " stage..... although 12.2/m3 is GRUB2 and 12.1/x86 is older GRUB1 I guess.....


----

this machine is also hanging at "GRUB " and doing nothing any more after vanilly milestone3 installation and adding once the oss/nonoss/debug factory repositories and zypper ref zypper dup.

kernel package amongst many others (1158 patches total I think) get installed, machine needs reboot. then never comes back alive again. hangs with "GRUB " and blinking cursor....

ok a small update for 12.2/m3 (factory)

i was able to repro this bug. I reinstalled the milestone3/x64 from the usbkey.

then i added a single repo: factory-oss

zypper ref

then i updated only the kernel-desktop .rpm package first. rebooted. system came back fine.

then i did another zypper ref and zypper up finally.

it installed 11xx packages alltogether and tried to reboot.

now the machine hangs at "GRUB " cursor blinking....


its not the kernel-desktop rpm update that kills the machine, it must be some of the other relevant packagages, related to grub, bootloader or whatever there is still involved.

please do look into this.

once again: machine has simple one sata hdd. milestone3 proposes

swap
/ (20gigs)
/home (all the rest)

/ and /home are ext4.

thats all.

HI,could you please help to have a look this?Feel free to reassign it.Thank you very much.;)

some other opensuse tester also reported a milestone4 grub stalling bug...

https://bugzilla.novell.com/show_bug.cgi?id=759224

there gotta some interconnection between opensuse 12.1 and opensuse 12.2

*** Bug 759224 has been marked as a duplicate of this bug. ***

Michael, I updated bug 759224 with the following information showing how I recovered my system by going back to 12.2 Milestone 3.
-----------------------------------------------------------------------------
I booted from a 12.2 Milestone 2 DVD into rescue, the Milestone 3 DVD fails
rescue.
I mounted /dev/sda1 as /mnt
chroot /mnt
grub2-install complained it couldn't find / (as I remember).

Booted 12.2 Milestone 3 DVD and chose install --> upgrade, included factory
repos.
It's up and running as Milestone 3.

It's backed off some of the changes, e.g gcc is now back at 4.6.3 whereas it
was 4.7.0 previously.

Awaiting your fix before doing zypper dup again.

Doing a zypper dup now and will try the commands suggested.

This is an autogenerated message for OBS integration:
This bug (758570) was mentioned in
https://build.opensuse.org/request/show/115825 Factory / perl-Bootloader

As the fix was already in factory, I'd like to close it.

Feel free to reopen if you still have problem. Thanks.