asked on
Failing hard disk?
Hi,
Im running Centos on an old HP DL140 1U server.
Before installing centos, I added a brand new WD Black 1TB drive for data. THe OS is installed on a 160GB drive that was already in the server.
3 months on, and the WD drive has started to develop problems. Centos keeps putting it into read-only mode and I have to totally power down the server to get the drive to work again. A standard reboot doesnt seem to help, and when i do try rebooting, i get a bios warning that the drive is faulty.
However, when i power the server down fully, it boots with no problem.
Here is the log from centos:-
Is this a hardware problem (faulty hard disk) or is this something software related (since power cycling seems to temporarily fix it)?
I've tried running fsck which doesnt show any problems at all.
Also, is the WD Black ok in a server that runs 24/7? Someone on IRC commented that I'm having these problems because its a desktop hard disk and therefore shouldnt be used in a server.
If its not ok, what SATA hard disk should I be looking at for a server?
The server only supports SATA.
Thanks
Dan
Im running Centos on an old HP DL140 1U server.
Before installing centos, I added a brand new WD Black 1TB drive for data. THe OS is installed on a 160GB drive that was already in the server.
3 months on, and the WD drive has started to develop problems. Centos keeps putting it into read-only mode and I have to totally power down the server to get the drive to work again. A standard reboot doesnt seem to help, and when i do try rebooting, i get a bios warning that the drive is faulty.
However, when i power the server down fully, it boots with no problem.
Here is the log from centos:-
Jul 10 00:47:58 backupserver kernel: end_request: I/O error, dev sdb, sector 614323705
Jul 10 00:47:58 backupserver kernel: end_request: I/O error, dev sdb, sector 614325649
Jul 10 00:47:58 backupserver kernel: end_request: I/O error, dev sdb, sector 1430681601
Jul 10 00:47:58 backupserver kernel: end_request: I/O error, dev sdb, sector 1430681705
Jul 10 00:47:58 backupserver kernel: end_request: I/O error, dev sdb, sector 1430683593
Jul 10 00:47:58 backupserver kernel: end_request: I/O error, dev sdb, sector 1430685545
Jul 10 00:47:58 backupserver kernel: JBD: Detected IO errors while flushing file data on sdb1
Jul 10 00:47:58 backupserver kernel: EXT3-fs (sdb1): error: ext3_journal_start_sb: Detected aborted journal
Jul 10 00:47:58 backupserver kernel: EXT3-fs (sdb1): error: remounting filesystem read-only
Jul 10 00:49:49 backupserver named[1118]: zone keshercomms.com/IN: refresh: non-authoritative answer from master 37.128.190.75#53 (source 0.0.0.0#0)
Jul 10 00:52:01 backupserver named[1118]: zone averwood.co.uk/IN: serial number (2012051611) received from master 37.128.190.75#53 < ours (2012051803)
Jul 10 00:52:15 backupserver named[1118]: zone essaproperties.co.uk/IN: serial number (2012051611) received from master 37.128.190.75#53 < ours (2012051803)
Jul 10 00:53:31 backupserver named[1118]: zone cdd.uk.com/IN: serial number (2012051615) received from master 37.128.190.75#53 < ours (2012051803)
Jul 10 00:53:48 backupserver ntpd[4315]: synchronized to 178.79.150.93, stratum 3
Jul 10 00:54:45 backupserver named[1118]: dumping master file: tmp-CNUzHVGo43: open: permission denied
Jul 10 00:55:22 backupserver named[1118]: zone tamid.co.uk/IN: serial number (2012051615) received from master 37.128.190.75#53 < ours (2012051803)
Jul 10 00:55:30 backupserver kernel: __ratelimit: 27 callbacks suppressed
Jul 10 00:55:30 backupserver kernel: sd 1:0:1:0: [sdb] Unhandled error code
Jul 10 00:55:30 backupserver kernel: sd 1:0:1:0: [sdb] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Jul 10 00:55:30 backupserver kernel: sd 1:0:1:0: [sdb] CDB: Read(10): 28 00 6f f6 3e c1 00 00 08 00
Jul 10 00:55:30 backupserver kernel: __ratelimit: 27 callbacks suppressed
Jul 10 00:55:30 backupserver kernel: EXT3-fs error (device sdb1): ext3_find_entry: reading directory #58695697 offset 0
Jul 10 00:55:53 backupserver kernel: sd 1:0:1:0: [sdb] Unhandled error code
Jul 10 00:55:53 backupserver kernel: sd 1:0:1:0: [sdb] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Jul 10 00:55:53 backupserver kernel: sd 1:0:1:0: [sdb] CDB: Read(10): 28 00 28 01 ff 19 00 00 08 00
Jul 10 00:55:53 backupserver kernel: EXT3-fs error (device sdb1): ext3_find_entry: reading directory #20971528 offset 0
Jul 10 00:56:00 backupserver kernel: sd 1:0:1:0: [sdb] Unhandled error code
Jul 10 00:56:00 backupserver kernel: sd 1:0:1:0: [sdb] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Jul 10 00:56:00 backupserver kernel: sd 1:0:1:0: [sdb] CDB: Read(10): 28 00 00 00 6e e1 00 00 08 00
Jul 10 00:56:00 backupserver kernel: EXT3-fs error (device sdb1): ext3_find_entry: reading directory #11 offset 0
Jul 10 00:56:11 backupserver named[1118]: zone jemsmanchester.co.uk/IN: serial number (2012051615) received from master 37.128.190.75#53 < ours (2012051803)
Jul 10 00:56:32 backupserver kernel: sd 1:0:1:0: [sdb] Unhandled error code
Jul 10 00:56:32 backupserver kernel: sd 1:0:1:0: [sdb] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Jul 10 00:56:32 backupserver kernel: sd 1:0:1:0: [sdb] CDB: Read(10): 28 00 33 d2 b4 d1 00 00 08 00
Jul 10 00:56:32 backupserver kernel: EXT3-fs error (device sdb1): ext3_find_entry: reading directory #27164879 offset 0
Jul 10 00:57:01 backupserver kernel: sd 1:0:1:0: [sdb] Unhandled error code
Jul 10 00:57:01 backupserver kernel: sd 1:0:1:0: [sdb] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Jul 10 00:57:01 backupserver kernel: sd 1:0:1:0: [sdb] CDB: Read(10): 28 00 28 02 be b1 00 00 08 00
Jul 10 00:57:01 backupserver kernel: EXT3-fs error (device sdb1): ext3_find_entry: reading directory #20971822 offset 0
Jul 10 00:57:01 backupserver kernel: sd 1:0:1:0: [sdb] Unhandled error code
Jul 10 00:57:01 backupserver kernel: sd 1:0:1:0: [sdb] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Jul 10 00:57:01 backupserver kernel: sd 1:0:1:0: [sdb] CDB: Read(10): 28 00 6f f5 be e9 00 00 08 00
Jul 10 00:57:01 backupserver kernel: EXT3-fs error (device sdb1): ext3_find_entry: reading directory #58695700 offset 0
Jul 10 00:57:01 backupserver kernel: sd 1:0:1:0: [sdb] Unhandled error code
Jul 10 00:57:01 backupserver kernel: sd 1:0:1:0: [sdb] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Jul 10 00:57:01 backupserver kernel: sd 1:0:1:0: [sdb] CDB: Read(10): 28 00 28 08 41 49 00 00 08 00
Jul 10 00:57:01 backupserver kernel: EXT3-fs error (device sdb1): ext3_get_inode_loc: unable to read inode block - inode=20989173, block=83951697
Jul 10 00:57:01 backupserver kernel: sd 1:0:1:0: [sdb] Unhandled error code
Jul 10 00:57:01 backupserver kernel: sd 1:0:1:0: [sdb] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Jul 10 00:57:01 backupserver kernel: sd 1:0:1:0: [sdb] CDB: Read(10): 28 00 28 5c 3f b1 00 00 08 00
Jul 10 00:57:01 backupserver kernel: EXT3-fs error (device sdb1): ext3_get_inode_loc: unable to read inode block - inode=21160397, block=84639774
Jul 10 00:57:01 backupserver kernel: sd 1:0:1:0: [sdb] Unhandled error code
Jul 10 00:57:01 backupserver kernel: sd 1:0:1:0: [sdb] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Jul 10 00:57:01 backupserver kernel: sd 1:0:1:0: [sdb] CDB: Read(10): 28 00 33 d9 ff 29 00 00 08 00
Jul 10 00:57:01 backupserver kernel: EXT3-fs error (device sdb1): ext3_find_entry: reading directory #27181070 offset 0
Jul 10 00:57:01 backupserver kernel: sd 1:0:1:0: [sdb] Unhandled error code
Jul 10 00:57:01 backupserver kernel: sd 1:0:1:0: [sdb] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Jul 10 00:57:01 backupserver kernel: sd 1:0:1:0: [sdb] CDB: Read(10): 28 00 28 54 40 89 00 00 08 00
Jul 10 00:57:01 backupserver kernel: EXT3-fs error (device sdb1): ext3_get_inode_loc: unable to read inode block - inode=21144443, block=84574265
Is this a hardware problem (faulty hard disk) or is this something software related (since power cycling seems to temporarily fix it)?
I've tried running fsck which doesnt show any problems at all.
Also, is the WD Black ok in a server that runs 24/7? Someone on IRC commented that I'm having these problems because its a desktop hard disk and therefore shouldnt be used in a server.
If its not ok, what SATA hard disk should I be looking at for a server?
The server only supports SATA.
Thanks
Dan
LinuxServer Hardware
Last Comment
DanJourno