LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Hardware (http://www.linuxquestions.org/questions/linux-hardware-18/)
-   -   Trouble with SCSI, Trouble with Sata (http://www.linuxquestions.org/questions/linux-hardware-18/trouble-with-scsi-trouble-with-sata-447996/)

humbletech99 05-24-2006 04:05 AM

Trouble with SCSI, Trouble with Sata
 
Hi,
I've got a really troublesome machine, it was having SCSI I/O errors a lot, replacing the disks didn't help, replacing the scsi cable didn't help, even replacing the scsi controller didn't help... (the disk were a jbod). So I've stuck in large Sata disks instead to test how much slower they are, and again I'm having input output errors as follows on newly created ext3 filesystems when I try to use them:
Code:

hostname        kern        20:29:48        kernel: EXT3-fs error (device sdc1) in start_transaction: Journal has aborted
hostname        kern        20:29:48        kernel: EXT3-fs error (device sdc1) in start_transaction: Journal has aborted
hostname        kern        20:29:48        kernel: ext3_splice_branch: aborting transaction: Journal has aborted in __ext3_journal_get_write_access<2>EXT3-fs error (device sdc1) in ext3_prepare_write: Journal has aborted
hostname        kern        20:29:48        kernel: Remounting filesystem read-only
hostname        kern        20:29:48        kernel: EXT3-fs abort (device sdc1): ext3_journal_start: Detected aborted journal
hostname        kern        20:29:47        kernel: ext3_abort called.
hostname        kern        20:29:44        kernel: EXT3-fs error (device sdc1) in ext3_ordered_writepage: IO failure
hostname        kern        20:29:44        kernel: Aborting journal on device sdc1.
hostname        kern        20:29:44        kernel: EXT3-fs error (device sdc1): ext3_new_block: Allocating block in system zone - block = 112263168
hostname        kern        17:46:30        kernel: EXT3-fs error (device sdb1): ext3_readdir: bad entry in directory #53710740: directory entry across blocks - offset=0, inode=0, rec_len=13056, name_len=20
hostname        kern        17:46:30        kernel: EXT3-fs error (device sdb1): ext3_readdir: bad entry in directory #53120466: directory entry across blocks - offset=0, inode=0, rec_len=6948, name_len=91
hostname        kern        17:46:28        kernel: EXT3-fs error (device sdb1): ext3_readdir: bad entry in directory #41791555: directory entry across blocks - offset=0, inode=0, rec_len=6824, name_len=94
hostname        kern        17:46:28        kernel: Remounting filesystem read-only
hostname        kern        17:46:28        kernel: EXT3-fs abort (device sdb1): ext3_journal_start: Detected aborted journal
hostname        kern        17:46:28        kernel: ext3_abort called.
hostname        kern        17:46:28        kernel: Aborting journal on device sdb1.
hostname        kern        17:46:28        kernel: EXT3-fs error (device sdb1): ext3_readdir: bad entry in directory #41791536: directory entry across blocks - offset=0, inode=0, rec_len=15696, name_len=50
hostname        kern        16:31:33        kernel: EXT3-fs error (device sdb1) in start_transaction: Journal has aborted
hostname        kern        16:31:33        kernel: EXT3-fs error (device sdb1) in start_transaction: Journal has aborted
hostname        kern        16:31:33        kernel: ext3_splice_branch: aborting transaction: Journal has aborted in __ext3_journal_get_write_access<2>EXT3-fs error (device sdb1) in ext3_prepare_write: Journal has aborted
hostname        kern        16:31:33        kernel: EXT3-fs error (device sdb1) in start_transaction: Journal has aborted
hostname        kern        16:31:33        kernel: Remounting filesystem read-only
hostname        kern        16:31:33        kernel: EXT3-fs abort (device sdb1): ext3_journal_start: Detected aborted journal
hostname        kern        16:31:33        kernel: ext3_abort called.
hostname        kern        16:31:33        kernel: Aborting journal on device sdb1.
hostname        kern        16:31:33        kernel: EXT3-fs error (device sdb1): ext3_new_block: Allocating block in system zone - block = 6651906
hostname        kern        16:18:44        kernel: EXT3-fs error (device sdb1) in start_transaction: Journal has aborted
hostname        kern        16:18:43        kernel: EXT3-fs error (device sdb1) in start_transaction: Journal has aborted
hostname        kern        16:18:43        kernel: ext3_splice_branch: aborting transaction: Journal has aborted in __ext3_journal_get_write_access<2>EXT3-fs error (device sdb1) in ext3_prepare_write: Journal has aborted
hostname        kern        16:18:43        kernel: EXT3-fs error (device sdb1) in start_transaction: Journal has aborted
hostname        kern        16:18:43        kernel: EXT3-fs error (device sdb1) in start_transaction: Journal has aborted
hostname        kern        16:18:41        kernel: EXT3-fs error (device sdb1) in start_transaction: Journal has aborted
hostname        kern        16:18:41        kernel: EXT3-fs error (device sdb1) in start_transaction: Journal has aborted
hostname        kern        16:18:39        kernel: Remounting filesystem read-only
hostname        kern        16:18:36        kernel: EXT3-fs abort (device sdb1): ext3_journal_start: Detected aborted journal
hostname        kern        16:18:34        kernel: ext3_abort called.

I'm beginning to think this machine is cursed, I've already changed the motherboard which inexplicably worked until I shut the machine down, then switched it back on (or at least tried) and it just didn't switch back on, no static discharge or anything like that, just wouldn't play ball...

What on earth could be causing all these problems, practiccally everything in the whole case is new... the last thing to try is changing the psu which I've just done and will have to see if the errors recur...


All times are GMT -5. The time now is 06:34 PM.