ST2000LM007 SimError - Remaining in BootFW

[DataMedics]

So I've seen this error before but it's always been when the ROM or PCB wasn't native. However, in this case the client was only at their computer guy, he swears he never took the PCB off (and I know him so I sort of trust him). Everything in the ROM code matches the drive serial, wwn, PCB serial matches the qr code, etc. So it definitely appears to be the original PCB and ROM code.

Here's the terminal output:

Code: Select all

Boot 0x80M[LBA=0x00000001 EC=]
EC:0x43110081
EC:0x43110081
EC:0x43110081
EC:0x43110081
EC:0x43110081
EC:0x43110081
EC:0x43110081
EC:0x43110081
EC:0x43110081
EC:0x43110081
EC:0x43110081
EC:0x43110081
EC:0x43110081[LBA=0x00000001 EC=]
EC:0x43110081
EC:0x43110081
EC:0x43110081
EC:0x43110081
EC:0x43110081
DSC PASS
EC:0x43110081
EC:0x43110081[LBA=0x0000CB21 EC=]
EC:0x43110081
EC:0x43110081
EC:0x43110081
EC:0x43110081
EC:0x43110081
EC:0x43110081
EC:0x43110081[LBA=0x00000406 EC=]
EC:0x43110081
EC:0x43110081
EC:0x43110081
EC:0x43110081
EC:0x43110081
EC:0x43110081
EC:0x43110081
EC:0x43110081
EC:0x43110081
EC:0x43110081
EC:0x43110081
EC:0x43110081
EC:0x43110081[LBA=0x00000406 EC=]
EC:0x43110081
EC:0x43110081
EC:0x43110081
EC:0x43110081
EC:0x43110081
EC:0x43110081
EC:0x43110081[LBA=0x0000CF26 EC=]
EC:0x43110081
EC:0x43110081
EC:0x43110081
EC:0x43110081
EC:0x43110081
EC:0x43110081
EC:0x43110081
EC:0x43110081
EC:0x43110081
EC:0x43110081
EC:0x43110081
EC:0x43110081
EC:0x43110081[LBA=0x0000CF26 EC=]
EC:0x43110081
EC:0x43110081
EC:0x43110081
EC:0x43110081
EC:0x43110081
EC:0x43110081
EC:0x43110081
SimError - Remaining in BootFW
00001002Perform a double download without a power cycle


Anyone else ever seen this when it wasn't a non-native ROM or PCB?

[Doomer]

Yes, it could happen with bad heads
or bad blocks in DiscFW (not your case, because the drive does not read at all)

[DataMedics]

OK, thanks. I've just never seen bad heads result in this error before. I didn't want to waste a perfectly good donor if I've got something suspect going on.

[DataMedics]

Just to update this case, I swapped heads and I'm getting the exact same error. So it wasn't from bad heads.

Must be some sort of firmware corruption, but I can't see any way to proceed with even attempting to fix it.

[Doomer]

Source of the post Just to update this case, I swapped heads and I'm getting the exact same error. So it wasn't from bad heads.

Must be some sort of firmware corruption, but I can't see any way to proceed with even attempting to fix it.

Yes, this is strange.
The drive does not read anything in SA, although it tries to read in 4 different places. If PCB/ROM is original then it's some kind of damage, maybe magnetic in SA.

[DataMedics]

Yeah, I even put the original heads in the donor and they seem to be working fine. So I've definitely ruled out heads and PCB and the ROM seems original too.

Despite even trying to short the read channel there doesn't seem to be any method to get terminal access either. So I can't see any path to attempt repair here.

It's almost like something triggered this drive to format the SA or something.

[GuideRecovery]

but how come you read the service area in the first place with this error there is no way to read SA !?
mostly seen this error where ROM/PCB is not native..

[falver]

Used donor for heads replacement - did not work. Put the heads back in donor - worked perfectly. In the morning the same donor start to click.
These slim drives are sick! So tired of them!