My stock CentOS 5.4 box won't come up after a reboot as reported from my office. Error is: "duplicate or bad block in use" Before rebooting xm dmsg had printk suppressed messages. The box is remote, 2 hour drive. Some advice on what hardware to bring with me and how to approach this via fsck would be welcome. Its an nvidia dmraid boot on WD Velocirapters. And Happy New Year to all. - Ben M.
Well, I'm not sure this is the best place to ask for help with hardware issues, but it does sound like a problem with at least one of your hard drives. Older raptors ran pretty hot and needed good cooling. WD's newer drives run cool. Hopefully, your raid is a mirror or a raid 5. The raid controllers built into motherboards aren't always the best way to go - how long has yours been running? Also hope you've created backup images... -----Original Message----- From: centos-virt-bounces at centos.org [mailto:centos-virt-bounces at centos.org] On Behalf Of Ben M. Sent: Monday, January 04, 2010 1:36 PM To: centos-virt at centos.org Subject: [CentOS-virt] Xen box down My stock CentOS 5.4 box won't come up after a reboot as reported from my office. Error is: "duplicate or bad block in use" Before rebooting xm dmsg had printk suppressed messages. The box is remote, 2 hour drive. Some advice on what hardware to bring with me and how to approach this via fsck would be welcome. Its an nvidia dmraid boot on WD Velocirapters. And Happy New Year to all. - Ben M. _______________________________________________ CentOS-virt mailing list CentOS-virt at centos.org http://lists.centos.org/mailman/listinfo/centos-virt __________ Information from ESET NOD32 Antivirus, version of virus signature database 4743 (20100104) __________ The message was checked by ESET NOD32 Antivirus. http://www.eset.com
--- On Mon, 1/4/10, Ben M. <centos at rivint.com> wrote:> From: Ben M. <centos at rivint.com> > Subject: [CentOS-virt] Xen box down > To: centos-virt at centos.org > Date: Monday, January 4, 2010, 12:36 PM > My stock CentOS 5.4 box won't come up > after a reboot as reported from my > office. > > Error is: "duplicate or bad block in use" > > Before rebooting xm dmsg had printk suppressed messages. > > The box is remote, 2 hour drive. Some advice on what > hardware to bring > with me and how to approach this via fsck would be > welcome. > > Its an nvidia dmraid boot on WD Velocirapters.Was there a kernel update? Sometimes the new initrd does not support dmraid. If this is applicable, boot into the old working kernel and run mkinitrd against the new kernel, reboot and x-fingers. This has worked for me in the past. My 18 yo kid has an ich5 Raid0 dual boot of Winxp/Fedora going for almost 4 years. Once when updating the kernel it was necessary to rebuild the initrd. -- Mark
On 04/01/10 20:36, Ben M. wrote:> The box is remote, 2 hour drive. Some advice on what hardware to bring > with me and how to approach this via fsck would be welcome.If you have more than 1 machine in the same facility, but dont have lights-out / ipmi console on the box then now would be a good time to invest in a null-modem cable and get serial console redirection setup between pairs of machines. :) -- Karanbir Singh kbsingh at karan.org | http://www.karan.org/ | twitter.com/kbsingh ICQ: 2522219 | Yahoo IM: z00dax | Gtalk: z00dax GnuPG Key : http://www.karan.org/publickey.asc
----- "Ben M." <centos at rivint.com> wrote:> Error is: "duplicate or bad block in use"It's probably just that fsck can't automatically fix some dirtiness and not a big deal. If you aren't prompted for a password or to log in to fix manually, get to the grub menu, edit the grub command line, stick ``single'' and/or ``init=/bin/sh'' on the end, boot, and run fsck manually. If you just want the machine up in a possibly slightly fucked state, just answer "yes" to everything. If not and you care a little bit about maybe getting some data back, see the next paragraph. (It's usually not that bad unless you have a skilled enemy or very bad luck.) You can probably have someone do all of it over the phone. If it doesn't even get that far or fsck can't fix it automatically, you're probably screwed. Whenever that has happened to me, I just do a block level dump of the partition/disk and recover from that image. It's a lot easier. Anyway, it is probably fine. If it isn't, you can always try pulling each of the disks or setting it back to use a single disk to try and isolate the problem. Also, switch to MD RAID. :) -- Christopher G. Stach II http://ldsys.net/~cgs/
What, you use a term program to connect? -----Original Message----- From: centos-virt-bounces at centos.org [mailto:centos-virt-bounces at centos.org] On Behalf Of Karanbir Singh Sent: Monday, January 04, 2010 6:44 PM To: Discussion about the virtualization on CentOS Subject: Re: [CentOS-virt] Xen box down On 04/01/10 20:36, Ben M. wrote:> The box is remote, 2 hour drive. Some advice on whathardware to bring> with me and how to approach this via fsck would bewelcome. If you have more than 1 machine in the same facility, but dont have lights-out / ipmi console on the box then now would be a good time to invest in a null-modem cable and get serial console redirection setup between pairs of machines. :) -- Karanbir Singh kbsingh at karan.org | http://www.karan.org/ | twitter.com/kbsingh ICQ: 2522219 | Yahoo IM: z00dax | Gtalk: z00dax GnuPG Key : http://www.karan.org/publickey.asc _______________________________________________ CentOS-virt mailing list CentOS-virt at centos.org http://lists.centos.org/mailman/listinfo/centos-virt __________ Information from ESET NOD32 Antivirus, version of virus signature database 4743 (20100104) __________ The message was checked by ESET NOD32 Antivirus. http://www.eset.com