Spinrite 6.1 5.07 Hangs on old IBM drive

[claudioz]

Spinrite 6.1 5.07 Hangs on (very old) IBM drive and the keyboard is not any longer responsive

Steve, I am running on a DELL PowerEdge T30, booting SpinRite from one of the front USB.
On the next USB I have connected a Sabrent SBT-ESU26 adapter compatible with Laptop drives from 20Y ago. I have 4 disk and I did not have any issues with a couple of them. This particular HD is a trouble maker. I tried level 1-5 and Spinrite hangs always on the same block (63.6481% of drive.) and the top of the screen is erased (see attachments). No red crash screen, only an unresponsive computer. I even switched just before the bad track to DynaStat and eventually the line went flat. After 15 min of no-action I end up re-booting.

Linux (sudo badblocks -v /dev/sde > badsector.txt) reports 8 bad blocks.

24867384
24867385
24867386
24867387
24868208
24868209
24868210
24868211


This was just a test and the disk contains a dusty Win95 image from 20Y ago, so no urgency whatsoever ... If you like I can send you the drive and adapter

 

[claudioz]

Spinrite 6.1 5.07 Hangs on (very old) IBM drive and the keyboard is not any longer responsive

Steve, I am running on a DELL PowerEdge T30, booting SpinRite from one of the front USB.
On the next USB I have connected a Sabrent SBT-ESU26 adapter compatible with Laptop drives from 20Y ago. I have 4 disk and I did not have any issues with a couple of them. This particular HD is a trouble maker. I tried level 1-5 and Spinrite hangs always on the same block (63.6481% of drive.) and the top of the screen is erased (see attachments). No red crash screen, only an unresponsive computer. I even switched just before the bad track to DynaStat and eventually the line went flat. After 15 min of no-action I end up re-booting.

Linux (sudo badblocks -v /dev/sde > badsector.txt) reports 8 bad blocks.

24867384
24867385
24867386
24867387
24868208
24868209
24868210
24868211


This was just a test and the disk contains a dusty Win95 image from 20Y ago, so no urgency whatsoever ... If you like I can send you the drive and adapter

(attached images)

 

[Steve]

Thanks for your report!

On the next USB I have connected a Sabrent SBT-ESU26 adapter compatible with Laptop drives from 20Y ago.

This is a textbook instance for triggering the BUG that I discovered earlier today in 5.07. I immediately replaced it with 5.08 which should not have that behavior. I cannot say for sure that there might not still be a problem, since having to work through a BIOS is always less direct than using SpinRite's native drivers... But I'll be interested in knowing what you find if/when you get the opportunity to try whatever the latest release is (5.08 or later) whenever you get around to it! Thanks!!