External HDD changes locations in /dev while mounted.
Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
External HDD changes locations in /dev while mounted.
I was a bit reluctant to post this problem, but either I simply can't figure out the right phrase to put in google or no one's ever posted this problem online before. I simply don't understand enough about how linux handles hard drives to figure this out on my own.
I've got an external HDD from Iomega that I've been using for over a year and lately it's been doing this thing where it suddenly changes from /dev/sdg to /dev/sdh while the partition on it is still mounted, seemingly at random. I'm often (not always) able to look at the contents of the partition, but it gives me I/O errors followed by a list of files and directories.
I am using slackware64 13.0 running kernel 2.6.29.6. Below I've provided the relevant lines from dmesg (edited out irrelevant lines to keep post under max character limit.) I'm beginning to suspect NFS has something to do with this, but I can't even begin to imagine how.
When this happens I'm able to umount -l the partition and remount it using the new /dev/sdh1 but eventually the same thing just happens and the whole drive switches back to /dev/sdg. This problem persists between reboots. It's also happened with an ext3 filesystem, in fact I switched to ext2 because it kept telling me "Aborting journal" and I was afraid I would get a corrupted journal and perhaps a destroyed file system. I just need someone to help me understand these errors in dmesg so I can figure out what's going on.
About 8 months ago I was doing some work at my brother's place and while down on the floor fiddling with cables I yanked this whole drive off the desk and it smashed into the floor (while spinning probably, I'm pretty sure this model is disk based.) I've been expecting to see some strange behavior since that happened, but it took a while and I can be certain this is related to that incident, although I'm rather convinced it is.
Thanks in advance for any help.
Code:
sd 5:0:0:0: [sdg] 976773168 512-byte hardware sectors: (500 GB/465 GiB)
sd 5:0:0:0: [sdg] Write Protect is off
sd 5:0:0:0: [sdg] Mode Sense: 34 00 00 00
sd 5:0:0:0: [sdg] Assuming drive cache: write through
sd 5:0:0:0: [sdg] 976773168 512-byte hardware sectors: (500 GB/465 GiB)
sd 5:0:0:0: [sdg] Write Protect is off
sd 5:0:0:0: [sdg] Mode Sense: 34 00 00 00
sd 5:0:0:0: [sdg] Assuming drive cache: write through
sdg: unknown partition table
sd 5:0:0:0: [sdg] Attached SCSI disk
sd 5:0:0:0: Attached scsi generic sg6 type 0
usb-storage: device scan complete
lp0: using parport0 (interrupt-driven).
lp0: console ready
....
usb-storage: device scan complete
NET: Registered protocol family 10
lo: Disabled Privacy Extensions
exportfs: exports duplicate symbol exportfs_decode_fh (owned by kernel)
sunrpc: module is already loaded
lockd: module is already loaded
Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery directory
NFSD: unable to find recovery directory /var/lib/nfs/v4recovery
NFSD: starting 90-second grace period
eth0: no IPv6 routers present
.......
sd 5:0:0:0: [sdg] 976773168 512-byte hardware sectors: (500 GB/465 GiB)
sd 5:0:0:0: [sdg] Write Protect is off
sd 5:0:0:0: [sdg] Mode Sense: 34 00 00 00
sd 5:0:0:0: [sdg] Assuming drive cache: write through
sdg: sdg1
.......
nfsd: last server has exited, flushing export cache
........
sd 6:0:0:0: [sdh] Unhandled error code
sd 6:0:0:0: [sdh] Result: hostbyte=0x00 driverbyte=0x00
end_request: I/O error, dev sdh, sector 610275
NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery directory
NFSD: unable to find recovery directory /var/lib/nfs/v4recovery
NFSD: starting 90-second grace period
.......
sd 8:0:0:0: [sdh] 976773168 512-byte hardware sectors: (500 GB/465 GiB)
sd 8:0:0:0: [sdh] Write Protect is off
sd 8:0:0:0: [sdh] Mode Sense: 34 00 00 00
sd 8:0:0:0: [sdh] Assuming drive cache: write through
sd 8:0:0:0: [sdh] 976773168 512-byte hardware sectors: (500 GB/465 GiB)
sd 8:0:0:0: [sdh] Write Protect is off
sd 8:0:0:0: [sdh] Mode Sense: 34 00 00 00
sd 8:0:0:0: [sdh] Assuming drive cache: write through
sdh: sdh1
sd 8:0:0:0: [sdh] Attached SCSI disk
sd 8:0:0:0: Attached scsi generic sg6 type 0
usb-storage: device scan complete
usb 1-3: USB disconnect, address 9
usb 1-3: new high speed USB device using ehci_hcd and address 10
usb 1-3: New USB device found, idVendor=059b, idProduct=0370
usb 1-3: New USB device strings: Mfr=10, Product=11, SerialNumber=5
usb 1-3: Product: External HD
usb 1-3: Manufacturer: Iomega
usb 1-3: SerialNumber: 924FFFFFFFFF
usb 1-3: configuration #1 chosen from 1 choice
scsi9 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 10
usb-storage: waiting for device to settle before scanning
scsi 9:0:0:0: Direct-Access ST350082 0AS PQ: 0 ANSI: 2 CCS
sd 9:0:0:0: [sdh] 976773168 512-byte hardware sectors: (500 GB/465 GiB)
sd 9:0:0:0: [sdh] Write Protect is off
sd 9:0:0:0: [sdh] Mode Sense: 34 00 00 00
sd 9:0:0:0: [sdh] Assuming drive cache: write through
sd 9:0:0:0: [sdh] 976773168 512-byte hardware sectors: (500 GB/465 GiB)
sd 9:0:0:0: [sdh] Write Protect is off
sd 9:0:0:0: [sdh] Mode Sense: 34 00 00 00
sd 9:0:0:0: [sdh] Assuming drive cache: write through
sdh: sdh1
sd 9:0:0:0: [sdh] Attached SCSI disk
sd 9:0:0:0: Attached scsi generic sg6 type 0
usb-storage: device scan complete
EXT2-fs error (device sdg1): ext2_get_inode: unable to read inode block - inode=23355393, block=93421570
------------[ cut here ]------------
WARNING: at fs/buffer.c:1247 mark_buffer_dirty+0x86/0xa0()
Hardware name: Aspire E380
Modules linked in: kvm_amd kvm snd_seq_dummy snd_seq_oss snd_seq_midi_event snd_seq snd_seq_device snd_pcm_oss snd_mixer_oss nfsd auth_rpcgss ipv6 joydev lp fuse nvidia(P) snd_hda_codec_realtek snd_hda_intel snd_hda_codec ppdev fan rfkill thermal rtc_cmos processor snd_hwdep rtc_core parport_pc snd_pcm rtc_lib led_class parport snd_timer thermal_sys sky2 snd psmouse k8temp sg wmi i2c_nforce2 button hwmon soundcore serio_raw snd_page_alloc evdev
Pid: 10922, comm: nfsd Tainted: P 2.6.29.6 #2
Call Trace:
[<ffffffff8023c50a>] warn_slowpath+0xea/0x160
[<ffffffff802363e8>] try_to_wake_up+0x138/0x1e0
[<ffffffff80252949>] autoremove_wake_function+0x9/0x30
[<ffffffff802318bb>] __wake_up_common+0x5b/0x90
[<ffffffff80231bb3>] __wake_up+0x43/0x70
[<ffffffff80232555>] set_next_entity+0x35/0x70
[<ffffffff808f9bfe>] thread_return+0x3d/0x78f
[<ffffffff80246ed4>] lock_timer_base+0x34/0x70
[<ffffffff802d2b26>] mark_buffer_dirty+0x86/0xa0
[<ffffffff80357429>] ext2_sync_super+0x39/0x60
[<ffffffff80358332>] ext2_error+0x102/0x130
[<ffffffff802d3550>] sync_buffer+0x0/0x50
[<ffffffff808fa384>] io_schedule+0x34/0x50
[<ffffffff80252a9a>] finish_wait+0x3a/0x90
[<ffffffff802d3550>] sync_buffer+0x0/0x50
[<ffffffff808fa819>] out_of_line_wait_on_bit+0x79/0xa0
[<ffffffff80252970>] wake_bit_function+0x0/0x30
[<ffffffff80354516>] ext2_get_inode+0x166/0x180
[<ffffffff80354950>] ext2_iget+0x80/0x400
[<ffffffff808c4c07>] sunrpc_cache_lookup+0x67/0x180
[<ffffffff80357008>] ext2_nfs_get_inode+0x38/0x70
[<ffffffff802cb4fb>] generic_fh_to_dentry+0x2b/0x50
[<ffffffff803bae83>] exportfs_decode_fh+0x63/0x2a0
[<ffffffffa0b46990>] nfsd_acceptable+0x0/0x110 [nfsd]
[<ffffffff808c436a>] cache_check+0x4a/0x4d0
[<ffffffffa0b4cd17>] exp_find_key+0x57/0xe0 [nfsd]
[<ffffffff80252940>] autoremove_wake_function+0x0/0x30
[<ffffffff80231fb0>] update_curr+0xe0/0x120
[<ffffffff80230f25>] place_entity+0x95/0xa0
[<ffffffffa0b4ce32>] exp_find+0x92/0xa0 [nfsd]
[<ffffffffa0b46e79>] fh_verify+0x369/0x680 [nfsd]
[<ffffffffa0b4750b>] nfsd_access+0x3b/0x160 [nfsd]
[<ffffffff808c436a>] cache_check+0x4a/0x4d0
[<ffffffffa0b51770>] nfsd3_proc_access+0x80/0xe0 [nfsd]
[<ffffffffa0b4323a>] nfsd_dispatch+0xba/0x270 [nfsd]
[<ffffffff808bb51b>] svc_process+0x4ab/0x810
[<ffffffff80236490>] default_wake_function+0x0/0x10
[<ffffffff808fbb07>] __down_read+0x17/0xaf
[<ffffffffa0b439a1>] nfsd+0x171/0x2a0 [nfsd]
[<ffffffffa0b43830>] nfsd+0x0/0x2a0 [nfsd]
[<ffffffff80252527>] kthread+0x47/0x90
[<ffffffff8020c93a>] child_rip+0xa/0x20
[<ffffffff802524e0>] kthread+0x0/0x90
[<ffffffff8020c930>] child_rip+0x0/0x20
---[ end trace 0ae183da81db8f2f ]---
EXT2-fs error (device sdg1): ext2_get_inode: unable to read inode block - inode=23355393, block=93421570
EXT2-fs error (device sdg1): ext2_get_inode: unable to read inode block - inode=23355393, block=93421570
EXT2-fs error (device sdg1): ext2_get_inode: unable to read inode block - inode=23355393, block=93421570
EXT2-fs error (device sdg1): ext2_get_inode: unable to read inode block - inode=23355393, block=93421570
EXT2-fs error (device sdg1): ext2_get_inode: unable to read inode block - inode=23355393, block=93421570
EXT2-fs error (device sdg1): ext2_get_inode: unable to read inode block - inode=23355393, block=93421570
EXT2-fs error (device sdg1): ext2_get_inode: unable to read inode block - inode=23355393, block=93421570
EXT2-fs error (device sdg1): ext2_get_inode: unable to read inode block - inode=23355393, block=93421570
EXT2-fs error (device sdg1): ext2_get_inode: unable to read inode block - inode=23355393, block=93421570
EXT2-fs error (device sdg1): ext2_get_inode: unable to read inode block - inode=23355393, block=93421570
EXT2-fs error (device sdg1): ext2_get_inode: unable to read inode block - inode=23355393, block=93421570
EXT2-fs error (device sdg1): ext2_get_inode: unable to read inode block - inode=23355393, block=93421570
usb 1-3: USB disconnect, address 10
usb 1-3: new high speed USB device using ehci_hcd and address 11
usb 1-3: New USB device found, idVendor=059b, idProduct=0370
usb 1-3: New USB device strings: Mfr=10, Product=11, SerialNumber=5
usb 1-3: Product: External HD
usb 1-3: Manufacturer: Iomega
usb 1-3: SerialNumber: 924FFFFFFFFF
usb 1-3: configuration #1 chosen from 1 choice
scsi10 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 11
usb-storage: waiting for device to settle before scanning
scsi 10:0:0:0: Direct-Access ST350082 0AS PQ: 0 ANSI: 2 CCS
sd 10:0:0:0: [sdh] 976773168 512-byte hardware sectors: (500 GB/465 GiB)
sd 10:0:0:0: [sdh] Write Protect is off
sd 10:0:0:0: [sdh] Mode Sense: 34 00 00 00
sd 10:0:0:0: [sdh] Assuming drive cache: write through
sd 10:0:0:0: [sdh] 976773168 512-byte hardware sectors: (500 GB/465 GiB)
sd 10:0:0:0: [sdh] Write Protect is off
sd 10:0:0:0: [sdh] Mode Sense: 34 00 00 00
sd 10:0:0:0: [sdh] Assuming drive cache: write through
sdh: sdh1
sd 10:0:0:0: [sdh] Attached SCSI disk
sd 10:0:0:0: Attached scsi generic sg6 type 0
usb-storage: device scan complete
usb 1-3: USB disconnect, address 11
usb 1-3: new high speed USB device using ehci_hcd and address 12
usb 1-3: New USB device found, idVendor=059b, idProduct=0370
usb 1-3: New USB device strings: Mfr=10, Product=11, SerialNumber=5
usb 1-3: Product: External HD
usb 1-3: Manufacturer: Iomega
usb 1-3: SerialNumber: 924FFFFFFFFF
usb 1-3: configuration #1 chosen from 1 choice
scsi11 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 12
usb-storage: waiting for device to settle before scanning
scsi 11:0:0:0: Direct-Access ST350082 0AS PQ: 0 ANSI: 2 CCS
sd 11:0:0:0: [sdh] 976773168 512-byte hardware sectors: (500 GB/465 GiB)
sd 11:0:0:0: [sdh] Write Protect is off
sd 11:0:0:0: [sdh] Mode Sense: 34 00 00 00
sd 11:0:0:0: [sdh] Assuming drive cache: write through
sd 11:0:0:0: [sdh] 976773168 512-byte hardware sectors: (500 GB/465 GiB)
sd 11:0:0:0: [sdh] Write Protect is off
sd 11:0:0:0: [sdh] Mode Sense: 34 00 00 00
sd 11:0:0:0: [sdh] Assuming drive cache: write through
sdh: sdh1
sd 11:0:0:0: [sdh] Attached SCSI disk
sd 11:0:0:0: Attached scsi generic sg6 type 0
usb-storage: device scan complete
usb 1-3: USB disconnect, address 12
usb 1-3: new high speed USB device using ehci_hcd and address 13
usb 1-3: New USB device found, idVendor=059b, idProduct=0370
usb 1-3: New USB device strings: Mfr=10, Product=11, SerialNumber=5
usb 1-3: Product: External HD
usb 1-3: Manufacturer: Iomega
usb 1-3: SerialNumber: 924FFFFFFFFF
usb 1-3: configuration #1 chosen from 1 choice
scsi12 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 13
usb-storage: waiting for device to settle before scanning
scsi 12:0:0:0: Direct-Access ST350082 0AS PQ: 0 ANSI: 2 CCS
sd 12:0:0:0: [sdh] 976773168 512-byte hardware sectors: (500 GB/465 GiB)
sd 12:0:0:0: [sdh] Write Protect is off
sd 12:0:0:0: [sdh] Mode Sense: 34 00 00 00
sd 12:0:0:0: [sdh] Assuming drive cache: write through
sd 12:0:0:0: [sdh] 976773168 512-byte hardware sectors: (500 GB/465 GiB)
sd 12:0:0:0: [sdh] Write Protect is off
sd 12:0:0:0: [sdh] Mode Sense: 34 00 00 00
sd 12:0:0:0: [sdh] Assuming drive cache: write through
sdh: sdh1
sd 12:0:0:0: [sdh] Attached SCSI disk
sd 12:0:0:0: Attached scsi generic sg6 type 0
usb-storage: device scan complete
usb 1-3: USB disconnect, address 13
usb 1-3: new high speed USB device using ehci_hcd and address 14
usb 1-3: New USB device found, idVendor=059b, idProduct=0370
usb 1-3: New USB device strings: Mfr=10, Product=11, SerialNumber=5
usb 1-3: Product: External HD
usb 1-3: Manufacturer: Iomega
usb 1-3: SerialNumber: 924FFFFFFFFF
usb 1-3: configuration #1 chosen from 1 choice
scsi13 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 14
usb-storage: waiting for device to settle before scanning
scsi 13:0:0:0: Direct-Access ST350082 0AS PQ: 0 ANSI: 2 CCS
sd 13:0:0:0: [sdh] 976773168 512-byte hardware sectors: (500 GB/465 GiB)
sd 13:0:0:0: [sdh] Write Protect is off
sd 13:0:0:0: [sdh] Mode Sense: 34 00 00 00
sd 13:0:0:0: [sdh] Assuming drive cache: write through
sd 13:0:0:0: [sdh] 976773168 512-byte hardware sectors: (500 GB/465 GiB)
sd 13:0:0:0: [sdh] Write Protect is off
sd 13:0:0:0: [sdh] Mode Sense: 34 00 00 00
sd 13:0:0:0: [sdh] Assuming drive cache: write through
sdh: sdh1
sd 13:0:0:0: [sdh] Attached SCSI disk
sd 13:0:0:0: Attached scsi generic sg6 type 0
usb-storage: device scan complete
usb 1-3: USB disconnect, address 14
usb 1-3: new high speed USB device using ehci_hcd and address 15
usb 1-3: New USB device found, idVendor=059b, idProduct=0370
usb 1-3: New USB device strings: Mfr=10, Product=11, SerialNumber=5
usb 1-3: Product: External HD
usb 1-3: Manufacturer: Iomega
usb 1-3: SerialNumber: 924FFFFFFFFF
usb 1-3: configuration #1 chosen from 1 choice
scsi14 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 15
usb-storage: waiting for device to settle before scanning
scsi 14:0:0:0: Direct-Access ST350082 0AS PQ: 0 ANSI: 2 CCS
sd 14:0:0:0: [sdh] 976773168 512-byte hardware sectors: (500 GB/465 GiB)
sd 14:0:0:0: [sdh] Write Protect is off
sd 14:0:0:0: [sdh] Mode Sense: 34 00 00 00
sd 14:0:0:0: [sdh] Assuming drive cache: write through
sd 14:0:0:0: [sdh] 976773168 512-byte hardware sectors: (500 GB/465 GiB)
sd 14:0:0:0: [sdh] Write Protect is off
sd 14:0:0:0: [sdh] Mode Sense: 34 00 00 00
sd 14:0:0:0: [sdh] Assuming drive cache: write through
sdh: sdh1
sd 14:0:0:0: [sdh] Attached SCSI disk
sd 14:0:0:0: Attached scsi generic sg6 type 0
usb-storage: device scan complete
usb 1-3: USB disconnect, address 15
usb 1-3: new high speed USB device using ehci_hcd and address 16
usb 1-3: New USB device found, idVendor=059b, idProduct=0370
usb 1-3: New USB device strings: Mfr=10, Product=11, SerialNumber=5
usb 1-3: Product: External HD
usb 1-3: Manufacturer: Iomega
usb 1-3: SerialNumber: 924FFFFFFFFF
usb 1-3: configuration #1 chosen from 1 choice
scsi15 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 16
usb-storage: waiting for device to settle before scanning
scsi 15:0:0:0: Direct-Access ST350082 0AS PQ: 0 ANSI: 2 CCS
sd 15:0:0:0: [sdh] 976773168 512-byte hardware sectors: (500 GB/465 GiB)
sd 15:0:0:0: [sdh] Write Protect is off
sd 15:0:0:0: [sdh] Mode Sense: 34 00 00 00
sd 15:0:0:0: [sdh] Assuming drive cache: write through
sd 15:0:0:0: [sdh] 976773168 512-byte hardware sectors: (500 GB/465 GiB)
sd 15:0:0:0: [sdh] Write Protect is off
sd 15:0:0:0: [sdh] Mode Sense: 34 00 00 00
sd 15:0:0:0: [sdh] Assuming drive cache: write through
sdh: sdh1
sd 15:0:0:0: [sdh] Attached SCSI disk
sd 15:0:0:0: Attached scsi generic sg6 type 0
usb-storage: device scan complete
EXT2-fs error (device sdg1): ext2_get_inode: unable to read inode block - inode=23355393, block=93421570
EXT2-fs error (device sdg1): ext2_get_inode: unable to read inode block - inode=23355393, block=93421570
EXT2-fs error (device sdg1): ext2_get_inode: unable to read inode block - inode=23355393, block=93421570
Clocksource tsc unstable (delta = 62500538 ns)
EXT2-fs error (device sdg1): ext2_get_inode: unable to read inode block - inode=23355393, block=93421570
EXT2-fs error (device sdg1): ext2_get_inode: unable to read inode block - inode=23355393, block=93421570
EXT2-fs error (device sdg1): ext2_get_inode: unable to read inode block - inode=23355393, block=93421570
EXT2-fs error (device sdg1): ext2_get_inode: unable to read inode block - inode=23355393, block=93421570
EXT2-fs error (device sdg1): ext2_get_inode: unable to read inode block - inode=23355393, block=93421570
EXT2-fs error (device sdg1): ext2_get_inode: unable to read inode block - inode=23355393, block=93421570
EXT2-fs error (device sdg1): ext2_get_inode: unable to read inode block - inode=23355393, block=93421570
EXT2-fs error (device sdg1): ext2_get_inode: unable to read inode block - inode=23355393, block=93421570
EXT2-fs error (device sdg1): ext2_get_inode: unable to read inode block - inode=23355393, block=93421570
EXT2-fs error (device sdg1): ext2_get_inode: unable to read inode block - inode=23355393, block=93421570
EXT2-fs error (device sdg1): ext2_get_inode: unable to read inode block - inode=23355393, block=93421570
EXT2-fs error (device sdg1): ext2_get_inode: unable to read inode block - inode=23355393, block=93421570
EXT2-fs error (device sdg1): ext2_get_inode: unable to read inode block - inode=23355393, block=93421570
EXT2-fs error (device sdg1): ext2_get_inode: unable to read inode block - inode=23355393, block=93421570
EXT2-fs error (device sdg1): ext2_get_inode: unable to read inode block - inode=23355393, block=93421570
EXT2-fs error (device sdg1): ext2_get_inode: unable to read inode block - inode=23355393, block=93421570
EXT2-fs error (device sdg1): ext2_get_inode: unable to read inode block - inode=23355393, block=93421570
EXT2-fs error (device sdg1): ext2_get_inode: unable to read inode block - inode=23355393, block=93421570
EXT2-fs error (device sdg1): ext2_get_inode: unable to read inode block - inode=23355393, block=93421570
EXT2-fs error (device sdg1): ext2_get_inode: unable to read inode block - inode=23355393, block=93421570
EXT2-fs error (device sdg1): ext2_get_inode: unable to read inode block - inode=23355393, block=93421570
EXT2-fs error (device sdg1): ext2_get_inode: unable to read inode block - inode=23355393, block=93421570
EXT2-fs error (device sdg1): ext2_get_inode: unable to read inode block - inode=23355393, block=93421570
EXT2-fs error (device sdg1): ext2_get_inode: unable to read inode block - inode=23355393, block=93421570
EXT2-fs error (device sdg1): ext2_get_inode: unable to read inode block - inode=23355393, block=93421570
EXT2-fs error (device sdg1): ext2_get_inode: unable to read inode block - inode=23355393, block=93421570
EXT2-fs error (device sdg1): ext2_get_inode: unable to read inode block - inode=23355393, block=93421570
EXT2-fs error (device sdg1): ext2_get_inode: unable to read inode block - inode=23355393, block=93421570
EXT2-fs error (device sdg1): ext2_get_inode: unable to read inode block - inode=23355393, block=93421570
EXT2-fs error (device sdg1): ext2_get_inode: unable to read inode block - inode=23355393, block=93421570
EXT2-fs error (device sdg1): ext2_get_inode: unable to read inode block - inode=23355393, block=93421570
EXT2-fs error (device sdg1): ext2_get_inode: unable to read inode block - inode=23355393, block=93421570
EXT2-fs error (device sdg1): ext2_get_inode: unable to read inode block - inode=23355393, block=93421570
EXT2-fs error (device sdg1): ext2_get_inode: unable to read inode block - inode=23355393, block=93421570
EXT2-fs error (device sdg1): ext2_get_inode: unable to read inode block - inode=23355393, block=93421570
EXT2-fs error (device sdg1): ext2_get_inode: unable to read inode block - inode=23355393, block=93421570
EXT2-fs error (device sdg1): ext2_get_inode: unable to read inode block - inode=23355393, block=93421570
EXT2-fs error (device sdg1): ext2_get_inode: unable to read inode block - inode=23355393, block=93421570
EXT2-fs error (device sdg1): ext2_get_inode: unable to read inode block - inode=23355393, block=93421570
EXT2-fs error (device sdg1): ext2_get_inode: unable to read inode block - inode=23355393, block=93421570
EXT2-fs error (device sdg1): ext2_get_inode: unable to read inode block - inode=26361857, block=105447426
EXT2-fs error (device sdg1): ext2_get_inode: unable to read inode block - inode=23355393, block=93421570
EXT2-fs error (device sdg1): ext2_get_inode: unable to read inode block - inode=7135233, block=28540930
EXT2-fs error (device sdg1): ext2_get_inode: unable to read inode block - inode=30408705, block=121634818
EXT2-fs error (device sdg1): ext2_get_inode: unable to read inode block - inode=20447233, block=81788930
EXT2-fs error (device sdg1): ext2_get_inode: unable to read inode block - inode=2, block=1027
Last edited by indubitableness; 02-23-2010 at 06:27 AM.
You may be getting power fluctuations, or access interruptions which cause the drive to be unmounted then remounted periodically. sdh is the next designation in line if sdg is already mounted. Your system thinks there are two drives attached but there obviously aren't. Damage to the drive or the USB/Firewire interface I would guess.
I agree that an intermittent electrical connection could do it, although I would have thought that the system would not assign sdh unless it saw that sdg was in use.
Personally, I would not trust a hard drive that had been dropped (running or not). How is this drive being used?
I agree that an intermittent electrical connection could do it, although I would have thought that the system would not assign sdh unless it saw that sdg was in use.
it would depend on the polling interval I guess. Maybe there is enough time for sdh to be assigned before the system notices sdg is missing ?
I use this drive primarily as an NFS share for media files I often need access to. It is not the primary storage drive for any of the files it holds and it is non-essential, if it dies it dies, and I'll be sad, but it can be replaced. It USED to be a back up drive, but that was before I dropped it.
As for the power supply the HDD has it's own plug and does not rely on the USB to provide power to it. Perhaps I should try a new plug? The power cord has never seen any wear or damage and should physically be in very good condition. I'll try to find a new power supply that provides an identical power output and see if the problem persists.
I'll also try another USB cord; although the same is true for this cord that it has never really been stressed except perhaps the time I pulled on it and the HDD fell, but I can't imagine that damaging the cord.
Is there anything else that could cause this? For now I'm still inclined to believe these symptoms are directly related to when it fell, but there's really no way for me the be certain. These symptoms only started appearing after I stopped using Samba in favor of NFS, but they did not appear for almost a month after the switch.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.