Curt wrote:

> On 2015-03-12, David Wright <deb...@lionunicorn.co.uk> wrote:
> >> >> 
> >> >> Is that Iomega USB drive healthy? 
> >
> > Do you mean "was it healthy before this incident"
> > or are you expressing concern for its health since
> > being disconnected.
> 
> I meant the former, though I'm sure you know more about
> everything than I do.
> 
> > Yes, I'd certainly think the latter, and fsck/chkdsk it.

It's a journaled (ext3) filesystem, so when I next mounted it, it just
recovered the journal.  e2fsck give me

    allegro$ /usr/bin/sudo e2fsck -p /dev/sdb1
    external: clean, 99789/19537920 files, 20715689/78142160 blocks
    allegro$ /usr/bin/sudo e2fsck /dev/sdb1
    e2fsck 1.42.12 (29-Aug-2014)
    external: clean, 99789/19537920 files, 20715689/78142160 blocks

> Why not?  How about those smartmon thingies?

smartctl --health reports no problems.  Though I don't know the smartmon
tools well; if there's some other check that makes sense to run, I'm
certainly open to suggestions.

    allegro$ /usr/bin/sudo smartctl --health /dev/sdb1
    smartctl 6.4 2014-10-07 r4002 [x86_64-linux-3.16.0-4-amd64] (local build)
    Copyright (C) 2002-14, Bruce Allen, Christian Franke, www.smartmontools.org
    
    === START OF READ SMART DATA SECTION ===
    SMART Health Status: OK
    
> >> > I haven't noticed any other issues with it, and I do scan
> >> > /var/log/syslog for warning and error messages.  That said, the drive
> >> > *is* 5 years old, and I'd been planning to replace it this year just
> >> > based on its age.  Maybe I should do that sooner rather than later.
> >> 
> >> I think you got some error messages (the ones you showed us).
> >
> > It might help if you'd quote the lines you're worried about, rather
> > than just referring us all back to a long list of diagnostics.
> 
> <snip> Buffer I/O error on device sdb1, logical block 39027202
> <snip> lost page write due to I/O error on sdb1
> <snip> JBD2: Error -5 detected when updating journal superblock for sdb1-8.

I thought those were a direct consequence of the disconnect, though I
don't know what the kernel was trying to write out.  I don't think I was
actively using the Iomega drive when I plugged in the thumb drive.

regards,
mike


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/12591.1426189497@allegro.localdomain

Reply via email to