FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Gentoo > Gentoo User

 
 
LinkBack Thread Tools
 
Old 07-22-2010, 04:14 AM
David Relson
 
Default dying hard drive

/var/log/messages has indicated a slew of XFS problems on an external
USB hard drive (see attachment). These look pretty fatal. Anybody
think the file system is recoverable?

Also, palimpsest is reporting (graphically) that my external hard drive is
about to die. Can I save it's report to a text file???
Jul 21 23:53:23 osage kernel: usb 2-1: new high speed USB device using ehci_hcd and address 2
Jul 21 23:53:23 osage kernel: usb 2-1: New USB device found, idVendor=0bc2, idProduct=3001
Jul 21 23:53:23 osage kernel: usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Jul 21 23:53:23 osage kernel: usb 2-1: Product: FreeAgent
Jul 21 23:53:23 osage kernel: usb 2-1: Manufacturer: Seagate
Jul 21 23:53:23 osage kernel: usb 2-1: SerialNumber: 2GEX0DP4
Jul 21 23:53:23 osage kernel: scsi4 : usb-storage 2-1:1.0
Jul 21 23:53:24 osage kernel: scsi 4:0:0:0: Direct-Access Seagate FreeAgent 102D PQ: 0 ANSI: 4
Jul 21 23:53:24 osage kernel: sd 4:0:0:0: Attached scsi generic sg1 type 0
Jul 21 23:53:28 osage kernel: sd 4:0:0:0: [sdb] 976773168 512-byte logical blocks: (500 GB/465 GiB)
Jul 21 23:53:28 osage kernel: sd 4:0:0:0: [sdb] Write Protect is off
Jul 21 23:53:28 osage kernel: sd 4:0:0:0: [sdb] Mode Sense: 1c 00 00 00
Jul 21 23:53:28 osage kernel: sd 4:0:0:0: [sdb] Assuming drive cache: write through
Jul 21 23:53:28 osage kernel: sd 4:0:0:0: [sdb] Assuming drive cache: write through
Jul 21 23:53:28 osage kernel: sdb: sdb1
Jul 21 23:53:28 osage kernel: sd 4:0:0:0: [sdb] Assuming drive cache: write through
Jul 21 23:53:28 osage kernel: sd 4:0:0:0: [sdb] Attached SCSI disk

Jul 21 23:54:18 osage kernel: XFS: bad magic number
Jul 21 23:54:18 osage kernel: XFS: SB validate failed
Jul 21 23:54:36 osage kernel: XFS mounting filesystem sdb1
Jul 21 23:54:36 osage kernel: Starting XFS recovery on filesystem: sdb1 (logdev: internal)

