DBAN issues on my maxtor hard drive

  • Thread starter Thread starter Anonymous
  • Start date Start date
A

Anonymous

Guest
I use DBAN to wipe my hard drive, but it didn't do what it supposes to do.
I guess that DBAN somehow delete my hard drive's physical firmware. Am I correct?
DOS 6.22 FDISK and windows 2000 set up complaine that it can not access to my hard drive which is 120GB, Firmware YAR41BW0.
I use autonuke to wipe my hard drive which is actually DOD short, 1 round of 3 passes method. DBAN successfuly wipe it, so I assume that I could use dos 6.22 FDISK to repartition my hard drive.
well, FDISK can not access to hard drive.
I try to use DBAN quick erase and it shows my hard drive as generic hard drive with the size of 8 GB and terminate without doing anything, other than finish with no fatal error message popped on my monitor.
My motherboard bios can detect the hard drive as Maxtor hard drive.
Now, what can I do to fix this problem?
All I wanna do is zero out my hard drive so that dos 6.22 FDISK would be able to access my hard drive.
DBAN would be a nice program if it does what it suppose to and would not create any kind of big problem.
 
I guess that DBAN somehow delete my hard drive's physical firmware. Am I correct?
Click to expand...
No. You are incorrect

DOS 6.22 FDISK and windows 2000 set up complaine that it can not access to my hard drive which is 120GB, Firmware YAR41BW0.
Click to expand...
What is the error message?

FDISK can not access to hard drive.
Click to expand...
Ensure that BIOS virus protection is disabled.


I try to use DBAN quick erase and it shows my hard drive as generic hard drive with the size of 8 GB and terminate without doing anything, other than finish with no fatal error message popped on my monitor.
Click to expand...
Provide the log file.


DBAN would be a nice program if it does what it suppose to and would not create any kind of big problem.
Click to expand...
Indeed. If you provide the information that I need to diagnose the problem, then also send $50 to my PayPal account to cover my consulting fee.
 
I disenable bios virus protection and it did run super slow like 0.01 % per hour to process.
I did find out to do quick method, but it was processing too slow as I mention in the beginning.
this is the issue; Bios can see my hard drive as it is , but when I try to use windows 2000 set up or Fdisk, it can not detect. tha t is also true for
other hard drive wiping or hard drive repair utility can not detect my hard drive..
I try to use windows 98 boot disk and it says my hard drive doesn't have any valid FAT or NTFS partition , so try to use Fdisk command or virus may infect my hard drive not registered, or third party partiioning program has been used.
Did you say I need you to send 50 dollars for consultation? You gotta be kidding me.. I can buy a brand new 160 GB hard drive for 120 dollars.
 
log

5/01/18 21:06:38] dban: Darik's Boot and Nuke 1.0.3 started.
[2005/01/18 21:06:38] dban: Found floppy drive /dev/floppy/0.
[2005/01/18 21:06:39] dban: Found 0 seed files on the floppy disk.
[2005/01/18 21:06:44] dban: Wipe started.
[2005/01/18 21:07:14] dban: DBAN finished with non-fatal errors. The disks were not properly wiped, or there were verification errors.

I get this message after I use Verbose mode

