UbuntuThis forum is for the discussion of Ubuntu 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.
I was watching a video file from a EXT-4 formatted drive I had connected via eSATA when part way through VLC stopped playing. I closed VLC and reopened the file only to get an error in the Dolphin status bar that read:
Quote:
An error occurred while accessing 'Videos', the system responded: [close button]
I also get this when attempting to mount the drive.
/var/log/syslog is full of the following errors:
mark@nettop:~$ sudo fsck -C /dev/sdb
[sudo] password for mark:
fsck from util-linux-ng 2.17.2
e2fsck 1.41.11 (14-Mar-2010)
fsck.ext2: Attempt to read block from filesystem resulted in short read while trying to open /dev/sdb
Could this be a zero-length partition?
mark@nettop:~$
Attempting to run fdisk on the partition (/dev/sdb1) instead gives the same output.
What happened here, has my relatively new 1TB drive suddenly died on me?
I was able to mount it as normal when I tried later (the computer had been powered off and on again since). However, part way through copying data to it I got errors that it couldn't be written. I kicked off a badblocks on it and came back to find it endlessly spamming out 'Invalid argument during seek' errors.
I ran the latest Samsung diagnostic from UBCD 4.1.1 but while it detected the drive it said that it wasn't supported. I tried the next oldest one and it couldn't detect it.
After that I ran Parted Magic from UBCD 5.0.2 performing both basic and extended SMART tests from there didn't find anything but did give some interesting information about the last 5 problems, though it doesn't mean much to me. I've attached the output to the post for anyone who's having the same problem or who's interested in taking a look.
The issue is consistent and reproducible and I'm willing to throw a fair bit of time and effort at this problem to solve it because I really don't want all that data to go. Any tests anyone can suggest would be welcome.
Drive looks dead to me. Infant mortality; only 28 hours. Either that, or the time counter has just rolled over, but it claims to have been running for only 28 hours.
I have exactly one suggestion for you, and that is to try Spinrite on the drive. The utility costs $89, but if the drive is at all recoverable, Spinrite will recover it.
If you have a hardware fault in the silicon, spinrite won't help you. If, however, you have some sort of media problem, spinrite might just save you. The errors you are reporting are ambiguous; I am not sure if it is hardware or media (could be either).
I hope it's still under warranty or I'll never buy another Samsung drive again. Just run fsck.ext4 on it and got a quite different result to when I ran fsck initially.
Quote:
mark@nettop:~$ sudo fsck.ext4 /dev/sdb
[sudo] password for mark:
e2fsck 1.41.11 (14-Mar-2010)
fsck.ext4: Superblock invalid, trying backup blocks...
fsck.ext4: Bad magic number in super-block while trying to open /dev/sdb
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
mark@nettop:~$
Are my problems likely down to something with EXT4 or the drive itself? Is there any chance at all that the drive itself isn't actually dead before I go out and buy a replacement?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.