Switch to full style
Data recovery and disk repair questions and discussions related to old-fashioned SATA, SAS, SCSI, IDE, MFM hard drives - any type of storage device that has moving parts
Post a reply

Incorrect WWN / Spoof Serial

October 23rd, 2023, 9:35

A few weeks ago we lost two drive in our Array, they are hitachi SAS drives.
Two was bad for our raid 5 configuration and we had data lose. The drives will initially come online and be ready, but quickly move to a degraded state. We sent them off to OnTrack Knoll to have them repaired. They were able to copy 99% of the disk (per their report). When we go the drives back, what no one told us was the the WWN was going to change because the drives are different.

I am looking at WDMarvel, i'm going to try the demo tomorrow. On the cloned drives i have nothing to lose. I want to try to change all the factory information to match the old drives. Does anyone know if this is possible with this tool?

Are there any other tips for getting the old drives working again? As a last ditch effort i'm willing to try whatever repair options might be out there.

Thanks in advance,

Re: Incorrect WWN / Spoof Serial

October 23rd, 2023, 11:26

AFAIK WDMarvel doesn't work with SAS, it's SATA only.

More info would be good.
Do you have any backup?
Hitachi model number?
More details of system and RAID pls, hardware/software RAID?

Re: Incorrect WWN / Spoof Serial

October 23rd, 2023, 12:20

So this was part of a 3par storage array.
We did not have a backup (long story there), we had some partial backups.
I opened WDMarvel with a different SAS drive today, it read the rom, but i honestly have no idea how to use it yet.

The new drives that were cloned by OnTrack are Hitachi, Model: HUC109090CSS600.

Honestly this is where we are at, just a bit disspointed we paid OnTrack so much only for them to say, yeah you can't just put them back in the array since the WWN changed after they've done the work and shippped it back. We asked if they could rebuild the drive into the old enclosure and they said no.

If you have any more ideas for me other than to try to modify the WWN i'm all ears.

Re: Incorrect WWN / Spoof Serial

October 23rd, 2023, 13:47

WDMarvel understands WD firmware architecture, not Hitachi.

Instead of trying to hack your new SAS drives, why not hack the RAID metadata in your array, or simply backup and rebuild your array with your new drives?

Re: Incorrect WWN / Spoof Serial

October 23rd, 2023, 13:50

Did Kroll Ontrack just make clones of the failed drives and not all drives in the array?

Re: Incorrect WWN / Spoof Serial

October 23rd, 2023, 14:01

fzabkar wrote:WDMarvel understands WD firmware architecture, not Hitachi.

Instead of trying to hack your new SAS drives, why not hack the RAID metadata in your array, or simply backup and rebuild your array with your new drives?


Ah i just assumed since WD has owned Hitachi for a while that the firmware was the same.
Ick, im worried about breaking the entire array. Also unsure how to hack the metadata?

Re: Incorrect WWN / Spoof Serial

October 23rd, 2023, 14:32

A sw raid recovery is the way to go here... I would avoid attaching the hacked array to the raid controller coz it can do more harm than good.

pepe

Re: Incorrect WWN / Spoof Serial

October 24th, 2023, 7:06

I looked into the sW raid recovery, the problem i'm going to have is the failed virtual volume is made up from a CPG which is comprised of a mix of drives and the virtual volume is made up of logical disks spread across that CPG.

Maybe this is a lost cause and i should just move on?

Re: Incorrect WWN / Spoof Serial

October 25th, 2023, 7:28

i am pretty sure it can be done in sw. But it might need quite some manual work.

Re: Incorrect WWN / Spoof Serial

October 25th, 2023, 7:44

pepe wrote:i am pretty sure it can be done in sw. But it might need quite some manual work.


I don't disagree with you, after you posted this i read up on the SWRaid and it seems like it would work. I just don't know where to start or if its worth the effort. There were 72 drvies in the CPG.
My next thought was that since i have a copy of the failed drive from ontrack, maybe i completely wipe the original bad drive, try to run some recovery tools on it, and if i can get it somewhat healthy, make another copy of the drive Ontrack sent me back onto the original drive.

Problem is that its a SAS drive, i purchased an external SAS to USB3 adapter (drive toaster), but it seems like it doesn't work with 10k drives, only 7.2k. So i'd need ot figure out out to access the drive first. I have a server i can put it in, but the servers doesn't just see physical drives, it makes me configure them as part of a logical drive via the controller. I could create a single drive raid 0 and run repairs, but that won' thelp when i need to copy the data again.
Post a reply