| |
|
 |
|
 |
|
|
|
| |
|
|
xen-users
[Xen-users] Re: Major problems with 2.0.7 and SATA drives
Ralph,
checked the drive with dd, tried to read everything, also checked it with
badblocks, nothing shows up. The problem is, when the error occurs, it
doesn't do it on the same sectors, it's always different, and now I have a
suspicion that it always happens when there is high throughput to the disk,
it happened yesterday twice on a box when I was trying to rsync from a
different machine and write on this one.
Thanks,
Alex
Ralph Passgang writes:
Hi,
ata1: status=0x51 { DriveReady SeekComplete Error }
ata1: error=0x04 { DriveStatusError }
this is usually a warning that only comes if the harddrive is really broken
(and cannot read/write some blocks). I saw this message a lot in the last
time and every time the diskdrive was really broken. But I never saw this in
on a xen host. So maybe it's _only_ a xen problem and not a hw problem, but
you should check.
To be sure you should check the harddrive with a special testing tool. All
major companies that sell harddrive have their own tool. I guess WD has a
similar tool anywhere on their webpage.
--Ralph
Am Mittwoch, 21. September 2005 13:02 schrieb Ernst Bachmann:
On Wednesday 21 September 2005 12:47, Alexander wrote:
> Hello everyone,
>
> I'm hoping to find an answer to my problem here. Currently I'm installing
> xen 2.0.7 on 30 dual opteron machines with 4GB memory. The machines have
> Tyan K8SR as motherboard with Silicon Image 3114 chip sata controler and
> 2 x 300 GB Western Digital SATA drives. Each xen server has 5 domUs,
> where some of them have high traffic and thus require high disk usage. On
> certain machines, I'm experiencing the following problem, after a while,
> I get this error in dom0's dmesg:
>
> TA: abnormal status 0xD0 on port 0xD080EC87
> ATA: abnormal status 0xD0 on port 0xD080EC87
> ATA: abnormal status 0xD0 on port 0xD080EC87
> ata1: command 0x35 timeout, stat 0x51 host_stat 0x61
> ata1: status=0x51 { DriveReady SeekComplete Error }
> ata1: error=0x04 { DriveStatusError }
Could you check /proc/interrupts if your SATA IRQ's are shared with some
other hardware, maybe the USB-Controller?
Oh, and with your hardware, you'd maybe want to consider running xen-3
(unstable) instead of xen-2.0.7, so you can get access to all your memory
(with 64 bit mode or PAE)
/Ernst
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
|
|
| |
|
Home