[SOLVED] Disk Diagnosis? Whassup, if anything?

business_kid · 10-03-2020, 06:04 AM

This is a 500G 2.5" platter disk which I'm using as a backup disk on /dev/sdb1. So it normally gets block copies or rsync jobs. Now some disk fault turned up and it got treated by e2fsck which did stuff, as it usually does. Then, next day (today) I get this

Code:

[mount /dev/sdb1
[ 8146.891969] sd 4:0:0:0: [sdb] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x08
[ 8146.893704] sd 4:0:0:0: [sdb] tag#0 Sense Key : 0x4 [current]
[ 8146.895424] sd 4:0:0:0: [sdb] tag#0 ASC=0x0 ASCQ=0x0
[ 8146.897148] sd 4:0:0:0: [sdb] tag#0 CDB: opcode=0x28 28 00 4b 00 07 80 00 00 08 00
[ 8146.898890] blk_update_request: I/O error, dev sdb, sector 1258293120 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
[ 8148.451568] EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: (null)
bash-5.0$

Which looks like an issue with /dev/sdb, not /dev/sdb1. Any ideas? Boot record or deeper?
At the moment, I probably have enough hard disk space to backup the backup disk, if you follow me, as I'm passing a 225G disk through my hands.

I also have my son's old 1TB platter, but it's a case of 'It's fine, IF it mounts'. It's a 'maybe' disk. The controller is iffy. So the trick is to put stuff on and get it off in one session

wpeckham · 10-03-2020, 06:13 AM

Quote:

Originally Posted by business_kid

This is a 500G 2.5" platter disk which I'm using as a backup disk on /dev/sdb1. So it normally gets block copies or rsync jobs. Now some disk fault turned up and it got treated by e2fsck which did stuff, as it usually does. Then, next day (today) I get this

Code:

[mount /dev/sdb1
[ 8146.891969] sd 4:0:0:0: [sdb] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x08
[ 8146.893704] sd 4:0:0:0: [sdb] tag#0 Sense Key : 0x4 [current]
[ 8146.895424] sd 4:0:0:0: [sdb] tag#0 ASC=0x0 ASCQ=0x0
[ 8146.897148] sd 4:0:0:0: [sdb] tag#0 CDB: opcode=0x28 28 00 4b 00 07 80 00 00 08 00
[ 8146.898890] blk_update_request: I/O error, dev sdb, sector 1258293120 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
[ 8148.451568] EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: (null)
bash-5.0$

Which looks like an issue with /dev/sdb, not /dev/sdb1. Any ideas? Boot record or deeper?
At the moment, I probably have enough hard disk space to backup the backup disk, if you follow me, as I'm passing a 225G disk through my hands.

I also have my son's old 1TB platter, but it's a case of 'It's fine, IF it mounts'. It's a 'maybe' disk. The controller is iffy. So the trick is to put stuff on and get it off in one session

The device upon which /dev/sdb1 is built is /dev/sdb. It is not the partition /dev/sdb1 specifically that has been reported as having an error, it is a sector of the DEVICE /dev/sdb. This COULD corrupt data on the /dev/sdb1 partition, but could be in another part of the device that is not /dev/sdb1. It COULD, on the other hand, be an isolated I/O error and nothing to worry about. There is not enough information to judge. I would, therefor, submit the disk to additional analysis and see what the disk diagnostic software reports. I might also start to budget for a replacement solution for my backups! (Just in case, because one thing about hardware is that it always fails in the end. Always!)

business_kid · 10-03-2020, 06:13 AM

Sorry, my bad. I/O error. Doesn't repeat.

JeremyBoden · 10-04-2020, 11:38 AM

Quote:

Originally Posted by business_kid

This is a 500G 2.5" platter disk whand it got treated by e2fsck which I'm using as a backup disk on /dev/sdb1.

So it normally gets block copies or rsync jobs. Now some disk fault turned up which did stuff, as it usually does. Then, next day (today) I get this....

So your backup device regularly fails.
Until you get a reasonably reliable disk there is little point in taking backups.

business_kid · 10-06-2020, 05:35 AM

I figured this. The disk is powers down, and is slow to start. So it throws one read error. I went a bit OTT on the knee-jerk reaction. The disk is fine, and young enough usage-wise.

I was thinking that I could just about backup the backup disk at the moment as I had a spare usb disk lying about. But it's case had some solder bridges on it's little pcb, so that wasn't going to work until I get a new case.