Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
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.
I have a 500 GB Seagate hard drive that's about 3-1/2 years old. It only has 16.88 GB of data on it. PCLOS was running very flacky so I popped in a live disk of Vector. When it booted, S.M.A.R.T said that the hard drive was failing so I backed up everything. Since then I haven't written anything to the hard drive. I also blew out a lot of dust from inside the case.
Today I booted a live disk of Salix OS. Ran fsck, badblocks and S.M.A.R.T. and got conflicting results. fsck and badblocks say the hard drive's OK, but S.M.A.R.T. says it's going to fail within hours.
umount /dev/sda gives the message that it's unmounted already. But then doing fsck on /dev/sda gives the message that the drive is mounted or busy.
/sda1 is the large partition on /dev/sda where I store my data.
Can anyone interpret these outputs?
Let me know what other information you need. As usual, I'm just lost ...
root[one]# umount /dev/sda
umount: /dev/sda: not mounted
root[one]# fsck -t ext3 /dev/sda
fsck from util-linux-ng 2.17.2
e2fsck 1.41.11 (14-Mar-2010)
/sbin/e2fsck: Device or resource busy while trying to open /dev/sda
Filesystem mounted or opened exclusively by another program?
Please use code-tags for output of programs in the future, it makes your posts much more readable and preserves the formatting.
To your problem: That you can't mount/unmount /dev/sda is pretty normal, since you state that it is partitioned. You can only mount file-systems, not whole partitioned disks. The smartctl output indicates that the disk is dying and I personally would trust that program. To be sure you can test the disk with the manufacturer's diagnosis tool.
If you use the advanced editor you can just mark the part of your post that you want to put into code-tags and press the #-button above the input field.
You cans also do it manually with writing the tags , for example [code]lspci[/code] will look like this:
why would not trust the output of smartctl? Call me cynical but I would rather doubt the results of the manufacturers test disk as it would surely give favorable results, no?
I've found the smart test on partedmagic to have accuratly predicted a drive's demise several times.It certainly gives more details than some test disks from some manufacturers.
why would not trust the output of smartctl?
Isn't that what I stated?
Call me cynical but I would rather doubt the results of the manufacturers test disk as it would surely give favorable results, no?
Actually no. If a major customer of that manufacturer, let's say someone running large server-farms, tests disks with that tool and they find out that the tool is giving inaccurate results you can be sure that there will be a) a major law-suit, and b) a change to a different manufacturer. While sometimes a little bit of mistrust is good, there are situations where it is simply misplaced.
I tend to trust the OEM's extended drive tests. They have more insight to their own equipment. I doubt they'd risk an intentional error that made their product look good. Smart is most of but not the entire diags being run. The long test is the best test to use for hard drives.