Replies: 2 comments
-
According to the drive manual it looks like these codes indicate the drive is having a hard time spinning up and stabilizing at operating speed. In the first log messages, the logs say:
In the second set of log messages, we have this series of events:
So the drive succeeded in performing recalibration (probably does this regularly every certain number of spin-ups) because we no longer see B0 in the second set of log messages. But B1 isn't any better, the drive can't reach a stable RPM and then fails to respond to further commands which is triggering the watchdog reset. |
Beta Was this translation helpful? Give feedback.
-
Thanks so much. So it's a drive issue rather than Blue SCSI, then. Can you recommend any resources where I could find a solution to these drive issues? (I'm wondering if it can't get stable RPM, should I try lubricating something? Switch out the power supply? etc) |
Beta Was this translation helpful? Give feedback.
-
I'm probably doing something wrong, but my first attempts to image a Q280 80-meg hard drive with a BlueSCSI initiator mode have not worked.
It looked and sounded like it was working. I powered up the hard drive, and its LED came on. Then I powered up the BlueSCSI, and its LED flashed then became solid. The hard drive spun up and it sounded like it was busy reading data. This went on for a long time, longer than I would have thought.
I decided to check the log file on the SD card to see if everything was working okay. I powered down the drive, then powered down the Blue SCSI and checked the SD card.
There was no .HD image on the card. There was only the .INI and log. The log looked like this:
I tried again. This time, I powered the BlueSCSI first, and then the drive. But the pattern was the same ... BlueSCSI reported trying to communicate with SCSI 0 for about 1 second. Then no further log entries for 8 minutes, at which point I powered off the hard drive. Then it resumed scanning the bus. I checked the SD card, and again, no HD image. Only the log file and the INI.
Finally, I realized the firmware was old, so I updated and tried again. This time the BlueSCSI LED behaved a bit differently. It was flashing at first and became solid when I powered on the HD. Then while the HD was spinning, sometimes it would go off for a moment, then come back on solid. After a minute or two, the LED turned off completely. At that point I powered off the drive and pulled the following log (with debugging turned on):
Beta Was this translation helpful? Give feedback.
All reactions