Re: lots of complaints with latest upgrade
The errors are caused by operating on a system using LVM, for which one of the disks died and some are missing because I switched to new hardware. Apparently update-grub scans for disks, and the LVM containers are aware of the absent disk, hence the errors. So I think I'm OK for the update, given that some disks are missing. Obviously enough are present to run the system! Ross On Mon, Sep 2, 2013 at 12:39 PM, André Nunes Batista andrenbati...@gmail.com wrote: On Thu, 2013-08-29 at 09:38 -0700, Ross Boylan wrote: Running wheezy amd64 the kernel/libc upgrade from today produced lots of complaints: terminal Preparing to replace linux-image-3.2.0-4-amd64 3.2.46-1 (using .../linux-image-3.2.0-4-amd64_3.2.46-1+deb7u1_amd64.deb) ... Unpacking replacement linux-image-3.2.0-4-amd64 ... Examining /etc/kernel/postrm.d . run-parts: executing /etc/kernel/postrm.d/initramfs-tools 3.2.0-4-amd64 /boot/vmlinuz-3.2.0-4-amd64 run-parts: executing /etc/kernel/postrm.d/zz-update-grub 3.2.0-4-amd64 /boot/vmlinuz-3.2.0-4-amd64 Preparing to replace linux-libc-dev:amd64 3.2.46-1 (using .../linux-libc-dev_3.2.46-1+deb7u1_amd64.deb) ... Unpacking replacement linux-libc-dev:amd64 ... Setting up linux-image-3.2.0-4-amd64 (3.2.46-1+deb7u1) ... Running depmod. Examining /etc/kernel/postinst.d. run-parts: executing /etc/kernel/postinst.d/initramfs-tools 3.2.0-4-amd64 /boot/vmlinuz-3.2.0-4-amd64 update-initramfs: Generating /boot/initrd.img-3.2.0-4-amd64 run-parts: executing /etc/kernel/postinst.d/pm-utils 3.2.0-4-amd64 /boot/vmlinuz-3.2.0-4-amd64 run-parts: executing /etc/kernel/postinst.d/zz-update-grub 3.2.0-4-amd64 /boot/vmlinuz-3.2.0-4-amd64 Generating grub.cfg ... Found background image: /usr/share/images/desktop-base/desktop-grub.png Found linux image: /boot/vmlinuz-3.2.0-4-amd64 Found initrd image: /boot/initrd.img-3.2.0-4-amd64 /dev/dm-0: read failed after 0 of 4096 at 22028419072: Input/output error /dev/dm-0: read failed after 0 of 4096 at 22028476416: Input/output error /dev/dm-0: read failed after 0 of 4096 at 0: Input/output error /dev/dm-0: read failed after 0 of 4096 at 4096: Input/output error /dev/dm-1: read failed after 0 of 4096 at 6324944896: Input/output error /dev/dm-1: read failed after 0 of 4096 at 6325002240: Input/output error . /dev/dm-8: read failed after 0 of 4096 at 4096: Input/output error /dev/sdf: read failed after 0 of 4096 at 0: Input/output error /dev/sdf: read failed after 0 of 4096 at 120034033664: Input/output error /dev/sdf: read failed after 0 of 4096 at 120034115584: Input/output error /dev/sdf: read failed after 0 of 4096 at 4096: Input/output error /dev/sdf1: read failed after 0 of 4096 at 2097348608: Input/output error /dev/sdf1: read failed after 0 of 4096 at 2097405952: Input/output error /dev/sdf1: read failed after 0 of 4096 at 0: Input/output error /dev/sdf1: read failed after 0 of 4096 at 4096: Input/output error /dev/sdf5: read failed after 0 of 2048 at 4096: Input/output error Couldn't find device with uuid GKasb9-Qo8q-vC83-S0N7-cvUd-nE0J-EEeMgv. Couldn't find device with uuid eDiLHt-Pzom-tjdr-Ky12-Z6Gx-o3Iz-lYh1wL. rmdir: failed to remove `/var/lib/os-prober/mount': Device or resource busy rmdir: failed to remove `/var/lib/os-prober/mount': Device or resource busy rmdir: failed to remove `/var/lib/os-prober/mount': Device or resource busy rmdir: failed to remove `/var/lib/os-prober/mount': Device or resource busy rmdir: failed to remove `/var/lib/os-prober/mount': Device or resource busy grub-probe: error: no such disk. rmdir: failed to remove `/var/lib/os-prober/mount': Device or resource busy rmdir: failed to remove `/var/lib/os-prober/mount': Device or resource busy Found Ubuntu 13.04 (13.04) on /dev/sda1 Found Debian GNU/Linux (7.0) on /dev/sdd1 Found Debian GNU/Linux (wheezy/sid) on /dev/mapper/daisy-amd64 Found Debian GNU/Linux (7.0) on /dev/mapper/daisy-chroot Found Debian GNU/Linux (6.0.2) on /dev/mapper/daisy-root_rescue done Setting up linux-libc-dev:amd64 (3.2.46-1+deb7u1) ... /terminal Does anyone know what's going on, or if I should be concerned? I think all the errors are associated with update-grub. My system is currently a hodge-podge as a result of earlier hardware failure. It shipped with a SSD with Ubuntu installed; I added lots of hard drives from the failed system; some of those drives are in a Vantec enclosure connected by USB. I'm using lvm and luks crypto. Thanks. Ross Boylan My wild guess is that those hard drives are one step away from complete failure. You should backup any sensitive info on those drives if you haven't done that already. Those messages mean what they say, your kernel is not being able to read some parts on those drives and at least two identified by UUID are not accessible at all. You may want to run badblocks or
Re: lots of complaints with latest upgrade
On Thu, 2013-08-29 at 09:38 -0700, Ross Boylan wrote: Running wheezy amd64 the kernel/libc upgrade from today produced lots of complaints: terminal Preparing to replace linux-image-3.2.0-4-amd64 3.2.46-1 (using .../linux-image-3.2.0-4-amd64_3.2.46-1+deb7u1_amd64.deb) ... Unpacking replacement linux-image-3.2.0-4-amd64 ... Examining /etc/kernel/postrm.d . run-parts: executing /etc/kernel/postrm.d/initramfs-tools 3.2.0-4-amd64 /boot/vmlinuz-3.2.0-4-amd64 run-parts: executing /etc/kernel/postrm.d/zz-update-grub 3.2.0-4-amd64 /boot/vmlinuz-3.2.0-4-amd64 Preparing to replace linux-libc-dev:amd64 3.2.46-1 (using .../linux-libc-dev_3.2.46-1+deb7u1_amd64.deb) ... Unpacking replacement linux-libc-dev:amd64 ... Setting up linux-image-3.2.0-4-amd64 (3.2.46-1+deb7u1) ... Running depmod. Examining /etc/kernel/postinst.d. run-parts: executing /etc/kernel/postinst.d/initramfs-tools 3.2.0-4-amd64 /boot/vmlinuz-3.2.0-4-amd64 update-initramfs: Generating /boot/initrd.img-3.2.0-4-amd64 run-parts: executing /etc/kernel/postinst.d/pm-utils 3.2.0-4-amd64 /boot/vmlinuz-3.2.0-4-amd64 run-parts: executing /etc/kernel/postinst.d/zz-update-grub 3.2.0-4-amd64 /boot/vmlinuz-3.2.0-4-amd64 Generating grub.cfg ... Found background image: /usr/share/images/desktop-base/desktop-grub.png Found linux image: /boot/vmlinuz-3.2.0-4-amd64 Found initrd image: /boot/initrd.img-3.2.0-4-amd64 /dev/dm-0: read failed after 0 of 4096 at 22028419072: Input/output error /dev/dm-0: read failed after 0 of 4096 at 22028476416: Input/output error /dev/dm-0: read failed after 0 of 4096 at 0: Input/output error /dev/dm-0: read failed after 0 of 4096 at 4096: Input/output error /dev/dm-1: read failed after 0 of 4096 at 6324944896: Input/output error /dev/dm-1: read failed after 0 of 4096 at 6325002240: Input/output error . /dev/dm-8: read failed after 0 of 4096 at 4096: Input/output error /dev/sdf: read failed after 0 of 4096 at 0: Input/output error /dev/sdf: read failed after 0 of 4096 at 120034033664: Input/output error /dev/sdf: read failed after 0 of 4096 at 120034115584: Input/output error /dev/sdf: read failed after 0 of 4096 at 4096: Input/output error /dev/sdf1: read failed after 0 of 4096 at 2097348608: Input/output error /dev/sdf1: read failed after 0 of 4096 at 2097405952: Input/output error /dev/sdf1: read failed after 0 of 4096 at 0: Input/output error /dev/sdf1: read failed after 0 of 4096 at 4096: Input/output error /dev/sdf5: read failed after 0 of 2048 at 4096: Input/output error Couldn't find device with uuid GKasb9-Qo8q-vC83-S0N7-cvUd-nE0J-EEeMgv. Couldn't find device with uuid eDiLHt-Pzom-tjdr-Ky12-Z6Gx-o3Iz-lYh1wL. rmdir: failed to remove `/var/lib/os-prober/mount': Device or resource busy rmdir: failed to remove `/var/lib/os-prober/mount': Device or resource busy rmdir: failed to remove `/var/lib/os-prober/mount': Device or resource busy rmdir: failed to remove `/var/lib/os-prober/mount': Device or resource busy rmdir: failed to remove `/var/lib/os-prober/mount': Device or resource busy grub-probe: error: no such disk. rmdir: failed to remove `/var/lib/os-prober/mount': Device or resource busy rmdir: failed to remove `/var/lib/os-prober/mount': Device or resource busy Found Ubuntu 13.04 (13.04) on /dev/sda1 Found Debian GNU/Linux (7.0) on /dev/sdd1 Found Debian GNU/Linux (wheezy/sid) on /dev/mapper/daisy-amd64 Found Debian GNU/Linux (7.0) on /dev/mapper/daisy-chroot Found Debian GNU/Linux (6.0.2) on /dev/mapper/daisy-root_rescue done Setting up linux-libc-dev:amd64 (3.2.46-1+deb7u1) ... /terminal Does anyone know what's going on, or if I should be concerned? I think all the errors are associated with update-grub. My system is currently a hodge-podge as a result of earlier hardware failure. It shipped with a SSD with Ubuntu installed; I added lots of hard drives from the failed system; some of those drives are in a Vantec enclosure connected by USB. I'm using lvm and luks crypto. Thanks. Ross Boylan My wild guess is that those hard drives are one step away from complete failure. You should backup any sensitive info on those drives if you haven't done that already. Those messages mean what they say, your kernel is not being able to read some parts on those drives and at least two identified by UUID are not accessible at all. You may want to run badblocks or smartctl to get a clear picture on the state of those drives. It's possible they are approaching unusable state. -- André N. Batista GNUPG/PGP KEY: 6722CF80 -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1378150787.16817.8.camel@tagesuhu-pc
lots of complaints with latest upgrade
Running wheezy amd64 the kernel/libc upgrade from today produced lots of complaints: terminal Preparing to replace linux-image-3.2.0-4-amd64 3.2.46-1 (using .../linux-image-3.2.0-4-amd64_3.2.46-1+deb7u1_amd64.deb) ... Unpacking replacement linux-image-3.2.0-4-amd64 ... Examining /etc/kernel/postrm.d . run-parts: executing /etc/kernel/postrm.d/initramfs-tools 3.2.0-4-amd64 /boot/vmlinuz-3.2.0-4-amd64 run-parts: executing /etc/kernel/postrm.d/zz-update-grub 3.2.0-4-amd64 /boot/vmlinuz-3.2.0-4-amd64 Preparing to replace linux-libc-dev:amd64 3.2.46-1 (using .../linux-libc-dev_3.2.46-1+deb7u1_amd64.deb) ... Unpacking replacement linux-libc-dev:amd64 ... Setting up linux-image-3.2.0-4-amd64 (3.2.46-1+deb7u1) ... Running depmod. Examining /etc/kernel/postinst.d. run-parts: executing /etc/kernel/postinst.d/initramfs-tools 3.2.0-4-amd64 /boot/vmlinuz-3.2.0-4-amd64 update-initramfs: Generating /boot/initrd.img-3.2.0-4-amd64 run-parts: executing /etc/kernel/postinst.d/pm-utils 3.2.0-4-amd64 /boot/vmlinuz-3.2.0-4-amd64 run-parts: executing /etc/kernel/postinst.d/zz-update-grub 3.2.0-4-amd64 /boot/vmlinuz-3.2.0-4-amd64 Generating grub.cfg ... Found background image: /usr/share/images/desktop-base/desktop-grub.png Found linux image: /boot/vmlinuz-3.2.0-4-amd64 Found initrd image: /boot/initrd.img-3.2.0-4-amd64 /dev/dm-0: read failed after 0 of 4096 at 22028419072: Input/output error /dev/dm-0: read failed after 0 of 4096 at 22028476416: Input/output error /dev/dm-0: read failed after 0 of 4096 at 0: Input/output error /dev/dm-0: read failed after 0 of 4096 at 4096: Input/output error /dev/dm-1: read failed after 0 of 4096 at 6324944896: Input/output error /dev/dm-1: read failed after 0 of 4096 at 6325002240: Input/output error . /dev/dm-8: read failed after 0 of 4096 at 4096: Input/output error /dev/sdf: read failed after 0 of 4096 at 0: Input/output error /dev/sdf: read failed after 0 of 4096 at 120034033664: Input/output error /dev/sdf: read failed after 0 of 4096 at 120034115584: Input/output error /dev/sdf: read failed after 0 of 4096 at 4096: Input/output error /dev/sdf1: read failed after 0 of 4096 at 2097348608: Input/output error /dev/sdf1: read failed after 0 of 4096 at 2097405952: Input/output error /dev/sdf1: read failed after 0 of 4096 at 0: Input/output error /dev/sdf1: read failed after 0 of 4096 at 4096: Input/output error /dev/sdf5: read failed after 0 of 2048 at 4096: Input/output error Couldn't find device with uuid GKasb9-Qo8q-vC83-S0N7-cvUd-nE0J-EEeMgv. Couldn't find device with uuid eDiLHt-Pzom-tjdr-Ky12-Z6Gx-o3Iz-lYh1wL. rmdir: failed to remove `/var/lib/os-prober/mount': Device or resource busy rmdir: failed to remove `/var/lib/os-prober/mount': Device or resource busy rmdir: failed to remove `/var/lib/os-prober/mount': Device or resource busy rmdir: failed to remove `/var/lib/os-prober/mount': Device or resource busy rmdir: failed to remove `/var/lib/os-prober/mount': Device or resource busy grub-probe: error: no such disk. rmdir: failed to remove `/var/lib/os-prober/mount': Device or resource busy rmdir: failed to remove `/var/lib/os-prober/mount': Device or resource busy Found Ubuntu 13.04 (13.04) on /dev/sda1 Found Debian GNU/Linux (7.0) on /dev/sdd1 Found Debian GNU/Linux (wheezy/sid) on /dev/mapper/daisy-amd64 Found Debian GNU/Linux (7.0) on /dev/mapper/daisy-chroot Found Debian GNU/Linux (6.0.2) on /dev/mapper/daisy-root_rescue done Setting up linux-libc-dev:amd64 (3.2.46-1+deb7u1) ... /terminal Does anyone know what's going on, or if I should be concerned? I think all the errors are associated with update-grub. My system is currently a hodge-podge as a result of earlier hardware failure. It shipped with a SSD with Ubuntu installed; I added lots of hard drives from the failed system; some of those drives are in a Vantec enclosure connected by USB. I'm using lvm and luks crypto. Thanks. Ross Boylan -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1377794301.3875.32.camel@localhost
