[opensuse] mkinitrd, dmsetup fails in rescue system
Hi, I'm still trying to boot a fresh installed 13.1 system. The initrd does not seem to be able to find my lvm root partition. I tried to repair from rescue system $ mount /dev/vg0/root /mnt $ mount /dev/sda1 /boot $ mount --bind /proc /mnt/proc $ mount --bind /dev /mnt/dev $ mount --bind /sys /mnt/sys $ chroot /mnt $ mkinitrd Kernel image: /boot/vmlinuz-3.11.10-7-desktop Initrd image: /boot/initrd-3.11.10-7-desktop KMS drivers: i915 Root device: /dev/vg0/root (mounted on / as ext4) /dev/mapper/control: mknod failed: No such file or directory Failure to communicate with kernel device-mapper driver. Check that device-mapper is available in the kernel. Command failed [...] Microcode: Adding Intel microcode 06-3c-03 Kernel Modules: thermal_sys thermal processor fan dm-mod dm-log dm-region-hash dm-mirror dm-snapshot scsi_dh scsi_dh_rdac scsi_dh_alua scsi_dh_emc scsi_dh_hp_sw video button i2c-algo-bit drm drm_kms_helper i915 xhci-hcd hid-logitech-dj hid-holtek-kbd hid-lenovo-tpkbd hid-ortek hid-roccat hid-roccat-common hid-roccat-arvo hid-roccat-isku hid-samsung ohci-pci Features: acpi dm intel_microcode kms plymouth usb resume.userspace resume.kernel I've tracked it down. It's "dmsetup info" which failes How cat I let the device-mapper work in rescue system or how else could I create a working initrd cu, Rudi -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Monday 10 March 2014, Ruediger Meier wrote:
Hi,
I'm still trying to boot a fresh installed 13.1 system. The initrd does not seem to be able to find my lvm root partition.
I tried to repair from rescue system
$ mount /dev/vg0/root /mnt $ mount /dev/sda1 /boot $ mount --bind /proc /mnt/proc $ mount --bind /dev /mnt/dev $ mount --bind /sys /mnt/sys $ chroot /mnt
$ mkinitrd Kernel image: /boot/vmlinuz-3.11.10-7-desktop Initrd image: /boot/initrd-3.11.10-7-desktop KMS drivers: i915 Root device: /dev/vg0/root (mounted on / as ext4) /dev/mapper/control: mknod failed: No such file or directory Failure to communicate with kernel device-mapper driver. Check that device-mapper is available in the kernel. Command failed [...] Microcode: Adding Intel microcode 06-3c-03 Kernel Modules: thermal_sys thermal processor fan dm-mod dm-log dm-region-hash dm-mirror dm-snapshot scsi_dh scsi_dh_rdac scsi_dh_alua scsi_dh_emc scsi_dh_hp_sw video button i2c-algo-bit drm drm_kms_helper i915 xhci-hcd hid-logitech-dj hid-holtek-kbd hid-lenovo-tpkbd hid-ortek hid-roccat hid-roccat-common hid-roccat-arvo hid-roccat-isku hid-samsung ohci-pci Features: acpi dm intel_microcode kms plymouth usb resume.userspace resume.kernel
I've tracked it down. It's "dmsetup info" which failes
How cat I let the device-mapper work in rescue system or how else could I create a working initrd
Got it working by $ mkdir /mnt/mounts $ mount --rbind /mounts /mn/mounts ... because the links in /dev/mapper/ were pointing to a squashfs /mounts. It gets more and more complicated and obviously the openSUSE installer couldn't do it correctly too. Isn't there a command in rescue system to setup a working chroot? cu, Rudi -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
В Mon, 10 Mar 2014 12:53:58 +0100 Ruediger Meier <sweet_f_a@gmx.de> пишет:
It gets more and more complicated and obviously the openSUSE installer couldn't do it correctly too.
Isn't there a command in rescue system to setup a working chroot?
Would make life more simple for users indeed. Care to open feature request? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Mon, Mar 10, Ruediger Meier wrote:
Isn't there a command in rescue system to setup a working chroot?
13.2, maybe: https://github.com/openSUSE/installation-images/pull/10 Olaf -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
В Mon, 10 Mar 2014 13:42:44 +0100 Olaf Hering <olaf@aepfle.de> пишет:
On Mon, Mar 10, Ruediger Meier wrote:
Isn't there a command in rescue system to setup a working chroot?
13.2, maybe:
It does not touch directory discussed here (/mounts). -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Monday 10 March 2014, Andrey Borzenkov wrote:
В Mon, 10 Mar 2014 13:42:44 +0100
Olaf Hering <olaf@aepfle.de> пишет:
On Mon, Mar 10, Ruediger Meier wrote:
Isn't there a command in rescue system to setup a working chroot?
13.2, maybe:
It does not touch directory discussed here (/mounts).
IMO such non-standard file system layout should be avoided in rescue system at all. The rescue system should be easy to understand by somebody who is using it for the first time. And it should be useful to repair different kind of openSUSE versions or other distributons. BTW a nice trick to add some "documentation" how to use it could be added via /root/.bash_history. When I was using several network booted rescue systems from different root server hosters it was usually very helpful that they had a bash_history showing me some useful commands how to setup chroot or other things. Another thing which is really annoying to me is that the small "net install CD" does not contain a full rescue system. In case you need it it's very annoying to always setup network first before being able to use it. cu, Rudi -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Mon, Mar 10, Ruediger Meier wrote:
Got it working by $ mkdir /mnt/mounts $ mount --rbind /mounts /mn/mounts ... because the links in /dev/mapper/ were pointing to a squashfs /mounts.
/mounts is likely populated by autofs. I wonder why symlinks in /dev/mapper start to point to targets outside of /dev. I'm sure this is not supposed to happen. But the script could be adjusted to handle also /mounts. Please open a bug with details. Olaf -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (3)
-
Andrey Borzenkov -
Olaf Hering -
Ruediger Meier