Jul 21 23:55:12 osage kernel: XFS internal error XFS_WANT_CORRUPTED_GOTO at line 1544 of file fs/xfs/xfs_alloc.c. Caller
0xffffffff81122bf8
Jul 21 23:55:12 osage kernel: Pid: 4415, comm: mount Not tainted 2.6.34-gentoo-r1 #1
Jul 21 23:55:12 osage kernel: Call Trace:
Jul 21 23:55:12 osage kernel: [<ffffffff81122bf8>] ? xfs_free_extent+0x7d/0x94
Jul 21 23:55:12 osage kernel: [<ffffffff81121289>] ? xfs_free_ag_extent+0x42e/0x662
Jul 21 23:55:12 osage kernel: [<ffffffff81122bf8>] ? xfs_free_extent+0x7d/0x94
Jul 21 23:55:12 osage kernel: [<ffffffff81158832>] ? xfs_trans_get_efd+0x21/0x29
Jul 21 23:55:12 osage kernel: [<ffffffff8114f069>] ? xlog_recover_process_efi+0x113/0x171
Jul 21 23:55:12 osage kernel: [<ffffffff8114f114>] ? xlog_recover_process_efis+0x4d/0x8a
Jul 21 23:55:12 osage kernel: [<ffffffff8114f475>] ? xlog_recover_finish+0x14/0xac
Jul 21 23:55:12 osage kernel: [<ffffffff81155101>] ? xfs_mountfs+0x48f/0x556
Jul 21 23:55:12 osage kernel: [<ffffffff8115cb13>] ? kmem_zalloc+0xd/0x28
Jul 21 23:55:12 osage kernel: [<ffffffff811557ca>] ? xfs_mru_cache_create+0x111/0x14c
Jul 21 23:55:12 osage kernel: [<ffffffff81165c89>] ? xfs_fs_fill_super+0x199/0x300
Jul 21 23:55:12 osage kernel: [<ffffffff8108f7aa>] ? get_sb_bdev+0x125/0x16d
Jul 21 23:55:12 osage kernel: [<ffffffff81165af0>] ? xfs_fs_fill_super+0x0/0x300
Jul 21 23:55:12 osage kernel: [<ffffffff8108f3a1>] ? vfs_kern_mount+0xaa/0x179
Jul 21 23:55:12 osage kernel: [<ffffffff8108f4c3>] ? do_kern_mount+0x43/0xe1
Jul 21 23:55:12 osage kernel: [<ffffffff810a2e93>] ? do_mount+0x766/0x7e2
Jul 21 23:55:12 osage kernel: [<ffffffff81072562>] ? copy_from_user+0x13/0x25
Jul 21 23:55:12 osage kernel: [<ffffffff810a2f93>] ? sys_mount+0x84/0xc5
Jul 21 23:55:12 osage kernel: [<ffffffff8100202b>] ? system_call_fastpath+0x16/0x1b
Jul 21 23:55:12 osage kernel: Filesystem "sdb1": XFS internal error xfs_trans_cancel at line 1161 of file fs/xfs/xfs_trans.c. Caller 0xffffffff8114f0b9
Jul 21 23:55:12 osage kernel:
Jul 21 23:55:12 osage kernel: Pid: 4415, comm: mount Not tainted 2.6.34-gentoo-r1 #1
Jul 21 23:55:12 osage kernel: Call Trace:
Jul 21 23:55:12 osage kernel: [<ffffffff8114f0b9>] ? xlog_recover_process_efi+0x163/0x171
Jul 21 23:55:12 osage kernel: [<ffffffff81156cbc>] ? xfs_trans_cancel+0x56/0xd3
Jul 21 23:55:12 osage kernel: [<ffffffff8114f0b9>] ? xlog_recover_process_efi+0x163/0x171
Jul 21 23:55:12 osage kernel: [<ffffffff8114f114>] ? xlog_recover_process_efis+0x4d/0x8a
Jul 21 23:55:12 osage udevd-work[3570]: '/bin/mount -a' unexpected exit with status 0x000b
Jul 21 23:55:12 osage kernel: [<ffffffff8114f475>] ? xlog_recover_finish+0x14/0xac
Jul 21 23:55:12 osage kernel: [<ffffffff81155101>] ? xfs_mountfs+0x48f/0x556
Jul 21 23:55:12 osage kernel: [<ffffffff8115cb13>] ? kmem_zalloc+0xd/0x28
Jul 21 23:55:12 osage kernel: [<ffffffff811557ca>] ? xfs_mru_cache_create+0x111/0x14c
Jul 21 23:55:12 osage kernel: [<ffffffff81165c89>] ? xfs_fs_fill_super+0x199/0x300
Jul 21 23:55:12 osage kernel: [<ffffffff8108f7aa>] ? get_sb_bdev+0x125/0x16d
Jul 21 23:55:12 osage kernel: [<ffffffff81165af0>] ? xfs_fs_fill_super+0x0/0x300
Jul 21 23:55:12 osage kernel: [<ffffffff8108f3a1>] ? vfs_kern_mount+0xaa/0x179
Jul 21 23:55:12 osage kernel: [<ffffffff8108f4c3>] ? do_kern_mount+0x43/0xe1
Jul 21 23:55:12 osage kernel: [<ffffffff810a2e93>] ? do_mount+0x766/0x7e2
Jul 21 23:55:12 osage kernel: [<ffffffff81072562>] ? copy_from_user+0x13/0x25
Jul 21 23:55:12 osage kernel: [<ffffffff810a2f93>] ? sys_mount+0x84/0xc5
Jul 21 23:55:12 osage kernel: [<ffffffff8100202b>] ? system_call_fastpath+0x16/0x1b
Jul 21 23:55:12 osage kernel: xfs_force_shutdown(sdb1,0x8) called from line 1162 of file fs/xfs/xfs_trans.c. Return address = 0xffffffff81156cd5
Jul 21 23:55:12 osage kernel: Filesystem "sdb1": Corruption of in-memory data detected. Shutting down filesystem: sdb1
Jul 21 23:55:12 osage kernel: Please umount the filesystem, and rectify the problem(s)
Jul 21 23:55:12 osage kernel: Failed to recover EFIs on filesystem: sdb1
Jul 21 23:55:12 osage kernel: XFS: log mount finish failed
Jul 21 23:55:12 osage kernel: general protection fault: 0000 [#1] SMP
Jul 21 23:55:12 osage kernel: last sysfs file: /sys/devices/pci0000:00/0000:00:14.4/0000:03:05.2/usb2/2-1/2-1:1.0/host4/target4:0:0/4:0:0:0/block/sdb/size
Jul 21 23:55:12 osage kernel: CPU 0
Jul 21 23:55:12 osage kernel: Modules linked in: ide_gd_mod netconsole configfs ide_cd_mod atiixp ide_core evdev fuse scsi_wait_scan
Jul 21 23:55:12 osage kernel:
Jul 21 23:55:12 osage kernel: Pid: 4415, comm: mount Not tainted 2.6.34-gentoo-r1 #1 M2A-VM HDMI/System Product Name
Jul 21 23:55:12 osage kernel: RIP: 0010:[<ffffffff81197b20>] [<ffffffff81197b20>] strnlen+0x10/0x19
Jul 21 23:55:12 osage kernel: RSP: 0018:ffff8800069e9980 EFLAGS: 00010082
Jul 21 23:55:12 osage kernel: RAX: 2e3279702d312e32 RBX: ffffffffffffffff RCX: ffffffffffffffff
Jul 21 23:55:12 osage kernel: RDX: 2e3279702d312e32 RSI: fffffffffffffffe RDI: 2e3279702d312e32
Jul 21 23:55:12 osage kernel: RBP: ffffffff815cac0c R08: ffffffff81408bef R09: ffffffff815cac0c
Jul 21 23:55:12 osage kernel: R10: 000000000000000a R11: 00000000ffffffff R12: 0000000000000000
Jul 21 23:55:12 osage kernel: R13: 2e3279702d312e32 R14: ffffffffffffffff R15: 00000000ffffffff
Jul 21 23:55:12 osage kernel: FS: 00007f490c034740(0000) GS:ffff880001600000(0000) knlGS:0000000000000000
Jul 21 23:55:12 osage kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
Jul 21 23:55:12 osage kernel: CR2: 00007f9d30b84890 CR3: 0000000006878000 CR4: 00000000000006f0
Jul 21 23:55:12 osage kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Jul 21 23:55:12 osage kernel: DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Jul 21 23:55:12 osage kernel: Process mount (pid: 4415, threadinfo ffff8800069e8000, task ffff880006a65d00)
Jul 21 23:55:12 osage kernel: Stack:
Jul 21 23:55:12 osage kernel: ffffffff81198959 ffff8800069e9a48 ffffffffff0a0004 0000000000000004
Jul 21 23:55:12 osage kernel: <0> 0000000000000000 00000000000000ff ffffffff8119980c ffff88011ef1c9c0
Jul 21 23:55:12 osage kernel: <0> 0000000000000002 ffffffff815aba67 ffff8801ffffffff 000000000000000a
Jul 21 23:55:12 osage kernel: Call Trace:
Jul 21 23:55:12 osage kernel: [<ffffffff81198959>] ? string+0x43/0xa4
Jul 21 23:55:12 osage kernel: [<ffffffff8119980c>] ? vsnprintf+0x53e/0x8a6
Jul 21 23:55:12 osage kernel: [<ffffffffa0062222>] ? write_msg+0x90/0xeb [netconsole]
Jul 21 23:55:12 osage kernel: [<ffffffff81199bc5>] ? sprintf+0x51/0x59
Jul 21 23:55:12 osage kernel: [<ffffffff8102f9e6>] ? release_console_sem+0x17b/0x1ad
Jul 21 23:55:12 osage kernel: [<ffffffff810253e0>] ? update_curr+0x4f/0xe2
Jul 21 23:55:12 osage kernel: [<ffffffff81025b5f>] ? set_next_entity+0x3b/0x5e
Jul 21 23:55:12 osage kernel: [<ffffffff81167390>] ? xfs_fs_vcmn_err+0x48/0xcd
Jul 21 23:55:12 osage kernel: [<ffffffff8114096d>] ? xfs_cmn_err+0x7d/0x89
Jul 21 23:55:12 osage kernel: [<ffffffff8119cf50>] ? list_sort+0x1f8/0x224
Jul 21 23:55:12 osage kernel: [<ffffffff8115e636>] ? xfs_buf_cmp+0x0/0x1a
Jul 21 23:55:12 osage kernel: [<ffffffff81157b4b>] ? xfs_trans_ail_delete+0xa6/0xd0
Jul 21 23:55:12 osage kernel: [<ffffffff81135a88>] ? xfs_buf_iodone+0x28/0x31
Jul 21 23:55:12 osage kernel: [<ffffffff81135a42>] ? xfs_buf_do_callbacks+0x23/0x2f
Jul 21 23:55:12 osage kernel: [<ffffffff81135bf5>] ? xfs_buf_iodone_callbacks+0x110/0x13b
Jul 21 23:55:12 osage kernel: [<ffffffff8115f207>] ? xfs_buf_delwri_split+0x65/0xf3
Jul 21 23:55:12 osage kernel: [<ffffffff8116016f>] ? xfs_bioerror+0x36/0x3d
Jul 21 23:55:12 osage kernel: [<ffffffff8115fd0f>] ? xfs_flush_buftarg+0xba/0x11b
Jul 21 23:55:12 osage kernel: [<ffffffff8115fd89>] ? xfs_free_buftarg+0x19/0x5a
Jul 21 23:55:12 osage kernel: [<ffffffff81165d75>] ? xfs_fs_fill_super+0x285/0x300
Jul 21 23:55:12 osage kernel: [<ffffffff8108f7aa>] ? get_sb_bdev+0x125/0x16d
Jul 21 23:55:12 osage kernel: [<ffffffff81165af0>] ? xfs_fs_fill_super+0x0/0x300
Jul 21 23:55:12 osage kernel: [<ffffffff8108f3a1>] ? vfs_kern_mount+0xaa/0x179
Jul 21 23:55:12 osage kernel: [<ffffffff8108f4c3>] ? do_kern_mount+0x43/0xe1
Jul 21 23:55:12 osage kernel: [<ffffffff810a2e93>] ? do_mount+0x766/0x7e2
Jul 21 23:55:12 osage kernel: [<ffffffff81072562>] ? copy_from_user+0x13/0x25
Jul 21 23:55:12 osage kernel: [<ffffffff810a2f93>] ? sys_mount+0x84/0xc5
Jul 21 23:55:12 osage kernel: [<ffffffff8100202b>] ? system_call_fastpath+0x16/0x1b
Jul 21 23:55:12 osage kernel: Code: 75 ec c6 42 01 00 48 89 f8 c3 48 89 f8 eb 03 48 ff c0 80 38 00 75 f8 48 29 f8 c3 48 89 f8 eb 03 48 ff c0 48 85 f6 74 08 48 ff ce <80> 38 00 75 f0 48 29 f8 c3 31 c0 eb 12 41 38 c8 74 0a 48 ff c2
Jul 21 23:55:12 osage kernel: RIP [<ffffffff81197b20>] strnlen+0x10/0x19
Jul 21 23:55:12 osage kernel: RSP <ffff8800069e9980>
Jul 21 23:55:12 osage kernel: ---[ end trace 8748e8ca06d119ba ]---
Jul 21 23:55:32 osage kernel: usb 2-1: USB disconnect, address 2
 
Old 07-22-2010, 06:11 AM
Mick
 
Default dying hard drive

On Thursday 22 July 2010 05:14:08 David Relson wrote:
> /var/log/messages has indicated a slew of XFS problems on an external
> USB hard drive (see attachment). These look pretty fatal. Anybody
> think the file system is recoverable?

You'll have to try to recover it, to see if it is possible: xfs is vulnerable
to power interruptions, so a faulty USB cable can cause corruption. I haven't
had a corrupted xfs system for years now, so I put initial experiences down to
early (buggy) versions of the drivers. In my case, I was not able to recover
and I had to reformat and start again. After a couple of early mortality
cases the fs in question carried on for 4 years without a single problem.

Try xfs_check and xfs_repair with the drive unmounted, but first use
xfs_dump/restore or dd to make a back up just in case.

> Also, palimpsest is reporting (graphically) that my external hard drive is
> about to die. Can I save it's report to a text file???

Sorry, can't help with that because I'm not familiar with the application.
You could use sys-apps/smartmontools if you want a console application that
you can copy and paste from.
--
Regards,
Mick
 
Old 07-22-2010, 04:34 PM
Paul Hartman
 
Default dying hard drive

On Thu, Jul 22, 2010 at 1:11 AM, Mick <michaelkintzios@gmail.com> wrote:
> On Thursday 22 July 2010 05:14:08 David Relson wrote:
>> /var/log/messages has indicated a slew of XFS problems on an external
>> USB hard drive (see attachment). *These look pretty fatal. *Anybody
>> think the file system is recoverable?
>
> You'll have to try to recover it, to see if it is possible: *xfs is vulnerable
> to power interruptions, so a faulty USB cable can cause corruption.

I had exactly this problem with a USB HDD formatted with xfs. The USB
cable that it came with was rubbish... the drive would disconnect &
reconnect on its own for no apparent reason, and corruption happened
of course. I replaced it with another cable and it worked fine after
that.

A few months later the power supply started to fail, it would
occasionally not provide enough power and the drive would go offline
or start beeping/clicking. At first I thought the disk was bad
(clicking is never good) but it was actually the sound of the drive
trying to spin up and failing. Eventually the power brick couldn't
even spin up the drive at all. I replaced the power supply and now the
drive works fine again, for now...
 

Thread Tools




All times are GMT. The time now is 07:30 AM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org