Re: using HDDerase
- From: Paul <nospam@xxxxxxxxxx>
- Date: Fri, 28 Oct 2011 11:00:12 -0400
"David H. Lipman" <DLipman~nospam~@Verizon.Net> wrote in message news:j8ccqg09e3@xxxxxxxxxxxxxxxxxxxxFrom: "astron" <astron@xxxxxxxxxxxxxxxxxxxxxxxxxx>----------
Hardware >>>> Device Manager. What is the problem?
"David H. Lipman" <DLipman~nospam~@Verizon.Net> wrote in message
From: "astron" <astron@xxxxxxxxxxxxxxxxxxxxxxxxxx>2nd hard
After secure erasing 2nd(slave) hard drive with HDDerase.exe utility,drive(slave) is not listed anymore in My Computer, but it shown inletter to and
Its a raw drive with no partition scheme that Windows can assign a drivethus wiull NOT be shown in Explorer.
This makes things clearer. But how to resolve issue I mentioned above, BIOS
show error "Primary Slave Hard Disk Error", press F1 to Resume. ?
I don't know. It would depend on the computer, hard disk and BIOS revision.
The BIOS looks at the hardware and communicates to the BIOS (firmware) embedded on the hard disk. It then sends the system BIOS the drive parameters (heads, cylinders & sectors per track).
When the user views the CMOS Setup they are running a routine in the BIOS that queries information set about the hardware in CMOS memory.
The fact that you used the text "2nd(slave) hard drive" is indicative of an older PC that has an IDE/EIDE (aka; PATA) interface. Thus will most likely have two IDE Channels cable of up to four IDE devices.
When the user views the CMOS Setup they should then be able to see the assigned drive parameters (heads, cylinders & sectors per track) or the hard disk model.
If Yes then there is good communication with the hard disk hardware and the information will be passed onto the installed Operating System. Presumably you have Windows XP (as you posted in this group) and in the WinXP "Device Manager" you can see the hardware.
Pretty much, that's all that counts. The drive can now be re-formatted using the OS.
It is possible that the un-named system using the un-named BIOS and BIOS version could be looking for a marker on said hard disk that was removed and thus the error message.
If the drive can be formatted under WinXP, its a moot point.
If the drive can NOT be formatted under WinXP then you would have to use the un-named hard disk manufacturer's disk utility to see if the drive can be revived (so to speak). The un-named hard disk manufacturer's disk utility would know how to fully communicate with its hardware and would give further indication one way or another.
Multi-AV Scanning Tool - http://multi-av.thespykiller.co.uk
The disk shown in Device Manager as "Disk Drive", when right click on it, there are NO option for partitioning or formatting disk. There is option Disable, Uninstall, but this not change anything.
<resend - server problems>
I tried the HDDERASE program here.
I used a Seagate 7200.7 80GB drive.
I used the HDDERASE.iso and made a boot DVD with it, and used that
to run the command.
The program waits while the erase command is running. It took 42 minutes
to complete, during which time the hard drive light was on. By calculation,
it should have taken 30 minutes to do the erasure, so it was a bit slow.
(30 minutes at average benchmark rate should have been enough to complete
the entire 80GB disk).
The program also wrote the MBR with the details of the erasure. I was
able to verify that by reading the MBR later and examining the data with
a hex editor. And the confirmation of erasure was printed in there. The
adjacent sectors contained all 0's, so that was the pattern used internally
by Secure Erase (drive didn't support Enhanced option).
When Windows next started, and that disk was connected:
1) BIOS made no complaints. There were no "Primary Slave Hard Disk Error"
type errors. Presumably that error is a SMART error ?
2) Windows had an entry in Device Manager, under Disk Drives ("ST380011")
3) Disk Management shows an uninitialized 80GB drive. The wizard popped up
and wanted to write a signature on the drive. I canceled that. I used
the initialize button on the left in Disk Management, to turn the disk
into a Basic disk.
4) I was able to make a partition on the drive after that. Now, it has
a single 80GB partition, as proof it's working.
So I had no problems with mine.
I had significant problems with the usage of MSDOS for this task.
It's a pain in the ass, because it insists on only the primary four
disk interfaces be used. On my current machine, the IDE interface is
done with a separate chip, and MSDOS couldn't see it. So the
HDDErase program had no menu items to select from, and could not
erase the disk.
On my "legacy" machine, I put the IDE hard drive on a ribbon cable
and it was seen fine. The problew on that machine was a bit different.
I was booting MSDOS from a SATA DVD. That uses Extended INT 0x13 as
far as I know. But when the setup tried to load a CDROM driver, of
course the CDROM driver can't see the SATA interface, and so I
couldn't actually access the copy of HDDErase which was on the R:
CDROM image. Yet, the rest of the boot files, used to boot the
system (on Q:) were visible. THe MSDOS ISO on the HDDErase download,
is one of those "oversized" setups, with floppy sized boot volume, but
also a separate CDROM section, and that's the part that wouldn't mount.
To fix that, I had to plug an IDE2SAT adapter into the back of the
DVD drive, and connect it to the ribbon cable, and then, with all
devices on ribbon cables, I was able to use HDDErase.
So no significant problems here, and no broken hard drive. The
HDDErase program seemed to work. And the disk did show up in Disk
Management just fine.
- Re: using HDDerase
- From: astron
- Re: using HDDerase