Non-fatal error on SCSI drives

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

Anonymous

Guest
Hello!

I am having some problems with DBAN 1.04 and SCSI drives. I have to erase 12 drives and DBAN seems as the perfect solution. However, I get a non-fatal error and the program exits.

I have tried 2 different drives and two different controllers with the same problem. My log files:

[2005/02/07 14:40:41] dban: Darik's Boot and Nuke 1.0.4 started.
[2005/02/07 14:40:41] dban: Found floppy drive /dev/floppy/0.
[2005/02/07 14:40:42] dban: Found 0 seed files on the floppy disk.
[2005/02/07 14:40:47] dban: Wipe started.
[2005/02/07 14:50:42] dban: DBAN finished with non-fatal errors. The disks were not properly wiped, or there were verification errors.


[2005/01/07 14:40:47] dwipe: notice: Program loaded.
[2005/01/07 14:40:47] dwipe: notice: Opened entropy source '/dev/urandom'.
[2005/01/07 14:40:47] dwipe: info: Automatically enumerated 1 devices.
[2005/01/07 14:40:47] dwipe: info: Device '/dev/scsi/host2/bus0/target0/lun0/disc' is size 18113808896.
[2005/01/07 14:41:34] dwipe: notice: Invoking method 'DoD 5220-22.M' on device '/dev/scsi/host2/bus0/target0/lun0/disc'.
[2005/01/07 14:41:34] dwipe: notice: Starting round 1 of 1 on device '/dev/scsi/host2/bus0/target0/lun0/disc'.
[2005/01/07 14:41:34] dwipe: notice: Starting pass 1 of 7, round 1 of 1, on device '/dev/scsi/host2/bus0/target0/lun0/disc'.
[2005/01/07 14:50:31] dwipe: dwipe_static_pass: write: Input/output error.
[2005/01/07 14:50:31] dwipe: fatal: Unable to write to '/dev/scsi/host2/bus0/target0/lun0/disc'.
[2005/01/07 14:50:34] dwipe: notice: Wipe finished.
[2005/01/07 14:50:34] dwipe: notice: Wipe of device '/dev/scsi/host2/bus0/target0/lun0/disc' incomplete.


Some parts of the dmesg.txt:

<snip>
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 Nov 21 2004 21:52:31)
scsi1 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 6.2.36
<Adaptec aic7896/97 Ultra2 SCSI adapter>
aic7896/97: Ultra2 Wide Channel A, SCSI Id=7, 32/253 SCBs

scsi2 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 6.2.36
<Adaptec aic7896/97 Ultra2 SCSI adapter>
aic7896/97: Ultra2 Wide Channel B, SCSI Id=7, 32/253 SCBs

(scsi2:A:0): 40.000MB/s transfers (20.000MHz, offset 127, 16bit)
Vendor: FUJITSU Model: MAJ3182M SUN18G Rev: 0503
Type: Direct-Access ANSI SCSI revision: 02
Vendor: ESG-SHV Model: SCA HSBP M7 Rev: 0.08
Type: Processor ANSI SCSI revision: 02
scsi2:A:0:0: Tagged Queuing enabled. Depth 253
scsi: <fdomain> Detection failed (no card)
<snip>
.
.
.
<snip>
I/O error: dev 08:00, sector 35378532
<end of dmesg>

I get the I/O error in the end of dmesg with the same sector every time. I have tried the DoD and quick erase with the same bad result.

Help!

/Johan
 
Probably nothing wrong with the disk...

Well, as I wrote, I have tried with two different disks of the same type and they both fail at the same sector according to dmesg.txt.

I tried using a commercial eraser (Expert Eraser from IBAS) and it worked perfect with a DoD wipe on the disk where DBAN failed. So it seems like there is noting wrong with the disk(s)...

However, the disks might be a bit special. They come from a Sun A1000 storage and are SUN rebranded... Is there any tuning I can do with DBAN to get it to wipe these disks? Do you need more logs? (The disk model is embedded in the dmesg.txt in my previous post...)

I would really be happy if you could help me, I have 11 more disks like this one that needs wiping...

Regards,
/Johan
 
However, the disks might be a bit special. They come from a Sun A1000 storage and are SUN rebranded...
This is not an issue. I have several Sun branded disks that are compatible.


I tried using a commercial eraser (Expert Eraser from IBAS) and it worked perfect with a DoD wipe on the disk where DBAN failed.

Really? Did you check whether it left data at the end of the disk?


Is there any tuning I can do with DBAN to get it to wipe these disks? Do you need more logs? (The disk model is embedded in the dmesg.txt in my previous post...)

The log reports that the wipe fails at sector 35378532, which would be near the end of this disk.

If DBAN fails on all Fujitsu MAJ3182M disks at sector 35378532, then the drive firmware is likely reporting an incorrect number of sectors. This is a common problem with 9 gigabyte SCSI disks, but this would be the first report of the problem with an 18 gigabyte disk.

Check whether Fujitsu is providing a firmware upgrade for the MAJ3182M.

If DBAN fails on these Fujitsu MAJ3182M disks at different sectors, then the media is likely bad. The vendor's diagnostic program might provide more insight.
 
Back
Top