Re: [gentoo-user] Re: Harddisk trouble ... or not yet?
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:80:00:3f:c1/00:00:00:00:00/e0 tag 0 dma 65536 in
res 51/84:4f:00:3f:c1/00:00:00:00:00/e0 Emask 0x10 (ATA bus error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { ICRC ABRT }
ata1: soft resetting link
ata1.00: configured for UDMA/33
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
I think you have driver issues. Might also be the cabling, but I doubt
it as faulty SATA cables are in my experience quite rare.
WD drives are known not to get along too well with VIA SATA1 controllers:
http://www.viaarena.com/forums/showthread.php?t=38871
http://forums.gentoo.org/viewtopic-t-794855.html
What kernel version are you using?
What does the kernel say when it first detects the disk?
Do you get the same errors under a recent kernel (try the latest gentoo
install cd) ?
My experience with WD advanced format drives has been positive so far,
especially considering how cheap they are... The only gripe I have is
that they report not only having a 512B *logical* sector size in the
response to ATA INFO commands (which is fine, as they have a translation
layer), but also a 512B *physical* sector size, which is wrong and
causes partitioning tools to use the wrong alignment.
All the five 1TB drives I have behave this way, and from what I read
this is not an isolated behavior...
andrea
Re: [gentoo-user] Re: Harddisk trouble ... or not yet?
On Samstag 29 Mai 2010, Andrea Conti wrote:
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:80:00:3f:c1/00:00:00:00:00/e0 tag 0 dma 65536 in
res 51/84:4f:00:3f:c1/00:00:00:00:00/e0 Emask 0x10 (ATA bus
error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { ICRC ABRT }
ata1: soft resetting link
ata1.00: configured for UDMA/33
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
I think you have driver issues. Might also be the cabling, but I doubt
it as faulty SATA cables are in my experience quite rare.
in my experience they are everything but rare. I had several defective cables
- myself and friends of mine.
Re: [gentoo-user] Re: Harddisk trouble ... or not yet?
Andrea Conti a...@alyf.net [10-05-29 10:08]:
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:80:00:3f:c1/00:00:00:00:00/e0 tag 0 dma 65536 in
res 51/84:4f:00:3f:c1/00:00:00:00:00/e0 Emask 0x10 (ATA bus error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { ICRC ABRT }
ata1: soft resetting link
ata1.00: configured for UDMA/33
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
I think you have driver issues. Might also be the cabling, but I doubt
it as faulty SATA cables are in my experience quite rare.
WD drives are known not to get along too well with VIA SATA1 controllers:
http://www.viaarena.com/forums/showthread.php?t=38871
http://forums.gentoo.org/viewtopic-t-794855.html
What kernel version are you using?
What does the kernel say when it first detects the disk?
Do you get the same errors under a recent kernel (try the latest gentoo
install cd) ?
My experience with WD advanced format drives has been positive so far,
especially considering how cheap they are... The only gripe I have is
that they report not only having a 512B *logical* sector size in the
response to ATA INFO commands (which is fine, as they have a translation
layer), but also a 512B *physical* sector size, which is wrong and
causes partitioning tools to use the wrong alignment.
All the five 1TB drives I have behave this way, and from what I read
this is not an isolated behavior...
andrea
Hi Andrea,
I tried these kernels (all vanilla):
2.6.32.13
2.6.33.5
2.6.34.0
This is, what I cut from the dmegs out (I hope to get all relevant
infos...if you missing something, I save the complete dmesg output to
disk for later refrence...):
sata_via :00:0f.0: version 2.6
sata_via :00:0f.0: PCI INT B - GSI 20 (level, low) - IRQ 20
sata_via :00:0f.0: routed to hard irq line 10
scsi0 : sata_via
PM: Adding info for scsi:host0
PM: Adding info for No Bus:host0
scsi1 : sata_via
PM: Adding info for scsi:host1
PM: Adding info for No Bus:host1
ata1: SATA max UDMA/133 cmd 0xd000 ctl 0xc800 bmdma 0xb800 irq 20
ata2: SATA max UDMA/133 cmd 0xc400 ctl 0xc000 bmdma 0xb808 irq 20
pata_via :00:0f.1: version 0.3.4
pata_via :00:0f.1: PCI INT A - GSI 20 (level, low) - IRQ 20
scsi2 : pata_via
PM: Adding info for scsi:host2
PM: Adding info for No Bus:host2
scsi3 : pata_via
PM: Adding info for scsi:host3
PM: Adding info for No Bus:host3
ata3: PATA max UDMA/133 cmd 0x1f0 ctl 0x3f6 bmdma 0xfc00 irq 14
ata4: PATA max UDMA/133 cmd 0x170 ctl 0x376 bmdma 0xfc08 irq 15
skge :00:0a.0: PCI INT A - GSI 17 (level, low) - IRQ 17
skge :00:0a.0: PCI: Disallowing DAC for device
skge: 1.13 addr 0xf9c0 irq 17 chip Yukon-Lite rev 9
PM: Adding info for No Bus:eth0
skge :00:0a.0: eth0: addr 00:15:f2:18:b0:20
sky2: driver version 1.27
usbcore: registered new interface driver usblp
Aligment:
I used
fdisk -cu -S 56 /dev/sda
to align my partitions, which seems to work.
Do I have to replace my motherboard/graphics card/RAM/...
only because WD cannot talk to and/or vice versa?
By the way:
Can I use PCI cards on newer motherboards with PCIe-slots???
Best regards,
mcc
--
Please don't send me any Word- or Powerpoint-Attachments
unless it's absolutely neccessary. - Send simply Text.
See http://www.gnu.org/philosophy/no-word-attachments.html
In a world without fences and walls nobody needs gates and windows.
Re: [gentoo-user] Re: Harddisk trouble ... or not yet?
On Saturday 29 May 2010 10:16:39 Volker Armin Hemmann wrote:
On Samstag 29 Mai 2010, Andrea Conti wrote:
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:80:00:3f:c1/00:00:00:00:00/e0 tag 0 dma 65536 in
res 51/84:4f:00:3f:c1/00:00:00:00:00/e0 Emask 0x10 (ATA bus
error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { ICRC ABRT }
ata1: soft resetting link
ata1.00: configured for UDMA/33
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
I think you have driver issues. Might also be the cabling, but I doubt
it as faulty SATA cables are in my experience quite rare.
in my experience they are everything but rare. I had several defective
cables - myself and friends of mine.
I find SATA connectors are what gives trouble. All fixed nicely with a dab of
hot glue, but I ask, why should that be necessary?
--
alan dot mckinnon at gmail dot com
Re: [gentoo-user] Re: Harddisk trouble ... or not yet?
Hi, I tried these kernels (all vanilla): 2.6.32.13 2.6.33.5 2.6.34.0 So it's not a known problem that has been fixed. Just a wild guess... can you try recompiling the kernel *without* pata_via? Some people have reported having problems with sata drives on VIA controllers when pata_via is also loaded. If you need to access devices on the PATA ports, you can use the the old non-libata via82cxxx IDE driver. This is, what I cut from the dmegs out (I hope to get all relevant infos...if you missing something, I save the complete dmesg output to disk for later refrence...): This is just the controller initialization part, it does not include the actual information about the drives. Look for something like ata1: SATA link up... a bit further in the log. fdisk -cu -S 56 /dev/sda Well, fdisk -cu defaults to creating the first partition beginning at sector 2048, which is fine as it's divisible by 8 (and thus is aligned on a 4096-byte boundary). I don't think you need to specify the number of sectors per track. But this is not really relevant, as creating unaligned partitions merely results in lower performance, not DMA errors :) Do I have to replace my motherboard/graphics card/RAM/... only because WD cannot talk to and/or vice versa? If the pata_via trick above does not work, and an upgrade is out of question, my suggestion is to find a cheap PCI sata2 controller and to use that instead of the on-board sata ports. Can I use PCI cards on newer motherboards with PCIe-slots??? You cannot use PCI cards in PCIe slots, but most new motherboards still have at least one PCI slot. andrea
Re: [gentoo-user] Re: Harddisk trouble ... or not yet?
On Samstag 29 Mai 2010, Alan McKinnon wrote:
On Saturday 29 May 2010 10:16:39 Volker Armin Hemmann wrote:
On Samstag 29 Mai 2010, Andrea Conti wrote:
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:80:00:3f:c1/00:00:00:00:00/e0 tag 0 dma 65536 in
res 51/84:4f:00:3f:c1/00:00:00:00:00/e0 Emask 0x10 (ATA bus
error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { ICRC ABRT }
ata1: soft resetting link
ata1.00: configured for UDMA/33
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
I think you have driver issues. Might also be the cabling, but I doubt
it as faulty SATA cables are in my experience quite rare.
in my experience they are everything but rare. I had several defective
cables - myself and friends of mine.
I find SATA connectors are what gives trouble. All fixed nicely with a dab
of hot glue, but I ask, why should that be necessary?
a spec made to guarantee early hardware death - to keep sales up.
Re: [gentoo-user] Re: Harddisk trouble ... or not yet?
walt w41...@gmail.com [10-05-29 03:21]:
On 05/27/2010 06:54 PM, meino.cra...@gmx.de wrote:
ata1.00: configured for UDMA/33
I know nothing about the new large-sector disks, but the line above
makes
me worried that the disk driver doesn't know any more than I do :)
Anyone know if that is the expected response from the disk driver?
I played around a little more with this effects...
At the WD-site there is a paper (pdf), which describes how to
jumper the WD-SATAs to behave as SATA1 even if being SATA2, which
I did.
Then I checked the cableing again and booted the system from a sdb,
which is my old system disk which I previously (before this hassle)
to replace with the WD 1TB-disks, since on the old disk there was
not enoughspace anymore.
Then I mounted two partitions (root and an empty one) of the WD-drive
and copied the root to the empty partition by
cp -a src dest
The process starts and after some blinks of the HD-LED I got again
such in the kernel log:
(there is more things I wrote below this log... ;)
ata1.00: cmd c8/00:00:68:a1:61/00:00:00:00:00/e4 tag 0 dma 131072 in
res 51/84:df:68:a1:61/00:00:00:00:00/e4 Emask 0x10 (ATA bus error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { ICRC ABRT }
ata1: soft resetting link
ata1.00: configured for UDMA/33
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
ata1.00: BMDMA stat 0x5
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:00:68:79:7f/00:00:00:00:00/e4 tag 0 dma 131072 in
res 51/84:df:68:79:7f/00:00:00:00:00/e4 Emask 0x10 (ATA bus error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { ICRC ABRT }
ata1: soft resetting link
ata1.00: configured for UDMA/33
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
ata1.00: BMDMA stat 0x5
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:00:68:19:84/00:00:00:00:00/e4 tag 0 dma 131072 in
res 51/84:3f:68:19:84/00:00:00:00:00/e4 Emask 0x10 (ATA bus error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { ICRC ABRT }
ata1: soft resetting link
ata1.00: configured for UDMA/33
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
ata1.00: BMDMA stat 0x5
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:00:68:a8:85/00:00:00:00:00/e4 tag 0 dma 131072 in
res 51/84:8f:68:a8:85/00:00:00:00:00/e4 Emask 0x10 (ATA bus error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { ICRC ABRT }
ata1: soft resetting link
ata1.00: configured for UDMA/33
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
ata1.00: BMDMA stat 0x5
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:00:68:3b:86/00:00:00:00:00/e4 tag 0 dma 131072 in
res 51/84:8f:68:3b:86/00:00:00:00:00/e4 Emask 0x10 (ATA bus error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { ICRC ABRT }
ata1: soft resetting link
ata1.00: configured for UDMA/33
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
ata1.00: BMDMA stat 0x5
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:00:68:83:87/00:00:00:00:00/e4 tag 0 dma 131072 in
res 51/84:0f:68:83:87/00:00:00:00:00/e4 Emask 0x10 (ATA bus error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { ICRC ABRT }
ata1: soft resetting link
ata1.00: configured for UDMA/33
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
ata1.00: BMDMA stat 0x5
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:00:68:61:88/00:00:00:00:00/e4 tag 0 dma 131072 in
res 51/84:6f:68:61:88/00:00:00:00:00/e4 Emask 0x10 (ATA bus error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { ICRC ABRT }
ata1: soft resetting link
ata1.00: configured for UDMA/33
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
ata1.00: BMDMA stat 0x5
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:00:68:c7:89/00:00:00:00:00/e4 tag 0 dma 131072 in
res 51/84:df:68:c7:89/00:00:00:00:00/e4 Emask 0x10 (ATA bus error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { ICRC ABRT }
ata1: soft resetting link
ata1.00: configured for UDMA/33
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
ata1.00: BMDMA stat 0x5
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:00:68:72:8c/00:00:00:00:00/e4 tag 0 dma 131072 in
res 51/84:4f:68:72:8c/00:00:00:00:00/e4 Emask 0x10 (ATA bus error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { ICRC ABRT }
ata1: soft resetting link
ata1.00: configured for UDMA/33
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
ata1.00: BMDMA stat 0x5
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:00:68:1c:90/00:00:00:00:00/e4 tag 0 dma 131072 in
res 51/84:af:68:1c:90/00:00:00:00:00/e4 Emask 0x10 (ATA bus error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { ICRC ABRT }
ata1: soft resetting link
ata1.00: configured for UDMA/33
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
ata1.00: BMDMA stat 0x5
ata1.00:
Re: [gentoo-user] Re: Harddisk trouble ... or not yet?
On 27 May 2010, at 01:19, meino.cra...@gmx.de wrote: ... Is there any way to check the disk without damaging its contents? If you have copied from /dev/sda to /dev/sdb then `md5sum /dev/sda / dev/sdb` will compare both drives. You're probably safest to compare a partition at a time `md5sum /dev/sda1 /dev/sdb1` to make sure the free space at the end of the drive don't throw things off. I'm pretty sure I've used this successfully. Stroller.
Re: [gentoo-user] Re: Harddisk trouble ... or not yet?
I was more thinking of a tool, which test the whole disc surface and reports every bad sector. badblocks -wvs (which takes forever, but in my experience is quite good at make failing disks actually fail ;) During the test you can monitor the smart attributes (smartctl -A, esp. the reallocated sector count) to see what is actually going on. Warning: backup your data as badblocks in destructive mode will wipe the disk clean. Also, you can run a SMART offline long test (smartctl -t long), which will scan the whole surface. But on most disks the test stops at the first error, so you don't get a complete picture. Smarts is more of statistical kind: It counts events and tries to calculate dooms day from that ;) That's just a part of it. Attribute values and the error log actually provide useful information about the status of the disk. andrea
Re: [gentoo-user] Re: Harddisk trouble ... or not yet?
Andrea Conti a...@alyf.net [10-05-27 17:20]:
I was more thinking of a tool, which test the whole disc surface
and reports every bad sector.
badblocks -wvs (which takes forever, but in my experience is quite good
at make failing disks actually fail ;)
During the test you can monitor the smart attributes (smartctl -A, esp.
the reallocated sector count) to see what is actually going on.
Warning: backup your data as badblocks in destructive mode will wipe the
disk clean.
Also, you can run a SMART offline long test (smartctl -t long), which
will scan the whole surface. But on most disks the test stops at the
first error, so you don't get a complete picture.
Smarts is more of statistical kind: It counts events and tries
to calculate dooms day from that ;)
That's just a part of it. Attribute values and the error log actually
provide useful information about the status of the disk.
andrea
Badblocks is running since yesterday on one of both harrdisks (and is still
running...for more then 10 hours now (1TB to check)) and I
got thise errors visible via dmesg:
ata1.00: BMDMA stat 0x5
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:80:00:3f:c1/00:00:00:00:00/e0 tag 0 dma 65536 in
res 51/84:4f:00:3f:c1/00:00:00:00:00/e0 Emask 0x10 (ATA bus error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { ICRC ABRT }
ata1: soft resetting link
ata1.00: configured for UDMA/33
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
ata1.00: BMDMA stat 0x5
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:80:80:f5:c1/00:00:00:00:00/e0 tag 0 dma 65536 in
res 51/84:0f:80:f5:c1/00:00:00:00:00/e0 Emask 0x10 (ATA bus error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { ICRC ABRT }
ata1: soft resetting link
ata1.00: configured for UDMA/33
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
ata1.00: BMDMA stat 0x5
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:80:80:40:d4/00:00:00:00:00/e0 tag 0 dma 65536 in
res 51/84:6f:80:40:d4/00:00:00:00:00/e0 Emask 0x10 (ATA bus error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { ICRC ABRT }
ata1: soft resetting link
ata1.00: configured for UDMA/33
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
ata1.00: BMDMA stat 0x5
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:80:80:a1:40/00:00:00:00:00/e1 tag 0 dma 65536 in
res 51/84:2f:80:a1:40/00:00:00:00:00/e1 Emask 0x10 (ATA bus error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { ICRC ABRT }
ata1: soft resetting link
ata1.00: configured for UDMA/33
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
(I dont know, where the report sequence starts, so I put some
repetitions here in)
They do not grow in count and badblocks did not report anything
onto the console where I start it.
I started it with
solfire:/rootbadblocks -v -n /dev/sda
At midnight, the DSL connection had been cut by the provider
and automagically reestablished by my linux box, but I dont
think, that this has something do to with it.
Additionall smartd is running in the background...
Smartd's smartd.conf contains this (first try...;)
/dev/sda -a -d sat -o on
/dev/sdb -a -d sat -o on
What the heck is going on in my system?
Thanks a lot in advance for any help !
Best regards,
worried,
mcc
--
Please don't send me any Word- or Powerpoint-Attachments
unless it's absolutely neccessary. - Send simply Text.
See http://www.gnu.org/philosophy/no-word-attachments.html
In a world without fences and walls nobody needs gates and windows.
Re: [gentoo-user] Re: Harddisk trouble ... or not yet?
Grant Edwards grant.b.edwa...@gmail.com [10-05-26 17:19]: On 2010-05-26, meino.cra...@gmx.de meino.cra...@gmx.de wrote: [...] I have two WDC WD10EARS-00Y5B1 (pasted from hdparm -i) harddisk (1TB, advanced format 4096 kb sectors). [...] dd if=/dev/sda of=/dev/sdb bs=8192 which gave me a LOT of I/O errors after a short time. [...] From what kernel version the new advanced format of the hd is fully supported ? My understanding is that the new format doesn't cause I/O errors, just slower transfer rates if you format with disk clusters that aren't aligned on 4K boundaries. I'm not aware of any support in the kernel. Are there other reasons -- beside defective hardware -- for the failing dd and how can I fix them ? In my experience, I/O errors have always been hardware problems (usually a failing drive, but it could also be a faulty cable or connector). -- Grant Edwards grant.b.edwardsYow! PIZZA!! at gmail.com Hi If it happens again, I will try to save the error list and post it here... May be: The WD-harddiscs are SATA2 my controllers are only SATA1... is it this, which cause the problems? Best regards, mcc -- Please don't send me any Word- or Powerpoint-Attachments unless it's absolutely neccessary. - Send simply Text. See http://www.gnu.org/philosophy/no-word-attachments.html In a world without fences and walls nobody needs gates and windows.
Re: [gentoo-user] Re: Harddisk trouble ... or not yet?
On Mittwoch 26 Mai 2010, meino.cra...@gmx.de wrote: Grant Edwards grant.b.edwa...@gmail.com [10-05-26 17:19]: On 2010-05-26, meino.cra...@gmx.de meino.cra...@gmx.de wrote: [...] I have two WDC WD10EARS-00Y5B1 (pasted from hdparm -i) harddisk (1TB, advanced format 4096 kb sectors). [...] dd if=/dev/sda of=/dev/sdb bs=8192 which gave me a LOT of I/O errors after a short time. [...] From what kernel version the new advanced format of the hd is fully supported ? My understanding is that the new format doesn't cause I/O errors, just slower transfer rates if you format with disk clusters that aren't aligned on 4K boundaries. I'm not aware of any support in the kernel. Are there other reasons -- beside defective hardware -- for the failing dd and how can I fix them ? In my experience, I/O errors have always been hardware problems (usually a failing drive, but it could also be a faulty cable or connector). Hi If it happens again, I will try to save the error list and post it here... May be: The WD-harddiscs are SATA2 my controllers are only SATA1... is it this, which cause the problems? Best regards, mcc usually it shouldn't.
Re: [gentoo-user] Re: Harddisk trouble ... or not yet?
On Wed, 26 May 2010 19:59:32 +0200, Volker Armin Hemmann wrote: May be: The WD-harddiscs are SATA2 my controllers are only SATA1... is it this, which cause the problems? usually it shouldn't. It has done for me in the past. SATA2 drives usually have a jumper to switch them to SATA1. -- Neil Bothwick Q-Tip: When an omnipotent alien gives you advice. signature.asc Description: PGP signature
Re: [gentoo-user] Re: Harddisk trouble ... or not yet?
On Mittwoch 26 Mai 2010, Neil Bothwick wrote: On Wed, 26 May 2010 19:59:32 +0200, Volker Armin Hemmann wrote: May be: The WD-harddiscs are SATA2 my controllers are only SATA1... is it this, which cause the problems? usually it shouldn't. It has done for me in the past. SATA2 drives usually have a jumper to switch them to SATA1. that is why I used 'usually' and 'shouldn't'. But that is not a sata1 or sata2 jumper but a speed jumper.
Re: [gentoo-user] Re: Harddisk trouble ... or not yet?
On Wed, 26 May 2010 21:13:06 +0200, Volker Armin Hemmann wrote: that is why I used 'usually' and 'shouldn't'. Have you considered a career in politics? ;-) -- Neil Bothwick A clean desk is a sign of a cluttered desk drawer. signature.asc Description: PGP signature
Re: [gentoo-user] Re: Harddisk trouble ... or not yet?
Neil Bothwick n...@digimed.co.uk [10-05-27 02:04]: On Wed, 26 May 2010 21:13:06 +0200, Volker Armin Hemmann wrote: that is why I used 'usually' and 'shouldn't'. Have you considered a career in politics? ;-) -- Neil Bothwick A clean desk is a sign of a cluttered desk drawer. Oh, uhh...I did not want to start a political discussion here... ;O) In the meantime I did the copy thingy (dd if=) again with a new KNOPPIX dvd (kernel 2.6.32.something) and it copied the whole disk in 204min without a single I/O error. Now I did not know exactly what think about it... (which again is like politics ;) Is there any way to check the disk without damaging its contents? best regards, mcc -- Please don't send me any Word- or Powerpoint-Attachments unless it's absolutely neccessary. - Send simply Text. See http://www.gnu.org/philosophy/no-word-attachments.html In a world without fences and walls nobody needs gates and windows.
Re: [gentoo-user] Re: Harddisk trouble ... or not yet?
walt w41...@gmail.com [10-05-27 04:08]: On 05/26/2010 05:19 PM, meino.cra...@gmx.de wrote: Is there any way to check the disk without damaging its contents? Do you know about SMART? Install sys-apps/smartmontools if you don't already have it, and read the manpage for smartctl. I add smartd to my default runlevel so the hard drives will test themselves once every month and log the test results in syslog. Hm. I just noticed that smartd isn't actually running, so I need to do some debugging now. But that's the idea, anyway. Hi, yes, I know smart... I was more thinking of a tool, which test the whole disc surface and reports every bad sector. Smarts is more of statistical kind: It counts events and tries to calculate dooms day from that ;) -- Please don't send me any Word- or Powerpoint-Attachments unless it's absolutely neccessary. - Send simply Text. See http://www.gnu.org/philosophy/no-word-attachments.html In a world without fences and walls nobody needs gates and windows.
Re: [gentoo-user] Re: Harddisk trouble ... or not yet?
On Thu, 2010-05-27 at 04:43 +0200, meino.cra...@gmx.de wrote: walt w41...@gmail.com [10-05-27 04:08]: On 05/26/2010 05:19 PM, meino.cra...@gmx.de wrote: Is there any way to check the disk without damaging its contents? Do you know about SMART? Install sys-apps/smartmontools if you don't already have it, and read the manpage for smartctl. I add smartd to my default runlevel so the hard drives will test themselves once every month and log the test results in syslog. Hm. I just noticed that smartd isn't actually running, so I need to do some debugging now. But that's the idea, anyway. Hi, yes, I know smart... I was more thinking of a tool, which test the whole disc surface and reports every bad sector. Smarts is more of statistical kind: It counts events and tries to calculate dooms day from that ;) Not so easy (coming in late on this thread, sorry if its been covered) Modern hard drives insulate the outside from whats actually happening internally. They have a number of spare locations they can swap into use when a bad patch develops. This is invisible except to something like smart reporting. Rule of thumb - when a modern drive starts showing bad sectors to the outside world, its already well past its use by date. So something like SMART is the only way for the average Joe to get the health of a drive. Google has lots on this sort of thing BillK
Re: [gentoo-user] Re: Harddisk trouble ... or not yet?
On Thu, 2010-05-27 at 11:52 +0800, W.Kenworthy wrote: So something like SMART is the only way for the average Joe to get the health of a drive. Google has lots on this sort of thing That sentence is correct in more than one way! Google the generic term for any web page found via searching on Google no doubt has lots on this sort of thing, but so does Google the company. I remember reading a SlasDot post about the results of their disk monitoring over the last x years, and they use and monitor a lot of disks. *looking* Here's the full study: http://labs.google.com/papers/disk_failures.html From the abstract: ...we conclude that models based on SMART parameters alone are unlikely to be useful for predicting individual drive failures. Surprisingly, we found that temperature and activity levels were much less correlated with drive failures than previously reported. I recall there were some summaries of this article, but I can't find them right now. An interesting read. Basically, you might not be able to get reliable warnings of impending failures. Keep Good Backups (so say we all) -- Iain Buchanan iaindb at netspace dot net dot au The naked truth of it is, I have no shirt. -- William Shakespeare, Love's Labour's Lost
