Bug#868268: initramfs-tools: Please add raid1 to the module added when MODULES=most
Le 14/07/2017 à 15:01, Ben Hutchings a écrit : > Control: tag -1 moreinfo > > On Thu, 2017-07-13 at 23:57 +0200, Jean-Yves LENHOF wrote: >> Package: initramfs-tools >> Version: 0.130 >> Severity: normal >> >> Dear Maintainer, >> >> When using raid1 lvm root, the raid1 module is not added to the initrd >> built (raid456 module is in). >> This will make the system unbootable and goind to the initramfs debug mode >> Please add raid1 in when selecting MODULES=most > [...] > > initramfs-tools doesn't add layered device drivers itself, because it > requires special tools to set them up. The packages containing those > tools should install hooks that add both drivers and tools to the > initramfs. > > Is dmraid installed on this system, or only dmsetup and lvm2? I'm a > bit puzzled as to how raid1 is being set up. > > Ben. Hi, Only dmsetup and lvm2 I've created the server just for the test with virt-manager Just after being installed I did transform the logical volume to have it mirrored with this command : lvconvert -m 1 --type raid1 /dev/VGroot/LVslash After wait for the copy to be made in background. (Watching with the command lvs the progress) When the copy is made reboot. The system is unbootable and go to initramfs shell I did not know for hooks, and I think in fact you were right Perhaps this bug should be reaffected to the lvm2 package I think the hook script which need to be changed to add raid1 module is /usr/share/initramfs-tools/hooks/lvm2 (in the 3 last lines) Regards, JYL
Bug#868268: initramfs-tools: Please add raid1 to the module added when MODULES=most
Package: initramfs-tools Version: 0.130 Severity: normal Dear Maintainer, When using raid1 lvm root, the raid1 module is not added to the initrd built (raid456 module is in). This will make the system unbootable and goind to the initramfs debug mode Please add raid1 in when selecting MODULES=most As a workaround you can add raid1 to /etc/initramfs-tools/modules and do update-initramfs -k all -u -- Package-specific info: -- initramfs sizes -rw-r--r-- 1 root root 18M Jul 13 23:24 /boot/initrd.img-4.9.0-3-amd64 -- /proc/cmdline BOOT_IMAGE=/boot/vmlinuz-4.9.0-3-amd64 root=/dev/mapper/VGroot-LVslash ro quiet -- resume RESUME=none -- /proc/filesystems xfs -- lsmod Module Size Used by snd_hda_codec_generic69632 1 snd_hda_intel 36864 0 snd_hda_codec 135168 2 snd_hda_intel,snd_hda_codec_generic snd_hda_core 81920 3 snd_hda_intel,snd_hda_codec,snd_hda_codec_generic snd_hwdep 16384 1 snd_hda_codec snd_pcm 110592 3 snd_hda_intel,snd_hda_codec,snd_hda_core snd_timer 32768 1 snd_pcm snd86016 6 snd_hda_intel,snd_hwdep,snd_hda_codec,snd_timer,snd_hda_codec_generic,snd_pcm soundcore 16384 1 snd qxl69632 1 ttm98304 1 qxl drm_kms_helper155648 1 qxl edac_mce_amd 28672 0 drm 360448 4 qxl,ttm,drm_kms_helper ppdev 20480 0 edac_core 57344 0 pcspkr 16384 0 evdev 24576 1 serio_raw 16384 0 joydev 20480 0 virtio_balloon 16384 0 parport_pc 28672 0 virtio_console 24576 0 parport49152 2 parport_pc,ppdev sg 32768 0 acpi_cpufreq 20480 0 button 16384 0 ip_tables 24576 0 x_tables 36864 1 ip_tables autofs440960 2 xfs 1208320 1 raid1 36864 1 dm_raid40960 1 raid456 106496 1 dm_raid async_raid6_recov 20480 1 raid456 async_memcpy 16384 2 raid456,async_raid6_recov async_pq 16384 2 raid456,async_raid6_recov async_xor 16384 3 async_pq,raid456,async_raid6_recov async_tx 16384 5 async_xor,async_pq,raid456,async_memcpy,async_raid6_recov md_mod131072 3 dm_raid,raid1,raid456 xor24576 1 async_xor raid6_pq 110592 3 async_pq,raid456,async_raid6_recov libcrc32c 16384 2 xfs,raid456 crc32c_generic 16384 1 dm_mod118784 16 dm_raid hid_generic16384 0 usbhid 53248 0 hid 122880 2 hid_generic,usbhid sr_mod 24576 0 cdrom 61440 1 sr_mod ata_generic16384 0 virtio_net 28672 0 virtio_blk 20480 4 psmouse 135168 0 floppy 69632 0 ata_piix 36864 0 ehci_pci 16384 0 uhci_hcd 45056 0 ehci_hcd 81920 1 ehci_pci usbcore 249856 4 usbhid,ehci_hcd,uhci_hcd,ehci_pci usb_common 16384 1 usbcore virtio_pci 24576 0 virtio_ring24576 5 virtio_blk,virtio_net,virtio_balloon,virtio_console,virtio_pci virtio 16384 5 virtio_blk,virtio_net,virtio_balloon,virtio_console,virtio_pci i2c_piix4 24576 0 libata249856 2 ata_piix,ata_generic scsi_mod 225280 3 libata,sr_mod,sg -- /etc/initramfs-tools/modules raid1 - /etc/kernel-img.conf # Kernel image management overrides # See kernel-img.conf(5) for details do_symlinks = yes do_bootloader = no do_initrd = yes link_in_boot = no -- /etc/initramfs-tools/initramfs.conf MODULES=most BUSYBOX=auto KEYMAP=n COMPRESS=gzip DEVICE= NFSROOT=auto -- /etc/initramfs-tools/update-initramfs.conf update_initramfs=yes backup_initramfs=no -- /proc/mdstat Personalities : [raid6] [raid5] [raid4] [raid1] unused devices: -- mkinitramfs hooks /etc/initramfs-tools/hooks/: /usr/share/initramfs-tools/hooks: dmsetup fsck keymap klibc-utils kmod lvm2 resume thermal udev zz-busybox -- System Information: Debian Release: 9.0 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-3-amd64 (SMP w/1 CPU core) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages initramfs-tools depends on: ii initramfs-tools-core 0.130 ii linux-base4.5 initramfs-tools recommends no packages. Versions of packages initramfs-tools suggests: ii bash-completion 1:2.1-4.3 -- no debconf information
Bug#783089: debian-installer: Cannot rescue a system installed on a raid1 lvm
Package: debian-installer Severity: normal Tags: d-i Dear Maintainer, I created a virtual server with 2 disks of the same size. (Problem wil be the same on a physical server with 2 disks of the same size) I did a minimum installation with : - a partition on the whole disk on each disk of type LVM. (/dev/vda1, /dev/vda2) - a volume group with name rootvg with /dev/vda1 - Everything on lvm, with /dev/rootvg/slashlv mounted on / and /dev/rootvg/swaplv for swap (a minimum partitioned system, I create more logical volume on my servers) - grub on /dev/vda And did a reboot after the installation... I can work on the server without problem... After a successul login under root, I did : - vgextend /dev/rootvg /dev/vdb1 - lvconvert --type raid1 -m 1 /dev/rootvg/slashlv - lvconvert --type raid1 -m 1 /dev/rootvg/swaplv - wait for the raid to be completely rebuilded (I checked with the lvs command) I can work on the server without problem... But If I reboot, grub can't regnosize my installation... The message (recopied manually) is : Booting from Hard Disk... error: disk `lvmid/Gwx3dG-v00h-9hJU-FVuk-Il8Z-bFUK-i6DkfU/KpVdER-OEMM-MWik-vKwM-hWxp-MeJf-LMnsf7' not found. Entering rescue mode... grub rescue So I try to reboot with the rescue mode but the CD of debian lack the module dm-raid on the kernel part. (Probably on a udeb package but don't know yet exactly which one, so I created this bug report against debian-installer), so I cannot access my disk anymore !!! Imagine you do this on a production server and you did'nt reboot before a long time. For the record, I already filled a bug report for the grub problem on http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=782591 -- System Information: Debian Release: 8.0 APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/1 CPU core) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#783089: debian-installer: Cannot rescue a system installed on a raid1 lvm
Hi, Le 22/04/2015 03:47, Lennart Sorensen a écrit : On Wed, Apr 22, 2015 at 12:28:26AM +0200, Jean-Yves LENHOF wrote: Package: debian-installer Severity: normal Tags: d-i Dear Maintainer, I created a virtual server with 2 disks of the same size. (Problem wil be the same on a physical server with 2 disks of the same size) I did a minimum installation with : - a partition on the whole disk on each disk of type LVM. (/dev/vda1, /dev/vda2) - a volume group with name rootvg with /dev/vda1 - Everything on lvm, with /dev/rootvg/slashlv mounted on / and /dev/rootvg/swaplv for swap (a minimum partitioned system, I create more logical volume on my servers) - grub on /dev/vda And did a reboot after the installation... I can work on the server without problem... After a successul login under root, I did : - vgextend /dev/rootvg /dev/vdb1 - lvconvert --type raid1 -m 1 /dev/rootvg/slashlv - lvconvert --type raid1 -m 1 /dev/rootvg/swaplv - wait for the raid to be completely rebuilded (I checked with the lvs command) Whyever would you use lvm raid rather than md raid with lvm on top? Because I prefer do it this way... lvm raid is more the traditionnal unix way of doing it (AIX and HP-UX for sure) As far as I understand it, lvm raid is very inflexible and makes it hard to ever make changes to the lvm in the future, while if you use md raid you are using something that is very flexible as raid and can easily be extended, and lvm on top of that is very flexible too. Why it is very inflexible ? It found it quite flexible. Basically your chosen setup is very unusual, and as far as I understand it highly discouraged. It will also be very hard to find anyone to help you if there are problems because it is so unusual (the normal setup works better and makes more sense, so that is what almost everyone uses). Perhaps the md raid support is there from a longer time because raid1 support (which is different from mirror support) in the kernel (and in lvm2 tools) came later... But things changes and I saw a lot of good things coming in LVM like thin lvm support or cache lvm support. Read redhat docs, such things are supported by RedHat since RedHat Enterprise 6.4 or such. Regards, -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#648633: gnome-shell-extensions: alternative status menu causes gnome-shell crash
Set a user image as a workaround The upstream bug : https://bugzilla.gnome.org/show_bug.cgi?id=660520 Regards, -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#395507: openssh: New upstream version
Package: openssh Severity: wishlist In the new upstream 4.4 version there are intersting changes : - logging sftp - the new Match Option to force a user to a command -- System Information: Debian Release: 3.1 Architecture: i386 (i686) Kernel: Linux 2.6.14-2-686 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#302718: Works now...
Hi, I just don't understand but today it works without problems Perhaps it was a hardware temporary failure But anyway you can close this one Regards, -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#297652: New version to correct this is there...
2.2.5 is there... It should be packaged because for know there are some problems with aspell dependances in sarge Regards, -- Jean-Yves LENHOF [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#291362: Workaround for this bug
Use the sarge-i386-businesscard.iso to install debian. Use expert26 to boot on the cd. Configure apt and choose a repository near you. When it will ask about which kernel version it should install, go to vt2... Do an apt-get install dmsetup (if you have a proxy do export http_proxy=http://myproxy:myport/ before) Go back to installer and choose your kernel 2.6 you want. Regards, -- Jean-Yves LENHOF [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
