I needed GPartEd to format a MicroSD card (don't trust Disk Utility too much as more problems seem to occur with hard drives and memory cards I formatted with it, than with the ones I formatted wth GPartEd), and almost got a heart attack... There's a damaged partition on my new hard drive (a bit more than 2 months old)!
Luckily it was only my SWAP partition, but still...
I'd like to know a few things...
- How to rule out the possibility of hardware failure.
- How this can happen if the problem's not hardware-related.
- I only installed Linux once on this computer (waited for Ubuntu 12.04 to get released), so it's not a SWAP partition that remains from an earlier installation.
- What can be the cause of physical hard drive damage.
- The computer hasn't fallen of a desk or anything...
- How to prevent this in future, if at all possible.
- Additional: Whether it's normal that reading (and writing as well, I think) speed drops significantly over a minute time; and if it's not, what are some possible ways to analyse/fix the issue?
No problem if you can't answer all of my questions.
Information
It's a read-only benchmark.
The partition labeled Windows holds a Windows 7 installation I'm supposed to need some time for school, and I used before Ubuntu 12.04 got released. I have booted it up a few times after Ubuntu 12.04 was installed (I don't know whether Windows' disk check can do any harm to Linux partitions, but it always seems to run a checkdisk after I changed my partition table layout with a Linux application like GPartEd)./dev/sda7
is the SWAP partition I'm talking about.
I guess my best option now is just try to boot a Live CD and format /dev/sda7
again? It won't format it from my installed Ubuntu system.
Just a shoot in the dark, but IMHO your swap partition isn't damaged at all. I've already seen discrepancies between
fdisk
andgparted
and, it's sad to say, but fdisk is almost always right.Try a:
you should see that your swap space is actually in use (or at least I hope so).
The explaination for that "unreadable"
/dev/mapper/cryptswap1
partition is thatcryptswap1
is actually a mapped encrypted swapspace, so it should be fine that no one can understand what's in there. If you want to disable it, you can look at this thread: How to disable cryptswap?Last but not least, your
SMART
status: at first sight (just watching the read error rate and the seek error rate), I'd have said that your drive was about to melt down. But, no, it's fine, I have a drive whoseSMART
says exactly the same. I'll post the full output just for reference (both for me and others) for future visits.And I have another drive that looks more "normal":
And another one with some "real" error, that however is still alive after several months of tiny complaints:
For what concerns the read speed benchmark, I think that a speed decrease over time is normal. I suspect that caching mechanisms make the disk appear faster in the initial phase of testing, and slower at the end. However I see that your "worst" read speed is around 80MB/s that is well above my "best average" read speed (around 60MB/s), so I wouldn't worry about this aspect.
(Intended as a comment, but too big...)
The gparted error is just that it is unable to detect the filesystem (read: it is probably reading the partition data and trying to detect the filesystem type).
fdisk
is listing the partition table, just that, and there the entry says it's a swap partition (this has nothing to do with the filesystem, it's the partition type entry in the partition table,fdisk
doesn't even try to autodetect the filesystem type).The
fdsik
output you show mentions acryptswap
device, which, I assume, is an encryption layer over the swap partition. So that means your swap partition is probably encrypted.If that's the case, then
gparted
is reading the swap partition itself, but will probably just find encrypted data that does not seem to be any usable filesystem nor a swap partition, because data there is encrypted and can only be accessed (in its clear, decrypted form) through thatcryptswap
device.And if the swap is in use, and the encrypted data is currently being decrypted at the
cryptswap
device, this also means the partition is in use, explaining the "device or resource busy" error.Just to check whether this is the issue, can you share the output of running in a terminal
/sbin/swapon -s
? And perhaps also the content of/etc/fstab
?