[Bug 849071] New: Boot cycle
https://bugzilla.novell.com/show_bug.cgi?id=849071 https://bugzilla.novell.com/show_bug.cgi?id=849071#c0 Summary: Boot cycle Classification: openSUSE Product: openSUSE 13.1 Version: RC 2 Platform: x86-64 OS/Version: openSUSE 12.2 Status: NEW Severity: Critical Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: werner@suse.com QAContact: qa-bugs@suse.de CC: werner@suse.com, coolo@suse.de, fcrozat@suse.com Found By: Development Blocker: --- This happens on a virtual system but may also happen on a normal system if consoles are enabled and also I see several messages with [ *** ] A start job is running for dev-disk-by\x2d ... I see after booting into rescue mode from the RC2 boot image and mounting the root partition I have investigated /var/log/messages and /var/log/warn. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=849071
https://bugzilla.novell.com/show_bug.cgi?id=849071#c1
--- Comment #1 from Dr. Werner Fink
https://bugzilla.novell.com/show_bug.cgi?id=849071
https://bugzilla.novell.com/show_bug.cgi?id=849071#c2
Dr. Werner Fink
https://bugzilla.novell.com/show_bug.cgi?id=849071
https://bugzilla.novell.com/show_bug.cgi?id=849071#c3
--- Comment #3 from Dr. Werner Fink
https://bugzilla.novell.com/show_bug.cgi?id=849071
https://bugzilla.novell.com/show_bug.cgi?id=849071#c4
--- Comment #4 from Dr. Werner Fink
https://bugzilla.novell.com/show_bug.cgi?id=849071
https://bugzilla.novell.com/show_bug.cgi?id=849071#c5
--- Comment #5 from Dr. Werner Fink
https://bugzilla.novell.com/show_bug.cgi?id=849071
https://bugzilla.novell.com/show_bug.cgi?id=849071#c6
Frederic Crozat
https://bugzilla.novell.com/show_bug.cgi?id=849071
https://bugzilla.novell.com/show_bug.cgi?id=849071#c7
Dr. Werner Fink
what is the output of systemctl status /dev/disk/by-id/ata-VBOX_HARDDISK_VB4f483f4f-50576920-part9 or of systemctl status /dev/sda9 ?
Let's see: werner/systemd> slogin g7 Last login: Wed Nov 6 09:21:24 2013 from boole.suse.de Have a lot of fun... linux /suse/werner> systemctl status /dev/disk/by-id/ata-VBOX_HARDDISK_VB4f483f4f-50576920-part9 dev-disk-by\x2did-ata\x2dVBOX_HARDDISK_VB4f483f4f\x2d50576920\x2dpart9.device Loaded: loaded Active: inactive (dead) linux /suse/werner> systemctl status /dev/sda9 dev-sda9.device - VBOX_HARDDISK Follow: unit currently follows state of sys-devices-pci0000:00-0000:00:0d.0-ata1-host0-target0:0:0-0:0:0:0-block-sda-sda9.device Loaded: loaded Active: active (plugged) Device: /sys/devices/pci0000:00/0000:00:0d.0/ata1/host0/target0:0:0/0:0:0:0/block/sda/sda9 .. smells like a udev problem(?) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=849071
https://bugzilla.novell.com/show_bug.cgi?id=849071#c8
Robert Milasan
https://bugzilla.novell.com/show_bug.cgi?id=849071
https://bugzilla.novell.com/show_bug.cgi?id=849071#c9
Dr. Werner Fink
console-shell.service is only used to get a shell on /dev/console, when not running getty. My guess it was added for embedded distro (or debug purpose).
I guess we should maybe prevent some services to be enabled in YaST. Removing the "[Install]" section would prevent systemctl enable to work on it at all (still allowing manual symlink to enable it but that is ok, I think).
OK the SR#205942 should fix that (In reply to comment #8)
Can you check if /dev/disk/by-id/ata-VBOX_HARDDISK_VB4f483f4f-50576920-part9 actually exists or points to the right device?
It does not linux /suse/werner> ll -G /dev/disk/by-id/ | grep part9 lrwxrwxrwx 1 root 10 Nov 5 19:13 ata-VBOX_HARDDISK_VBf2a6c046-4d1601b6-part9 -> ../../sda9 lrwxrwxrwx 1 root 10 Nov 5 19:13 scsi-1ATA_VBOX_HARDDISK_VBf2a6c046-4d1601b6-part9 -> ../../sda9 lrwxrwxrwx 1 root 10 Nov 5 19:13 scsi-SATA_VBOX_HARDDISK_VBf2a6c046-4d1601b6-part9 -> ../../sda9 .. how the IDs will be calculated? I had trouble to boot grub2 from the virtual parition table of the VirtualBox disk layout[1]. That is I had to extend the virtual but old DOS partition table with 63 blocks for the MBR to a modern partition table to be able to install grub in the 2048 blocks of such an extend MBR ... I'll change /etc/fstab to the new IDs [1] werner/systemd> VBoxManage internalcommands listpartitions -rawdisk /dev/sdb Number Type StartCHS EndCHS Size (MiB) Start (Sect) 1 0x82 0 /32 /33 1023/254/63 8188 2048 5 0x82 1023/254/63 1023/254/63 4094 16773120 6 0x83 1023/254/63 1023/254/63 98303 25159680 7 0x82 1023/254/63 1023/254/63 4094 226486272 8 0x83 1023/254/63 1023/254/63 98303 234872832 9 0x82 1023/254/63 1023/254/63 4093 436199424 10 0x83 1023/254/63 1023/254/63 98303 444583936 11 0x82 1023/254/63 1023/254/63 4094 645910528 12 0x83 1023/254/63 1023/254/63 157449 654297088 werner/systemd> cat /abuild/VirtualBox/Machines/OpenSUSE\ 13.1/OpenSUSE\ 13.1.vmdk # Disk DescriptorFile version=1 CID=a6b758ca parentCID=ffffffff createType="partitionedDevice" # Extent description RW 2048 FLAT "OpenSUSE 13.1-fixed.vmdk" 0 RW 16769024 ZERO RW 63 FLAT "OpenSUSE 13.1-fixed.vmdk" 2048 RW 1985 ZERO RW 8384512 ZERO RW 158 ZERO RW 63 FLAT "OpenSUSE 13.1-fixed.vmdk" 2111 RW 1827 ZERO RW 201324544 ZERO RW 146 ZERO RW 63 FLAT "OpenSUSE 13.1-fixed.vmdk" 2174 RW 1839 ZERO RW 8384512 ZERO RW 63 FLAT "OpenSUSE 13.1-fixed.vmdk" 2237 RW 1985 ZERO RW 201324544 ZERO RW 63 FLAT "OpenSUSE 13.1-fixed.vmdk" 2300 RW 1985 ZERO RW 8382464 FLAT "/dev/sdb9" 0 RW 922 ZERO RW 63 FLAT "OpenSUSE 13.1-fixed.vmdk" 2363 RW 1063 ZERO RW 201324544 FLAT "/dev/sdb10" 0 RW 910 ZERO RW 63 FLAT "OpenSUSE 13.1-fixed.vmdk" 2426 RW 1075 ZERO RW 8384512 ZERO RW 280 ZERO RW 63 FLAT "OpenSUSE 13.1-fixed.vmdk" 2489 RW 1705 ZERO RW 322455552 ZERO RW 20528 ZERO -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=849071
https://bugzilla.novell.com/show_bug.cgi?id=849071#c10
--- Comment #10 from Bernhard Wiedemann
https://bugzilla.novell.com/show_bug.cgi?id=849071
https://bugzilla.novell.com/show_bug.cgi?id=849071#c11
--- Comment #11 from Robert Milasan
It does not
linux /suse/werner> ll -G /dev/disk/by-id/ | grep part9 lrwxrwxrwx 1 root 10 Nov 5 19:13 ata-VBOX_HARDDISK_VBf2a6c046-4d1601b6-part9 -> ../../sda9 lrwxrwxrwx 1 root 10 Nov 5 19:13 scsi-1ATA_VBOX_HARDDISK_VBf2a6c046-4d1601b6-part9 -> ../../sda9 lrwxrwxrwx 1 root 10 Nov 5 19:13 scsi-SATA_VBOX_HARDDISK_VBf2a6c046-4d1601b6-part9 -> ../../sda9
There is your problem. For whatever reason what you have setup in fstab and grub.conf is totally different then what is really available. Not sure why you have a different info, besides maybe different disk with different serial number. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=849071
https://bugzilla.novell.com/show_bug.cgi?id=849071#c12
Dr. Werner Fink
https://bugzilla.novell.com/show_bug.cgi?id=849071
https://bugzilla.novell.com/show_bug.cgi?id=849071#c13
Robert Milasan
https://bugzilla.novell.com/show_bug.cgi?id=849071
https://bugzilla.novell.com/show_bug.cgi?id=849071#c14
--- Comment #14 from Frederic Crozat
(In reply to comment #11)
... Beside this systemd 208 seems now to wait on jobs even if LSB ... from /var/log/boot.log
[* ] (1 of 2) A start job is running for LSB: Configure n... set up routing [** ] (1 of 2) A start job is running for LSB: Configure n... set up routing [ ***] (2 of 2) A start job is running for ifup managed net...nterface enp0s3
... this seems to be new
The animation is new, but the wait was already there.. /var/log/boot.log is written by plymouth, so maybe it is a bit stupid in what it is writing :) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=849071
https://bugzilla.novell.com/show_bug.cgi?id=849071#c15
--- Comment #15 from Dr. Werner Fink
https://bugzilla.novell.com/show_bug.cgi?id=849071
https://bugzilla.novell.com/show_bug.cgi?id=849071#c16
--- Comment #16 from Dr. Werner Fink
https://bugzilla.novell.com/show_bug.cgi?id=849071
https://bugzilla.novell.com/show_bug.cgi?id=849071#c17
--- Comment #17 from Bernhard Wiedemann
https://bugzilla.novell.com/show_bug.cgi?id=849071
https://bugzilla.novell.com/show_bug.cgi?id=849071#c
Dr. Werner Fink
https://bugzilla.novell.com/show_bug.cgi?id=849071
https://bugzilla.novell.com/show_bug.cgi?id=849071#c18
--- Comment #18 from Bernhard Wiedemann
https://bugzilla.novell.com/show_bug.cgi?id=849071
https://bugzilla.novell.com/show_bug.cgi?id=849071#c19
Dr. Werner Fink
https://bugzilla.novell.com/show_bug.cgi?id=849071
https://bugzilla.novell.com/show_bug.cgi?id=849071#c20
--- Comment #20 from Bernhard Wiedemann
https://bugzilla.novell.com/show_bug.cgi?id=849071
https://bugzilla.novell.com/show_bug.cgi?id=849071#c21
--- Comment #21 from Swamp Workflow Management
participants (1)
-
bugzilla_noreply@novell.com