[Novalug] disk wipe causing panic

Mark Smith mark@winksmith.com
Mon Jun 16 16:34:46 EDT 2014


that aside, a failing drive is not supposed to panic my system.

On Mon, Jun 16, 2014 at 04:31:58PM -0400, Zachary Zebrowski wrote:
> Hi Mark,
> 
> Looks like the drive is failing... see the top part of screen?  You may
> just need to ... um ... grab hammer and solve the problem with gravity...
> 
> Zak
> 
> 
> On Mon, Jun 16, 2014 at 4:28 PM, Mark Smith <mark@winksmith.com> wrote:
> 
> > i have a bunch of USB disks i'm trying to wipe.  i have resorted to my
> > old friend dd for this.
> >
> >         dd if=/dev/zero of=/dev/sdc bs=1M
> >
> > you'd think that'd be the end of this story, but it's just the start.
> > my system panics have running for an hour or so.  I have a new-ish
> > motherboard with new-ish i5 hardware.  this system is known to work
> > fine.  i just took these disks out of a working storage system.  they
> > are also known to work.
> >
> > i've tried /dev/sdc and /dev/sdc1 from both front/back USB ports with
> > the same results.  it either hangs hard or i panic.  when i do get any
> > messages, i get a bunch of IO errors from the device i'm writing a stack
> > trace with function calls that look like block device writers and a hard
> > lock up.
> >
> >         blk_update_request
> >         blk_update_bidi
> >         blk_end_bidi
> >         blk_end_request_err
> >         scsi_io_completion
> >         scsi_finish_command
> >         scsi_softirq_done
> >         blk_done_softirq
> >         __do_softirq
> >         run_ksoftirqd
> >         smpboot_thread_fn
> >         ? SyS_setgroups
> >         kthread
> >         ? kthread_create_on_node
> >         ret_from_fork
> >         ? ktthread_create_on_node
> >         Code: 47 c1 c1 ea 03 83 c2 01 39 d0 0f 47 c2 c3 66 90 0f 1f 44 00
> > 00 85 f6 74 17 f0 80 67 18 fe 48 8b 47 40 48 85 c0 74 07 55 48 89 e5 <ff>
> > d0 5d f3 c3 48 8b 47 18 a8 01 b8 fb ff ff ff 0f 44 f0 eb de
> >
> > for the full traceback panic screen:
> >
> >
> > https://drive.google.com/file/d/0B3jQ8Q3Zo2xcbmhrbDc5LWVyMVE/edit?usp=sharing
> >
> > i didn't want to kill my system, so i have it booted off of a USB key.
> > not sure what version it is, but it did the same thing when i booted
> > normally into my 12.04.4LTS latest stable kernel.
> >
> > nobody is into linux around these parts so i'm putting an ntfs filesystem
> > on it.  the mkfs.ntfs attempts to do a disk write of every block by
> > default.  this also panics my system.
> >
> > my last stab effort that i'm trying right now is i run dd for a couple
> > gig, re-write the partitions using fdisk, create an ext4 filesystem
> > on it, mount, and then create a file which consumes the entire disk.
> > finally, i overwrite the ext4 with an ntfs file system in quick mode.
> > rinse, repeat.  i expect this to work as i know ext4 works.
> >
> > 1. what's going on?
> > 2. what's the best way to clear these disks?
> > 3. have i really cleared the entire disk?  i was hoping to write to
> >    /dev/sdc whacking the entire drive in the process.
> >
> > --
> > Hei konā mai
> > Mark Smith
> > mark@winksmith.com
> > _______________________________________________
> > Novalug mailing list
> > Novalug@calypso.tux.org
> > http://calypso.tux.org/mailman/listinfo/novalug

-- 
Hei konā mai
Mark Smith
mark@winksmith.com



More information about the Novalug mailing list