Re: Understanding output from update-grub with md
Solved this one. Turns out I just needed to do grub-install on the old partitions. They must have had a stale version of grub. On Mon, Feb 10, 2014 at 7:53 PM, Ari Epstein wrote: > Hi all, > > Trying this again. I have a server with / (including /boot) on a md, > RAID1 device. Or so I thought. After updating installing latest 7.4 > kernel and rebooting I noticed it was running an older kernel. Output from > update-grub suggested that two unused spares somehow had older versions of > the / partition. I added them back as hot spares and then made them > mirrors of the current / partition (which should have the updated kernel on > it), but the error messages I have got from update-grub since have gone > from disturbing to just plain weird. Have a look at the attachment. > > I am guessing GRUB is working off an old map of partitions, but don't > understand enough of how it works to get any further than that. Any advice > or pointers to decent documentation appreciated! >
Re: GRUB seems to confuse md boot device and its spares
A footnote to this. I did mdadm --manage /dev/md0 --add /dev/sda1 and mdadm --manage /dev/md0 --add /dev/sdb1, and now the output from update grub is different: error: superfluous RAID member (2 found). error: superfluous RAID member (2 found). error: disk missing. error: disk missing. error: superfluous RAID member (2 found). error: superfluous RAID member (2 found). error: disk missing. error: disk missing. Generating grub.cfg ... Found linux image: /boot/vmlinuz-3.2.0-4-amd64 Found initrd image: /boot/initrd.img-3.2.0-4-amd64 error: superfluous RAID member (2 found). error: superfluous RAID member (2 found). error: disk missing. error: disk missing. error: superfluous RAID member (2 found). error: superfluous RAID member (2 found). error: disk missing. error: disk missing. error: superfluous RAID member (2 found). error: superfluous RAID member (2 found). error: disk missing. error: disk missing. /usr/sbin/grub-probe: error: disk missing. Found linux image: /boot/vmlinuz-2.6.32-5-amd64 Found initrd image: /boot/initrd.img-2.6.32-5-amd64 Found linux image: /boot/vmlinuz-2.6.32-trunk-amd64 Found initrd image: /boot/initrd.img-2.6.32-trunk-amd64 error: superfluous RAID member (2 found). error: superfluous RAID member (2 found). error: disk missing. error: disk missing. error: superfluous RAID member (2 found). error: superfluous RAID member (2 found). error: disk missing. error: disk missing. error: superfluous RAID member (2 found). error: superfluous RAID member (2 found). error: disk missing. error: disk missing. error: superfluous RAID member (2 found). error: superfluous RAID member (2 found). error: disk missing. error: disk missing. Found Debian GNU/Linux (7.0) on /dev/sda1 error: superfluous RAID member (2 found). error: superfluous RAID member (2 found). error: disk missing. error: disk missing. error: superfluous RAID member (2 found). error: superfluous RAID member (2 found). error: disk missing. error: disk missing. error: superfluous RAID member (2 found). error: superfluous RAID member (2 found). error: disk missing. error: disk missing. error: superfluous RAID member (2 found). error: superfluous RAID member (2 found). error: disk missing. error: disk missing. Found Debian GNU/Linux (7.2) on /dev/sdb1 error: superfluous RAID member (2 found). error: superfluous RAID member (2 found). error: disk missing. error: disk missing. error: superfluous RAID member (2 found). error: superfluous RAID member (2 found). error: disk missing. error: disk missing. error: superfluous RAID member (2 found). error: superfluous RAID member (2 found). error: disk missing. error: disk missing. error: superfluous RAID member (2 found). error: superfluous RAID member (2 found). error: disk missing. error: disk missing. Found Debian GNU/Linux (7.4) on /dev/sdc1 error: superfluous RAID member (2 found). error: superfluous RAID member (2 found). error: disk missing. error: disk missing. error: superfluous RAID member (2 found). error: superfluous RAID member (2 found). error: disk missing. error: disk missing. error: superfluous RAID member (2 found). error: superfluous RAID member (2 found). error: disk missing. error: disk missing. error: superfluous RAID member (2 found). error: superfluous RAID member (2 found). error: disk missing. error: disk missing. Found Debian GNU/Linux (7.4) on /dev/sdd1 error: superfluous RAID member (2 found). error: superfluous RAID member (2 found). error: disk missing. error: disk missing. error: superfluous RAID member (2 found). error: superfluous RAID member (2 found). error: disk missing. error: disk missing. error: superfluous RAID member (2 found). error: superfluous RAID member (2 found). error: disk missing. error: disk missing. error: superfluous RAID member (2 found). error: superfluous RAID member (2 found). error: disk missing. error: disk missing. done On Sun, Feb 9, 2014 at 8:32 AM, Ari Epstein wrote: > I'm having peculiar difficulties getting grub to boot from a RAID1 md. > The machine has four drives, and the md (which contains / as well as > /boot) is on sdc1 and sdd1. sda1 and sdb1 were once configured as spares > though at the moment they are not connected to the raid at all. The > grub.cfg has the correct UUID for the md. > Today I upgraded to the latest 7.4 kernel (3.2.54-2) and rebooted. The > system appeared to boot correctly, but I noticed the kernel is the same one > that was running before (3.2.41-2). > > The output from update-grub suggests it is detecting older installations > of debian, which I suspect are in sda1 and sdb1. I am guessing that > somehow grub is loading from those unused spare partitions instead of the > ones in active use, but could use some help confirming this/understanding > how I can fix it. Any ideas? > > Here's the update-grub output: > > error: superfluous RAID member (2 found). > error: superfluous RAID member (2 found). > error: superfluous RAID memb
GRUB seems to confuse md boot device and its spares
I'm having peculiar difficulties getting grub to boot from a RAID1 md. The machine has four drives, and the md (which contains / as well as /boot) is on sdc1 and sdd1. sda1 and sdb1 were once configured as spares though at the moment they are not connected to the raid at all. The grub.cfg has the correct UUID for the md. Today I upgraded to the latest 7.4 kernel (3.2.54-2) and rebooted. The system appeared to boot correctly, but I noticed the kernel is the same one that was running before (3.2.41-2). The output from update-grub suggests it is detecting older installations of debian, which I suspect are in sda1 and sdb1. I am guessing that somehow grub is loading from those unused spare partitions instead of the ones in active use, but could use some help confirming this/understanding how I can fix it. Any ideas? Here's the update-grub output: error: superfluous RAID member (2 found). error: superfluous RAID member (2 found). error: superfluous RAID member (2 found). error: superfluous RAID member (2 found). Generating grub.cfg ... error: superfluous RAID member (2 found). error: superfluous RAID member (2 found). error: superfluous RAID member (2 found). error: superfluous RAID member (2 found). error: superfluous RAID member (2 found). error: superfluous RAID member (2 found). error: superfluous RAID member (2 found). error: superfluous RAID member (2 found). error: superfluous RAID member (2 found). error: superfluous RAID member (2 found). error: superfluous RAID member (2 found). error: superfluous RAID member (2 found). error: superfluous RAID member (2 found). error: superfluous RAID member (2 found). error: superfluous RAID member (2 found). error: superfluous RAID member (2 found). error: superfluous RAID member (2 found). error: superfluous RAID member (2 found). error: superfluous RAID member (2 found). error: superfluous RAID member (2 found). error: superfluous RAID member (2 found). error: superfluous RAID member (2 found). Found linux image: /boot/vmlinuz-3.2.0-4-amd64 Found initrd image: /boot/initrd.img-3.2.0-4-amd64 error: superfluous RAID member (2 found). error: superfluous RAID member (2 found). error: superfluous RAID member (2 found). error: superfluous RAID member (2 found). error: superfluous RAID member (2 found). error: superfluous RAID member (2 found). error: superfluous RAID member (2 found). error: superfluous RAID member (2 found). Found linux image: /boot/vmlinuz-2.6.32-5-amd64 Found initrd image: /boot/initrd.img-2.6.32-5-amd64 Found linux image: /boot/vmlinuz-2.6.32-trunk-amd64 Found initrd image: /boot/initrd.img-2.6.32-trunk-amd64 error: superfluous RAID member (2 found). error: superfluous RAID member (2 found). error: superfluous RAID member (2 found). error: superfluous RAID member (2 found). error: superfluous RAID member (2 found). error: superfluous RAID member (2 found). error: superfluous RAID member (2 found). error: superfluous RAID member (2 found). error: superfluous RAID member (2 found). error: superfluous RAID member (2 found). Found Debian GNU/Linux (7.0) on /dev/sda1 error: superfluous RAID member (2 found). error: superfluous RAID member (2 found). error: superfluous RAID member (2 found). error: superfluous RAID member (2 found). error: superfluous RAID member (2 found). error: superfluous RAID member (2 found). error: superfluous RAID member (2 found). error: superfluous RAID member (2 found). Found Debian GNU/Linux (7.2) on /dev/sdb1 error: superfluous RAID member (2 found). error: superfluous RAID member (2 found). error: superfluous RAID member (2 found). error: superfluous RAID member (2 found). error: superfluous RAID member (2 found). error: superfluous RAID member (2 found). error: superfluous RAID member (2 found). error: superfluous RAID member (2 found). Found Debian GNU/Linux (7.4) on /dev/sdc1 error: superfluous RAID member (2 found). error: superfluous RAID member (2 found). error: superfluous RAID member (2 found). error: superfluous RAID member (2 found). error: superfluous RAID member (2 found). error: superfluous RAID member (2 found). error: superfluous RAID member (2 found). error: superfluous RAID member (2 found). Found Debian GNU/Linux (7.4) on /dev/sdd1 error: superfluous RAID member (2 found). error: superfluous RAID member (2 found). error: superfluous RAID member (2 found). error: superfluous RAID member (2 found). error: superfluous RAID member (2 found). error: superfluous RAID member (2 found). error: superfluous RAID member (2 found). error: superfluous RAID member (2 found). done
Re: Diagnosing kernel panic involving fglrx
One change I made shortly before the problems started that might be relevant: I enabled i386 architecture support (it's amd64 laptop). On Tue, Jun 4, 2013 at 7:36 AM, Ari Epstein wrote: > Hi all, > > Got a new laptop and installed wheezy a few weeks ago. I noticed the HDMI > audio was not working, and figured it was a limitation in the fglrx driver > and it seemed otherwise to run well. Starting yesterday, however, I have > frequent but not consistent kernel panics during the boot process that seem > to involve support for that feature. Sometimes it boots without any audio > (there is another integrated audio device), sometimes with, sometimes it > does not boot at all. Never had to debug something like this before so some > pointers about how to go about it are appreciated! dmesg logs attached for > occassions that it booted with audio and without audio. > -- Ari Epstein 311 W Buffalo St Ithaca, NY 14850-4123 aepstein...@gmail.com 607.222.5116
[SOLVED] Re: libvirt/kvm virtual hosts unbootable after upgrading hypervisor to wheezy from squeeze
Thanks Zenaan. Had a lucky break: I changed the virtual disks from SCSI to SATA using virt-manager and suddenly they were bootable again. On Wed, May 15, 2013 at 9:00 PM, Zenaan Harkness wrote: > I can only give wild suggests: read errata; use (low-level) tools to > check disk availability; try running your vm on a test box - you did > test a migration before deploying the upgrade, hint hint :) > Good luck > Zenaan > > > -- > 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/caosgnssrwmhins3m+xyes_hwauyo10qyas+extsoelwrvpd...@mail.gmail.com > >
Re: libvirt/kvm virtual hosts unbootable after upgrading hypervisor to wheezy from squeeze
Belatedly realizing the VM configuration would probably be helpful in diagnosing: vm01 0026ba80-bdd4-ffb0-e120-3cc331bfaebb 1310720 1310720 2 hvm destroy restart restart /usr/bin/kvm On Wed, May 15, 2013 at 5:19 PM, Ari Epstein wrote: > Hi all, > > I have hardly had to touch libvirt/kvm since I set it up for a server > several years ago, but need to learn fast after a wheezy upgrade has made > them unbootable. I can connect to the virtual hosts through virt-manager > and see that the virtual firmware is unable to find any bootable media. I > believe I have a pretty plain vanilla libvirt setup. The hosts are all > ext4 on kpartx on LVM. No settings changed during the upgrade. Any advice > appreciated! > > -- > > Ari Epstein > > 311 W Buffalo St > Ithaca, NY 14850-4123 > > aepstein...@gmail.com > 607.222.5116 > -- Ari Epstein 311 W Buffalo St Ithaca, NY 14850-4123 aepstein...@gmail.com 607.222.5116
libvirt/kvm virtual hosts unbootable after upgrading hypervisor to wheezy from squeeze
Hi all, I have hardly had to touch libvirt/kvm since I set it up for a server several years ago, but need to learn fast after a wheezy upgrade has made them unbootable. I can connect to the virtual hosts through virt-manager and see that the virtual firmware is unable to find any bootable media. I believe I have a pretty plain vanilla libvirt setup. The hosts are all ext4 on kpartx on LVM. No settings changed during the upgrade. Any advice appreciated! -- Ari Epstein 311 W Buffalo St Ithaca, NY 14850-4123 aepstein...@gmail.com 607.222.5116
Re: HELP! Boot stops at chkrootfs.sh and can't fsck: /sbin/fsck: cannot execute binary file
Thanks for the help. Not quite sure if I'm providing the right info, but... 1. I don't know any initrd files in the dom1, only the domU. The link to the initrd.gz is (from the xen ".cfg"): /boot/ initrd.img-2.6.18-6-xen-amd64 2. The rootdelay=30 did not resolve it. Here's the configuration for the dom1 (xen1). -A # # Configuration file for the Xen instance xen1, created on # Fri Oct 13 11:00:26 2006. # # # Kernel + memory size # kernel = '/boot/vmlinuz-2.6.18-6-xen-amd64' ramdisk = '/boot/initrd.img-2.6.18-6-xen-amd64' extra = 'rootdelay=30' memory = '512' # # Disk device(s). # root= '/dev/sda1 ro' disk= [ 'phy:vg00/xen1-disk,sda1,w', 'phy:vg00/xen1-swap,sda2,w' ] # # Hostname # name= 'xen1' # # Networking # vif = [ 'ip=128.253.16.121' ] # # Behaviour # on_poweroff = 'destroy' on_reboot = 'restart' on_crash= 'restart' On Jan 31, 2008, at 7:47 PM, martin f krafft wrote: also sprach Ari Epstein <[EMAIL PROTECTED]> [2008.02.01.1056 +1100]: Console output is as follows: Can you mount the filesystem and provide me with a link to the initrd.gz file for the kernel? The RAID does not start and it may be because the disk names have changed. Also, try adding rootdelay=30 to the kernel command line and see if that fixes it. -- .''`. martin f. krafft <[EMAIL PROTECTED]> : :' : proud Debian developer, author, administrator, and user `. `'` http://people.debian.org/~madduck - http://debiansystem.info `- Debian - when you have better things to do than fixing systems one morning i shot an elephant in my pyjamas. how he got into my pyjamas i'll never know. -- groucho marx
HELP! Boot stops at chkrootfs.sh and can't fsck: /sbin/fsck: cannot execute binary file
trans len 1024, max batch 900, max commit age 30, max trans age 30 ReiserFS: sda1: checking transaction log (sda1) ReiserFS: sda1: Using r5 hash to sort names Begin: Running /scripts/local-bottom ... Done. Done. Begin: Running /scripts/init-bottom ... Done. modprobe: FATAL: Could not load /lib/modules/2.6.18-6-xen-amd64/ modules.dep: No such file or directory modprobe: FATAL: Could not load /lib/modules/2.6.18-6-xen-amd64/ modules.dep: No such file or directory INIT: version 2.86 booting * Mount point '/dev/shm' does not exist. Skipping mount. Activating swap...Adding 1048568k swap on /dev/sda2. Priority:-1 extents:1 across:1048568k done. Checking root file system...modprobe: FATAL: Could not load /lib/ modules/2.6.18-6-xen-amd64/modules.dep: No such file or directory modprobe: FATAL: Could not load /lib/modules/2.6.18-6-xen-amd64/ modules.dep: No such file or directory /etc/rcS.d/S10checkroot.sh: line 266: /sbin/logsave: cannot execute binary file failed (code 126). * An automatic file system check (fsck) of the root filesystem failed. A manual fsck must be performed, then the system restarted. The fsck should be performed in maintenance mode with the root filesystem mounted in read-only mode. * The root filesystem is currently mounted in read-only mode. A maintenance shell will now be started. After performing system maintenance, press CONTROL-D to terminate the maintenance shell and restart the system. Press enter for maintenance (or type Control-D to continue): xen1:~# fsck /dev/sda1 modprobe: FATAL: Could not load /lib/modules/2.6.18-6-xen-amd64/ modules.dep: No such file or directory modprobe: FATAL: Could not load /lib/modules/2.6.18-6-xen-amd64/ modules.dep: No such file or directory bash: /sbin/fsck: cannot execute binary file - Ari Epstein Assistant Director Office of Assemblies 109 Day Hall Cornell University Ithaca, NY 14853 tel. 607 254 5161 mob. 607 222 5116 fax. 607 255 2182 [EMAIL PROTECTED]
