BadMac wrote:
hddguy wrote:
BlackST wrote:
Module RSVD Copy F...................... : Error[/u][/i]
I see this often and does not affect disk ID or accessibility.
But I agree that PCB is suspect. If you look in the NVRAM, some model show the serial number of the native disk is belongs to, Im pretty sure this is the case with this series also. You should check this.
Thanks for you suggestions so far guys. I really appreciate it.
I agree the RSVD Copy F error doesn't matter, we also see this often and it hasn't stopped us getting at the data.
I am pretty sure the PCB is original. It came out of a eeePC and was removed by the warranty/repair place under instructions from the supplier to be sent to us, so they would have had no reason to swap it. This is the first time we have seen this particular model of drive and spent a while just getting PC3000 to see it at all.
I do suspect an NVRam issue so we are currently trying to source a spare drive for its PCB (from ebay). However I also don't understand why it reports the "open" module error at boot up, what does this mean? what are the "open" modules? the PC3000 manual isn't helpful here at all and Ace haven't answered our emails. When I do the module check and select only "open" modules I don't see anything.
In case it helps, when you boot the drive it comes ready normally but as soon as you try to access its data (on Deepspar) it goes BSY and never comes back, requiring a power cycle.
Subject: Help with HTS545016B9A300 (5K500 B-160)BadMac wrote:
hddguy wrote:
BlackST wrote:
Module RSVD Copy F...................... : Error[/u][/i]
I see this often and does not affect disk ID or accessibility.
But I agree that PCB is suspect. If you look in the NVRAM, some model show the serial number of the native disk is belongs to, Im pretty sure this is the case with this series also. You should check this.
Thanks for you suggestions so far guys. I really appreciate it.
I agree the RSVD Copy F error doesn't matter, we also see this often and it hasn't stopped us getting at the data.
I am pretty sure the PCB is original. It came out of a eeePC and was removed by the warranty/repair place under instructions from the supplier to be sent to us, so they would have had no reason to swap it. This is the first time we have seen this particular model of drive and spent a while just getting PC3000 to see it at all.
I do suspect an NVRam issue so we are currently trying to source a spare drive for its PCB (from ebay). However I also don't understand why it reports the "open" module error at boot up, what does this mean? what are the "open" modules? the PC3000 manual isn't helpful here at all and Ace haven't answered our emails. When I do the module check and select only "open" modules I don't see anything.
In case it helps, when you boot the drive it comes ready normally but as soon as you try to access its data (on Deepspar) it goes BSY and never comes back, requiring a power cycle.
I have the same error on a drive:
Startup Mode...................................... : Normal Mode
WARNING! Failed to obtain the hard disk ID information. It may caused by the following reasons:
1. Incorrect compiler module.
2. NV-RAM configuration is incorrect.
Selected family:7210xxKLA
Model:ÿHDS7210xxKLxxx
Loading TeachKey.................................. : OK
Loading NV-RAM.................................... : OK
Loading module table Error,Try to Copy1......
Loading module table.............................. : OK
Loading "Open" module table....................... : Error
Loading Zone...................................... : Error
Initialization is complete
Loading module table[Cpoy1]....................... : OK
Loading module table[Cpoy1]....................... : OK
Loading module table[CpoyF]....................... : OK
Equipment identification.......................... : OK
Loading module table.............................. : OK
Loading "Open" module table....................... : Error
Loading Zone...................................... : OK
Could you find the solution for your drive?
Mine gets me 0 capacity, which means LBA was not mounted and, therefore, the fw was not completely loaded.
The question is: what happened and how to load it to ram and all the rest.
Any clues, anyone?
Thank you!