Bugzilla – Bug 152738
installation hangs on volume group creation
Last modified: 2006-03-21 13:27:57 UTC
0) choosed minimal installation 1a) created 2 mirrors (on 2 disks) one 150M, one 10G (disks size 32Gb, identical) 2a) 150M - /boot (on md0), 10G for volume group sys (on md1) 3a) installer created partiotions, raids, volume group, but logical volumes in vg aren't that, which i choose. Installer created 3 lv - domU_root, dom1_swap, dom1_root (snapshot from domU_root) 1b) created 2 mirrors (on 2 disks) one 150M, one 32G (max aviable remaining size) 2b) 150M - /boot (on md0), 32G for volume group sys (on md1) 3b) installer creates all in right way (as far as i know), but when reboots - than not cames up - "mdadm: Bad super-minor number: .", resyncronize raid in background, after than don't came up too ;(
Hint: Pressing `Submit bug' once will also do ;)
*** Bug 152736 has been marked as a duplicate of this bug. ***
*** Bug 152737 has been marked as a duplicate of this bug. ***
*** Bug 152722 has been marked as a duplicate of this bug. ***
This still is in effect: Please be more verbose and add information about your disks (`fdisk -l' and a volume group scan), furthermore add the YaST2 logs located in /var/log/YaST2/* as tarball and the resulting fstab of the system.
About than:" 1) created 2 mirrors (on 2 disks) one 150M, one 10G 2) 150M - /boot, 10G for volume group sys 3) when creating fs in sys vg, than sys vg size is shown as whole disk size, but not 10G ;(" Can reproduse: Have vg on disks when install, vg is on raid-1, on another raid-1 is /boot, on disks is free not partiioned space. In my case i have 150M raid-1 (sda1, sdb1) on it was /boot, 10G raid-1 (sda2, sdb2) on than md device was "sys" volume group, on 32G disks. In vg wasn't no logical volume, when added lvs, than free size was not 10G, but 33.2G
(In reply to comment #5) > This still is in effect: > > Please be more verbose and add information about your disks (`fdisk -l' and a > volume group scan), furthermore add the YaST2 logs located in /var/log/YaST2/* > as tarball and the resulting fstab of the system. > (In reply to comment #5) > This still is in effect: > > Please be more verbose and add information about your disks (`fdisk -l' and a > volume group scan), furthermore add the YaST2 logs located in /var/log/YaST2/* > as tarball and the resulting fstab of the system. > Disks - Seagate st336607LC how could i get than /var/log/YaST2/* if there isn't network configured?
> how could i get than /var/log/YaST2/* if there isn't network configured? Change to console two, mount a disk, copy the logfiles there and retrieve them later.
> Change to console two, mount a disk, copy the logfiles there and retrieve them > later. > Ok, will try find usb stick. Logs for what case your are interesting in? 1)Wrong free size in vg? 2)Wrong lvs are created, patitioner GUI looks hangs on create vg. 3)System don't boot with "mdadm: Bad super-minor number: ."? Could you reproduce any of that 3 bugs? Maybe my hardware issue?
Provide as much information as you can and after the errors ocurred, compress the directory /var/log/YaST2 and attach it here.
Created attachment 70152 [details] for case#2 - installer stops on "Creating volume group sys"
Partitioner issue, reassigning.
From the log I see that command it hangs is: "pvcreate -ff -M2 /dev/md1" I tried to reproduce this on beta#8 and the pvcreate calls returned fast. Please retry with beta#8 or newer. If it still handgs also look for md realted kernel messages in /var/log/messages.
(In reply to comment #13) > From the log I see that command it hangs is: > > "pvcreate -ff -M2 /dev/md1" > > I tried to reproduce this on beta#8 and the pvcreate calls returned fast. > Please retry with beta#8 or newer. If it still handgs also look for > md realted kernel messages in /var/log/messages. > Installation hangs anyway. It hangs on creating volume group. For me strange is this, from dmesg: device-mapper: device doesn't appear to be in the dev hash table. Logs and some related info will attached.
Created attachment 74100 [details] Logs from beta8
Unfortunately this does not show anything helpful, could you try changing to an ascii console and execute "strace pvcreate -ff -M2 /dev/md1" to see where the command hangs.
(In reply to comment #16) > Unfortunately this does not show anything helpful, could you try changing to > an ascii console and execute "strace pvcreate -ff -M2 /dev/md1" to see where > the command hangs. > there was such process in process list, so first time pvcreate hunged, when i killed than process, command was asked confirmation and sucessfully ended.
I meant not doing it all by YaST2 but by typing the command "strace pvcreate -ff -M2 /dev/md1" manually after you switch to an ascii console. This way I possibly should be able to see where pvcreate hangs. What did you mean with "command was asked confirmation"? Did pvcreate write anything to the screen and expected user input?
there was process "pvcreate -ff -M2 /dev/md1" - so first time pvcreate stoppped due vg lock, when a killed that process, than a could create pv.
> What did you mean with "command was asked confirmation"? > Did pvcreate write anything to the screen and expected user input? > I type pvcreate -ff -M2 /dev/md1 and got: Really INITIALIZE physical volume "/dev/md1" of volume group "system" [y/n]?
Thaks alot, this was what I was searching for. I was now able to reproduce and fix this here. Problem should be fixed in RC1