et: success
hda: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hda: read_intr: error=0x04 { DriveStatusError }
hda: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hda: read_intr: error=0x04 { DriveStatusError }
hda: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hda: read_intr: error=0x04 { DriveStatusError }
hda: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hda: read_intr: error=0x04 { DriveStatusError }
ide0: reset: success
hda: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hda: read_intr: error=0x04 { DriveStatusError }
end_request: I/O error, dev 03:00 (hda), sector 2
hda: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hda: read_intr: error=0x04 { DriveStatusError }
hda: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hda: read_intr: error=0x04 { DriveStatusError }
hda: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hda: read_intr: error=0x04 { DriveStatusError }
hda: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hda: read_intr: error=0x04 { DriveStatusError }
ide0: reset: success
hda: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hda: read_intr: error=0x04 { DriveStatusError }
hda: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hda: read_intr: error=0x04 { DriveStatusError }
hda: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hda: read_intr: error=0x04 { DriveStatusError }
hda: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hda: read_intr: error=0x04 { DriveStatusError }
ide0: reset: success
hda: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hda: read_intr: error=0x04 { DriveStatusError }
end_request: I/O error, dev 03:00 (hda), sector 3
hda: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hda: read_intr: error=0x04 { DriveStatusError }
hda: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hda: read_intr: error=0x04 { DriveStatusError }
hda: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hda: read_intr: error=0x04 { DriveStatusError }
hda: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hda: read_intr: error=0x04 { DriveStatusError }
ide0: reset: success
hda: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hda: read_intr: error=0x04 { DriveStatusError }
hda: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hda: read_intr: error=0x04 { DriveStatusError }
hda: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hda: read_intr: error=0x04 { DriveStatusError }
hda: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hda: read_intr: error=0x04 { DriveStatusError }
ide0: reset: success
hda: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hda: read_intr: error=0x04 { DriveStatusError }
end_request: I/O error, dev 03:00 (hda), sector 4
hda: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hda: read_intr: error=0x04 { DriveStatusError }
hda: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hda: read_intr: error=0x04 { DriveStatusError }
hda: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hda: read_intr: error=0x04 { DriveStatusError }
hda: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hda: read_intr: error=0x04 { DriveStatusError }
ide0: reset: success
hda: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hda: read_intr: error=0x04 { DriveStatusError }
hda: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hda: read_intr: error=0x04 { DriveStatusError }
hda: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hda: read_intr: error=0x04 { DriveStatusError }
hda: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hda: read_intr: error=0x04 { DriveStatusError }
ide0: reset: success
hda: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hda: read_intr: error=0x04 { DriveStatusError }
end_request: I/O error, dev 03:00 (hda), sector 5
hda: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hda: read_intr: error=0x04 { DriveStatusError }
hda: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hda: read_intr: error=0x04 { DriveStatusError }
hda: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hda: read_intr: error=0x04 { DriveStatusError }
hda: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hda: read_intr: error=0x04 { DriveStatusError }
ide0: reset: success
hda: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hda: read_intr: error=0x04 { DriveStatusError }
hda: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hda: read_intr: error=0x04 { DriveStatusError }
hda: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hda: read_intr: error=0x04 { DriveStatusError }
hda: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hda: read_intr: error=0x04 { DriveStatusError }
ide0: reset: success
hda: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hda: read_intr: error=0x04 { DriveStatusError }
end_request: I/O error, dev 03:00 (hda), sector 6
hda: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hda: read_intr: error=0x04 { DriveStatusError }
hda: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hda: read_intr: error=0x04 { DriveStatusError }
hda: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hda: read_intr: error=0x04 { DriveStatusError }
hda: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hda: read_intr: error=0x04 { DriveStatusError }
ide0: reset: success
hda: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hda: read_intr: error=0x04 { DriveStatusError }
hda: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hda: read_intr: error=0x04 { DriveStatusError }
hda: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hda: read_intr: error=0x04 { DriveStatusError }
hda: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hda: read_intr: error=0x04 { DriveStatusError }
ide0: reset: success
hda: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hda: read_intr: error=0x04 { DriveStatusError }
end_request: I/O error, dev 03:00 (hda), sector 7
unable to read partition table
/dev/ide/host0/bus0/target1/lun0: p1
SCSI subsystem driver Revision: 1.00
Loading Adaptec I2O RAID: Version 2.4 Build 5
Detecting Adaptec I2O RAID controllers...
Red Hat/Adaptec aacraid driver (1.1-3 Feb 22 2004 20:50:50)
scsi: <fdomain> Detection failed (no card)
NCR53c406a: no available ports found
sym53c416.c: Version 1.0.0-ac
Failed initialization of WD-7000 SCSI card!
IBM MCA SCSI: Version 4.0b
IBM MCA SCSI: No Microchannel-bus present --> Aborting.
This machine does not have any IBM MCA-bus
or the MCA-Kernel-support is not enabled!
DC390: 0 adapters found
megaraid: v1.18k (Release Date: Thu Aug 28 10:05:11 EDT 2003)
megaraid: no BIOS enabled.
aec671x_detect:
GDT: Storage RAID Controller Driver. Version: 2.05
GDT: Found 0 PCI Storage RAID Controllers
3ware Storage Controller device driver for Linux v1.02.00.036.
3w-xxxx: No cards found.
nsp32: loading...
RAMDISK: Compressed image found at block 0
Freeing initrd memory: 154k freed
VFS: Mounted root (cramfs filesystem) readonly.
Mounted devfs on /dev
Freeing unused kernel memory: 340k freed


Last error message log recorded on floppy drive

[2005/00/18 21:06:44] dwipe: notice: Program loaded.
[2005/00/18 21:06:44] dwipe: notice: Opened entropy source '/dev/urandom'.
[2005/00/18 21:06:44] dwipe: info: Automatically enumerated 3 devices.
[2005/00/18 21:07:14] dwipe: dwipe_main: shmget: Invalid argument.
[2005/00/18 21:07:14] dwipe: fatal: Unable to allocate shared memory for the context array.

Is my hard drive a good one?
Is it due to seed file issue?
You gotta reduce the consultation fee, then I may do it so.
 
Your drive's slag and DBAN didn't do it. That'll be $20, please.
 
You must log in or register to reply here.
Back
Top