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@centos.org [mailto:centos-virt-bounces@centos.org] On Behalf Of Ben M. Sent: Monday, January 04, 2010 1:36 PM To: centos-virt@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@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.
A few months, these are the newer Velociraptors, almost cool to the touch.
Raid1 nvidia fakeraid via dmraid.
The images and vms are on separate drives, also mirrored on nvidia mobo raid.
So far my list is this:
- CentOS 5.4 dvd - Spare identical Velociraptor - Terabyte external USB drive. - BackTrack (or any other suggestions?)
From what I garner from my office is that it hits BOOT (grub) but is erroring on a bad or duplicate block.
I wonder if I had a "Time went backwards" error on the year turnover or something.
Other errors reported over the phone:
"(smp -alternatives off)" followed by "acpi: core revision 20060707"
I asked them to hit the F1 key, to see if they could get into bios, but I think it was too fast for them as they kept hitting grub and what they read to me over the phone sounded like the grub.conf file was fine.
compdoc wrote:
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@centos.org [mailto:centos-virt-bounces@centos.org] On Behalf Of Ben M. Sent: Monday, January 04, 2010 1:36 PM To: centos-virt@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@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.
CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
--- On Mon, 1/4/10, Ben M. centos@rivint.com wrote:
From: Ben M. centos@rivint.com Subject: [CentOS-virt] Xen box down To: centos-virt@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.
Thanks, I have heard of that issue. I will put that on my checklist.
Grub is accessible, so I can try a menu change from there.
Mr. X wrote:
--- On Mon, 1/4/10, Ben M. centos@rivint.com wrote:
From: Ben M. centos@rivint.com Subject: [CentOS-virt] Xen box down To: centos-virt@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.
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. :)
What, you use a term program to connect?
-----Original Message----- From: centos-virt-bounces@centos.org [mailto:centos-virt-bounces@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 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. :)
Hi,
On 01/05/2010 03:42 AM, compdoc wrote:
What, you use a term program to connect?
invest in a null-modem cable and get serial console redirection setup between pairs of machines. :)
Try not top posting please.
Also, yes, I use a term program to connect - either 'cu' from the uucp package or just plain minicom. I only have 2 such 'cross wired console pairs' of machines now ( so 4 in all ). Most of the rest have proper lights out management and I run a private management network ( or try to anyway )
-
Ben M. -
compdoc -
Karanbir Singh -
Mr. X