| Author |
Message |
   
John Ahearne
Username: jahearne
Registered: N/A
| | Posted on Tuesday, Jun 3, 2008 - 18:57: | |
Will WinHex see 520 bps drives? |
   
Stefan Fleischmann
Username: admin
Registered: 1-2001
| | Posted on Tuesday, Jun 3, 2008 - 19:06: | |
Yes, it should see them if Windows sees them. If with the standard disk access method it cannot read the sectors, try the alternative disk access methods. |
   
John Ahearne
Username: jahearne
Registered: N/A
| | Posted on Tuesday, Jun 3, 2008 - 20:27: | |
Windows sees the drives. I can access them, but all I see are zeros and I'm not convinced that these drives are blank. I use SCSItoolbox to verify that the drives are 520 bps, which also proves that Windows can see them. I tried alternative disk access methods, 1 & 2, closed WinHex each time. The sector boundaries in WinHex still show 512 bytes in size. MAC sedit can see 520bps drives. At least I'll be able to verify if they're blank or not then take it from there. |
   
John Ahearne
Username: jahearne
Registered: N/A
| | Posted on Wednesday, Jun 4, 2008 - 23:09: | |
sedit did confirm that there is data on the 520bps drives. My last attempts with WinHex were on XP and Win2003. Back to Win2000 workstation and I can see data on the 520bps drives, which is great! Now the problem is I can only see 512 bytes worth out of those 520 byte sectors. There is a lot of readable ASCII characters that's repeated and I can clearly see where 8 bytes of data is missing at the sector boundaries. I've added a row with no results. Unlike the old fibre channel drives where the extra 8 bytes was used for CRC values and what have you and EMC Clariions use that extra 8 bytes for checksums and other info, these NetApp drives appear to be using the entire 520 bytes for data. I have yet to confirm this on sedit. Any ideas on how to get WinHex to see the entire 520? I've tried Alternative disk access methods. Thanks, John |
   
Stefan Fleischmann
Username: admin
Registered: 1-2001
| | Posted on Thursday, Jun 5, 2008 - 1:02: | |
That means that Windows reports to WinHex a sector size of 512 bytes. I could try to compile a special version for you that tries to read all 520 bytes per sector and where you can explicitly persuade WinHex to assume such a sector size. |