> I posted some info about this a while ago ... now I have more trouble.
Sorry, I know that following up ones own postings is bad style, but I just
discovered something that might help solving the problem.
When I partition the media (which I tried to avoid doing till now) with one
primary partition, and THEN mke2fs -b 2048 -m0 -c /dev/sdb1 it, mke2fs tells
me that
Checking for bad blocks (read-only test): done
Block 0 in primary superblock/group descriptor area bad.
Blocks 0 through 2 must be good in order to build a filesystem.
Aborting....
OK, I fdisk the medium to use blocks 4..606 for partition 1. Perfect. No
errors without -c. With -c, it complains about block 0 being bad. (How can I
still use the medium?)
When I start cp -a ~ /mod, there is an occasional SCSI bus reset that looks
like this:
Jan 17 10:11:33 debian kernel: scsi : aborting command due to timeout : pid
274795, scsi0, channel 0, id 2, lun 0 Write (6) 00 00 08 02 00
Jan 17 10:11:33 debian kernel: ncr53c8xx_abort: pid=274795
serial_number=274822 serial_number_at_timeout=274822
Jan 17 10:11:33 debian kernel: scsi : aborting command due to timeout : pid
274796, scsi0, channel 0, id 2, lun 0 Write (6) 00 02 0b 01 00
Jan 17 10:11:33 debian kernel: ncr53c8xx_abort: pid=274796
serial_number=274823 serial_number_at_timeout=274823
Jan 17 10:11:33 debian kernel: ncr53c875-0: abort ccb=c0013820 (cancel)
Jan 17 10:11:35 debian kernel: SCSI host 0 abort (pid 274795) timed out -
resetting
Jan 17 10:11:35 debian kernel: SCSI bus is being reset for host 0 channel 0.
Jan 17 10:11:35 debian kernel: ncr53c8xx_reset: pid=274795 reset_flags=2
serial_number=274822 serial_number_at
Jan 17 10:11:35 debian kernel: ncr53c875-0: resetting, command processing
suspended for 2 seconds
Jan 17 10:11:35 debian kernel: ncr53c875-0: restart (scsi reset).
Jan 17 10:11:35 debian kernel: ncr53c875-0: enabling clock multiplier
Jan 17 10:11:35 debian kernel: ncr53c875-0: Downloading SCSI SCRIPTS.
Jan 17 10:11:35 debian kernel: ncr53c875-0: command processing resumed
Jan 17 10:11:38 debian kernel: scsi0: MEDIUM ERROR on channel 0, id 2, lun
0, CDB: Write (6) 00 00 08 02 00
Jan 17 10:11:38 debian kernel: Deferred error sd08:11: sense key Medium
Error
Jan 17 10:11:38 debian kernel: Additional sense indicates Write error - auto
reallocation failed
Jan 17 10:11:38 debian kernel: scsidisk I/O error: dev 08:11, sector 0
Jan 17 10:11:38 debian kernel: ncr53c875-0-<2,*>: FAST-10 SCSI 10.0 MB/s
(100 ns, offset 10)
Jan 17 10:11:39 debian kernel: ncr53c875-0-<9,*>: WIDE SCSI (16 bit)
enabled.
Jan 17 10:11:39 debian kernel: ncr53c875-0-<9,*>: FAST-20 WIDE SCSI 40.0
MB/s (50 ns, offset 15)
Jan 17 10:11:40 debian kernel: ncr53c875-0-<0,*>: WIDE SCSI (16 bit)
enabled.
Jan 17 10:11:40 debian kernel: ncr53c875-0-<0,*>: FAST-20 WIDE SCSI 40.0
MB/s (50 ns, offset 15)
during which even the mouse cursor stops.
I cannot trust my MOD media under these circumstances. Is there any way to
resolve this and make them reliable?
--
_ciao, Jens_______________________________ http://www.pinguin.conetix.de
cat /dev/boiler/water | tea | sieve > /cup
mount -t hdev /dev/human/mouth01 /mouth ; cat /cup >/mouth/gulp
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/