|
Bugzilla – Full Text Bug Listing |
| Summary: | LILO "read-only" flag | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 11.0 | Reporter: | Forgotten User N1m2whZ-xl <forgotten_N1m2whZ-xl> |
| Component: | Other | Assignee: | Josef Reidinger <jreidinger> |
| Status: | RESOLVED FIXED | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Normal | ||
| Priority: | P3 - Medium | CC: | cerebus_8, davejplater, dgahling, forgotten_OfsFetVrzR, mike, per, pmendygral, pth |
| Version: | Beta 1 | ||
| Target Milestone: | --- | ||
| Hardware: | i686 | ||
| OS: | openSUSE 11.0 | ||
| Whiteboard: | |||
| Found By: | Beta-Customer | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: |
Trimmed YaST2 log directory and lilo.confs
tar.gz of /var/log/YaST2/ /etc/lilo.conf |
||
|
Description
Forgotten User N1m2whZ-xl
2008-04-19 21:22:29 UTC
I see the same thing here. I updated to factory lilo on an existing install and had the same problem, solved by removing read-only from lilo.conf. I could only start to single user mode. Could you please provide yast2 logs (http://en.opensuse.org/Bugs/YaST) and your /etc/lilo.conf? Created attachment 209567 [details]
Trimmed YaST2 log directory and lilo.confs
Sorry about the mess, I only have a 10.3 cd to repair 11 and I switched between grub and lilo a couple of times. When the 10.3 lilo was installed my system booted. I also played with my kernel a bit to try and fix the problem. It started on Friday when I switched to lilo in order to get Vista to work for my daughter, I wasn't able to get grub to dual boot properly. I could kick myself for not noticing read-only in lilo.conf earlier. I have also recently changed to xfs just to add to my own confusion.
The 'read-only' flag in lilo.conf is normal I think. The root filesystem should normally be remounted read/write by boot.rootfsck. Created attachment 209696 [details]
tar.gz of /var/log/YaST2/
Created attachment 209697 [details]
/etc/lilo.conf
The bug is still present in Beta 2. IMO this is problem of perl-Bootloader. Alexander could you check it please? 11.0 seems to check root filesystem in initial ramdisk so that boot.rootfsck does neither check it nor remount it read-write. Thus the solution would be not including 'read-only' directive by default. Or let boot.rootfsck remount root filesystem read-write even if it is already checked by initial ramdisk. An option may be to force re-check (which would be not very time consuming) in boot.rootfsck. As the problem is between initial ramdisk and init scripts, GRUB should have the same problem as well. IMHO LILO should solve it the way GRUB does, ie. if GRUB doesn't pass read-only flag to kernel (does it?), neither should LILO. *** Bug 382070 has been marked as a duplicate of this bug. *** yes this is a duplicate of my bug report 382070. How are we going to resolve this? I see the "read-only" in lilo.conf on 10.3, which is carried over to 11.0 will this get fixed in time for 11.0 final release? New package is submitted for openSUSE 11.0, thus problem will be fixed with next build. Closing RESOLVED FIXED. I'm curious about how this worked in 10.3 since it had the read-only as well, and how things changed so much to break that? What I mean is, why couldn't 11.0 do what 10.3 did, since that worked? I apologize for adding to a bug that has been resolved. I did a network upgrade from 10.1 to 11.0 just this weekend, and I had this same exact problem happen. Did this patch really make it in? My system is x86_64 with the root partition on a raid1 (/dev/md0) array. LILO mounts it as read-only with fsck reporting success. I commented out the read-only line as noted above. Also as noted above, the system will now load into single user mode. I can confirm that 11.0 still has this bug. Yep, it sure does. I tried to repost my info, but that bug report got closed too. I have a "work around" (or two) of sorts, but it's not pretty. Do a base install, absolute base using the GM (non-retail) 11.0, use it's default, I believe ext3/grub. Note, if you used LILO before or are upgrading, or even reinstalling overtop (with format) of a system that had LILO, you're going to run into problems! There's only one way around that I've found, in the bootloader config, under grub, choose "boot", "root" AND "mbr", this will force it to rewrite all three sections and finally work properly. once installed, go into the bootloader, change to LILO, and use "propose", make sure all three parts are chosen, again. or, alternatively, during the install setup of bootloader, choose grub, select all three, THEN switch to LILO, use "propse", and it *should* keep the three parts (root/boot/mbr). you can use reiserfs or ext3 with this method. I've confirmed these methods work on all the systems I've tried. it's not pretty though. Reassigning to new maintainer. in svn I fixed it (remove from read-only flag during kernel update)...it time to expect bugreport about removing read-only flag :) will be in perl-Bootloader-0.4.70 0.4.70 released, if problem still happen please reopen with actual logs Still waiting for perl-Bootloader-0.4.70. Did not appear yet. |