|
Bugzilla – Full Text Bug Listing |
| Summary: | cannot boot installed system from installation system | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 11.2 | Reporter: | michel munnix <michel.munnix> |
| Component: | YaST2 | Assignee: | Josef Reidinger <jreidinger> |
| Status: | RESOLVED WONTFIX | QA Contact: | Jiri Srain <jsrain> |
| Severity: | Major | ||
| Priority: | P3 - Medium | CC: | jdsn, jreidinger, jsrain, snwint |
| Version: | Milestone 7 | ||
| Target Milestone: | --- | ||
| Hardware: | i586 | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: |
/var/log
y2logs.tgz saved before clicking "Boot" tail -f /var/log/YaST2/y2log from clicking "Boot" |
||
|
Description
michel munnix
2009-09-24 13:57:11 UTC
alternate boot method: using boot menu entry 3: "repair installed system" directly, it does mount the root partition and gives a login prompt "very fast" in session 1. The keyboard is english, not belgian as configured in that partition If I type the root password as if it where a qwerty keyboard, I get the message: "Error in service module" and again the login prompt In session 3: starting /dev/sda7 insmod /modules/crc16.ko insmod: error inserting '/modules/crc16.ko': -1 File exists Created attachment 319875 [details]
/var/log
reverting to the first method to get yast2 logs
attaching the logs
It doesn't look like and installation issue... What about 'repair'? Sorry, repair was not in the components list, trying yast2 trying again with milestone 8: boot menu entry 3: "repair installed system" expert tools: boot installed system selected the "milestone 7" partition / "boot" message: modprobe: FATAL: Could not open '/lib/modules/2.6.31-10-default/initrd/ext4.ko': No such file or directory shift lock led blinks Steffen, did the linuxrc menu or its behaviour change? Not that I'm aware of. But I think this report is mostly about yast's repair tool? (In reply to comment #7) > Not that I'm aware of. But I think this report is mostly about yast's repair > tool? I think that this message says why repair cannot boot this system: modprobe: FATAL: Could not open '/lib/modules/2.6.31-10-default/initrd/ext4.ko': No such file or directory There is missing module for ext4 in insts-sys. This is not repair problem. I am not sure, who is responsible for packages in inst-sys. The module is there; ext4 is our default fs! I don't know why it is missing at that point, though. (In reply to comment #9) > The module is there; ext4 is our default fs! I don't know why it is missing > at that point, though. OK, I look at it. Could you please provide fresh yast logs from M8? It looks like problem is little change and I cannot find who tries load ext4 module and in which way. Thanks Created attachment 321323 [details]
y2logs.tgz saved before clicking "Boot"
Created attachment 321325 [details]
tail -f /var/log/YaST2/y2log from clicking "Boot"
I did set yast2 logs to verbose before clicking "Boot" and appended y2log to a file on a usb stick while continuously syncing
That's the most I can get until the message about ext4.ko appears
At that moment, keyboard leds blink and system is halted
(In reply to comment #11) > Could you please provide fresh yast logs from M8? Logs are attached, Josef. thanks for logs. I find that ext4 is not supported by repair (looks like communication error, because no one add this item to my features). Also I found that is problem if yast fallback to text_mode, then repair crash (founded during reproducing on M8). I take this bug, but due to big workload I am not sure if I can fix it until 11.2 release. yast2-repair is dropped now, so no fixes will be done |