[Solved-hopefully]Hard Disk error?
Posted: Wed Oct 31, 2012 7:51 am
Hello!
I've been using Linux Mint for about 3 months now without any problems (except for fglrx... ) but now I've found a great problem, however, I'm not sure if it's Mint's fault or not.
I have a new 2 TB Western Digital Caviar Green HDD (wd20earx), it's 3 months old just like my Mint installation. It used to have MBR and a single 2 TB NTFS partition. Yesterday when I woke up I found nothing on it, after looking at it with HD Sentinel (from a Windows) it said that it's half-formatted (and with full format, not with quick!) with ext4 which happened the previous day at ~20:30. However, at that time the only running thing was Linux Mint and a Chromium (without root rights of course) browser. I didn't notice a single thing about it neither a window asking "is it okay if I kill your HDD?" or any suspicious sounds of heavy disk-usage due to formatting. The HDD's SMART looks 98% fine too. At (Oct 29) 21:15:38 I've shut down the system. The HDD was mounted the whole day just like for 3 months before where nothing wrong happened. I used it that day too and as I remember I used it (write+read too) at ~20:00 last time that day.
I also can't find any error message related to this, only one from ~17:45, from syslog:
Oct 29 17:44:17 MikiMint kernel: [21655.808037] ata5.00: exception Emask 0x10 SAct 0x0 SErr 0x4050002 action 0xe frozen
Oct 29 17:44:17 MikiMint kernel: [21655.808042] ata5: SError: { RecovComm PHYRdyChg CommWake DevExch }
Oct 29 17:44:17 MikiMint kernel: [21655.808044] ata5.00: failed command: SMART
Oct 29 17:44:17 MikiMint kernel: [21655.808048] ata5.00: cmd b0/da:00:00:4f:c2/00:00:00:00:00/00 tag 0
Oct 29 17:44:17 MikiMint kernel: [21655.808049] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x14 (ATA bus error)
Oct 29 17:44:17 MikiMint kernel: [21655.808051] ata5.00: status: { DRDY }
Oct 29 17:44:17 MikiMint kernel: [21655.808058] ata5: hard resetting link
Oct 29 17:44:18 MikiMint kernel: [21656.688120] ata5: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Oct 29 17:44:18 MikiMint kernel: [21656.745126] ata5.00: configured for UDMA/133
Oct 29 17:44:18 MikiMint kernel: [21656.745150] ata5: EH complete
Smart says ~20 days online, and ~500 read errors, the only other non-zero values are power on/off related.
Luckily 99% of the data was backed up, so I was lucky this time but I'm afraid that it might happen again...
Is it possible that Mint noticed a serious HDD error and then tried to fix it without asking(!) first?
Any ideas why it happened?
Also, what other log files, data, etc. should I attach?
Thanks in advance!
Garmine
P.s.:
I've checked my other HDDs' SMART:
A 1.2 yrs runned 1 TB says 1 read errors,
while the other, 1 yrs runned 80GB says 0 read errors,
but the new has 500 read errors in only 20 days!
Please say that I'm wrong but then it's an HDD fault, isn't it? :S
I've been using Linux Mint for about 3 months now without any problems (except for fglrx... ) but now I've found a great problem, however, I'm not sure if it's Mint's fault or not.
I have a new 2 TB Western Digital Caviar Green HDD (wd20earx), it's 3 months old just like my Mint installation. It used to have MBR and a single 2 TB NTFS partition. Yesterday when I woke up I found nothing on it, after looking at it with HD Sentinel (from a Windows) it said that it's half-formatted (and with full format, not with quick!) with ext4 which happened the previous day at ~20:30. However, at that time the only running thing was Linux Mint and a Chromium (without root rights of course) browser. I didn't notice a single thing about it neither a window asking "is it okay if I kill your HDD?" or any suspicious sounds of heavy disk-usage due to formatting. The HDD's SMART looks 98% fine too. At (Oct 29) 21:15:38 I've shut down the system. The HDD was mounted the whole day just like for 3 months before where nothing wrong happened. I used it that day too and as I remember I used it (write+read too) at ~20:00 last time that day.
I also can't find any error message related to this, only one from ~17:45, from syslog:
Oct 29 17:44:17 MikiMint kernel: [21655.808037] ata5.00: exception Emask 0x10 SAct 0x0 SErr 0x4050002 action 0xe frozen
Oct 29 17:44:17 MikiMint kernel: [21655.808042] ata5: SError: { RecovComm PHYRdyChg CommWake DevExch }
Oct 29 17:44:17 MikiMint kernel: [21655.808044] ata5.00: failed command: SMART
Oct 29 17:44:17 MikiMint kernel: [21655.808048] ata5.00: cmd b0/da:00:00:4f:c2/00:00:00:00:00/00 tag 0
Oct 29 17:44:17 MikiMint kernel: [21655.808049] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x14 (ATA bus error)
Oct 29 17:44:17 MikiMint kernel: [21655.808051] ata5.00: status: { DRDY }
Oct 29 17:44:17 MikiMint kernel: [21655.808058] ata5: hard resetting link
Oct 29 17:44:18 MikiMint kernel: [21656.688120] ata5: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Oct 29 17:44:18 MikiMint kernel: [21656.745126] ata5.00: configured for UDMA/133
Oct 29 17:44:18 MikiMint kernel: [21656.745150] ata5: EH complete
Smart says ~20 days online, and ~500 read errors, the only other non-zero values are power on/off related.
Luckily 99% of the data was backed up, so I was lucky this time but I'm afraid that it might happen again...
Is it possible that Mint noticed a serious HDD error and then tried to fix it without asking(!) first?
Any ideas why it happened?
Also, what other log files, data, etc. should I attach?
Thanks in advance!
Garmine
P.s.:
I've checked my other HDDs' SMART:
A 1.2 yrs runned 1 TB says 1 read errors,
while the other, 1 yrs runned 80GB says 0 read errors,
but the new has 500 read errors in only 20 days!
Please say that I'm wrong but then it's an HDD fault, isn't it? :S