|
Bugzilla – Full Text Bug Listing |
| Summary: | openSUSE 12.2 freezes during installation (there are another *BSD and Linux encrypted partitions) | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 12.2 | Reporter: | Alexander Naumov <alexander_naumov> |
| Component: | Installation | Assignee: | E-mail List <kernel-maintainers> |
| Status: | RESOLVED DUPLICATE | QA Contact: | Jiri Srain <jsrain> |
| Severity: | Critical | ||
| Priority: | P2 - High | CC: | rpm |
| Version: | Final | ||
| Target Milestone: | --- | ||
| Hardware: | x86-64 | ||
| OS: | openSUSE 12.2 | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: |
/var/log/YaST2/y2log
dmesg output (installation) strace /sbin/blkid -c /dev/null (from rescure system) |
||
Please attach y2log file. Created attachment 509004 [details]
/var/log/YaST2/y2log
sdc(1) - usb stick for copying log-file
The last command executed just before the hang is: BLKID_SKIP_CHECK_MDRAID=1 /sbin/blkid -c /dev/null Strange. /sbin/blkid just opens all block devices and checks for md, lvm, swap, filesystem signatures. As far as I can see there is no problem with your disks (parted display all partitions fine). Could be that blkid is confused by BSD partition. Maybe it is the cdrom drive. Are there any unusual devices attached? Could you boot into a rescue system and execute the following command strace /sbin/blkid -c /dev/null and see where it hangs, strace output can be put into a file with strace -o <filename> ... If possible please attach strace output here. Potentially interesting could also be kernel messages on different consoles or output of command dmesg. Created attachment 509018 [details]
dmesg output (installation)
Created attachment 509019 [details]
strace /sbin/blkid -c /dev/null (from rescure system)
> Maybe it is the cdrom drive. It looks like a floppy drive (/dev/fd0), but you can believe me - I haven't one :) > Are there any unusual devices attached? No. I had the same bug. It freezes at 60%, but in the background it tries to call the floppy-drive (which I do not have), so it freeze for about 10 Minutes. But you can work around this bug by deactivate floppy in the BIOS or if your BIOS does not support this you can blacklist floppy after SUSE installation. So it seems that openSUSE does not ignore the missing response of a floppy-drive if floppy is enabled... BR So this seems to be either a problem with udev creating devices for non-existing hardware or the kernel handling access to non-existing floppy drives. Reassigning to kernel maintainers. I can reproduce it in openSUSE 12.3 Beta1. Sigh. Yet another nonexistent floppy drive problem. Can we get the partitioner to stop probing them? It seems like modern BIOSes aren't tested with access to the floppy port i/o addresses and freak out. *** This bug has been marked as a duplicate of bug 773058 *** |
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:7.0.1) Gecko/20110929 Firefox/7.0.1 SeaMonkey/2.4.1 Hello, I'm trying to install oS 12.2 on x86_64 with 2 SATA disks. Installation process freezes during checking system information (after choose language and keyboard layout) at 60% (information about partition table). As you can see I have there OpenBSD and encrypted Linux partitions. I think that's the reason of this problem. Output from oS 12.1 (encrypted) ================================================= # fdisk -l Disk /dev/sda: 250.0 GB, 250000000000 bytes 255 heads, 63 sectors/track, 30394 cylinders, total 488281250 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x000f3bd3 Device Boot Start End Blocks Id System /dev/sda1 * 2048 610303 304128 83 Linux /dev/sda2 610304 210323455 104856576 8e Linux LVM /dev/sda3 210323456 302593127 46134836 a6 OpenBSD Disk /dev/sdb: 750.2 GB, 750156374016 bytes 255 heads, 63 sectors/track, 91201 cylinders, total 1465149168 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x000539b2 Device Boot Start End Blocks Id System /dev/sdb1 2048 8386559 4192256 82 Linux swap / Solaris /dev/sdb2 * 8386560 427827199 209720320 83 Linux Disk /dev/mapper/cr_sda2: 107.4 GB, 107371036672 bytes 255 heads, 63 sectors/track, 13053 cylinders, total 209709056 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x00000000 Disk /dev/mapper/cr_sda2 doesn't contain a valid partition table Disk /dev/mapper/system-root: 103.1 GB, 103075020800 bytes 255 heads, 63 sectors/track, 12531 cylinders, total 201318400 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x00000000 Disk /dev/mapper/system-root doesn't contain a valid partition table Disk /dev/mapper/system-swap: 4294 MB, 4294967296 bytes 255 heads, 63 sectors/track, 522 cylinders, total 8388608 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x00000000 Disk /dev/mapper/system-swap doesn't contain a valid partition table ================================================= I installed oS 12.2 on another x86_64 machine (without *BSD and Linux encrypted partitions), and I haven't some problems there. Can you tell me how to debug this problem and what's name of YaST modul/package, that check system information during installation? Thank you Reproducible: Always Steps to Reproduce: 1. Just run installer 2. Wait for checking information about partition table 3.