Over the past week or so the machine has been a little slow and has had a total lockup( this is the first time I have had a full lockup on the linux machine) This meant I had to reset the machine but all seems fine… check
This is a part of the messages log:
Aug 22 23:49:27 linux-office smartd[3547]: Device: /dev/sda, 2 Currently unreadable (pending) sectors
Aug 22 23:49:27 linux-office smartd[3547]: Device: /dev/sda, 2 Offline uncorrectable sectors
Aug 22 23:49:27 linux-office smartd[3547]: Device: /dev/sda, SMART Usage Attribute: 190 Temperature_Celsius changed from 55 to 56
Aug 22 23:49:27 linux-office smartd[3547]: Device: /dev/sda, SMART Usage Attribute: 194 Temperature_Celsius changed from 45 to 44
Aug 22 23:49:27 linux-office smartd[3547]: Device: /dev/sdb, SMART Usage Attribute: 194 Temperature_Celsius changed from 125 to 127
Aug 23 00:00:01 linux-office /usr/sbin/cron[4912]: (root) CMD ( test -x /usr/lib/secchk/security-control.sh && /usr/lib/secchk/security-control.sh daily &)
Aug 23 00:19:26 linux-office smartd[3547]: Device: /dev/sda, 2 Currently unreadable (pending) sectors
Aug 23 00:19:26 linux-office smartd[3547]: Device: /dev/sda, 2 Offline uncorrectable sectors
Aug 23 00:48:53 linux-office syslog-ng[2138]: STATS: dropped 0
Aug 23 00:49:26 linux-office smartd[3547]: Device: /dev/sda, 2 Currently unreadable (pending) sectors
Aug 23 00:49:26 linux-office smartd[3547]: Device: /dev/sda, 2 Offline uncorrectable sectors
Aug 23 01:19:26 linux-office smartd[3547]: Device: /dev/sda, 2 Currently unreadable (pending) sectors
Aug 23 01:19:26 linux-office smartd[3547]: Device: /dev/sda, 2 Offline uncorrectable sectors
Aug 23 01:48:53 linux-office syslog-ng[2138]: STATS: dropped 0
Aug 23 01:49:26 linux-office smartd[3547]: Device: /dev/sda, 2 Currently unreadable (pending) sectors
Aug 23 01:49:26 linux-office smartd[3547]: Device: /dev/sda, 2 Offline uncorrectable sectors
I booted up in Mint light to run a e2fsck on the drive this came back clean when run but when opening the drive shows unreadable sectors.
My question can i run the e2fsck on bootup?
>
> Over the past week or so the machine has been a little slow and has had
> a total lockup( this is the first time I have had a full lockup on the
> linux machine) This meant I had to reset the machine but all seems
> fine… check
>
> This is a part of the messages log:
>
>
> Code:
> --------------------
> Aug 22 23:49:27 linux-office smartd[3547]: Device: /dev/sda, 2
> Currently unreadable (pending) sectors Aug 22 23:49:27 linux-office
> smartd[3547]: Device: /dev/sda, 2 Offline uncorrectable sectors Aug 22
> 23:49:27 linux-office smartd[3547]: Device: /dev/sda, SMART Usage
> Attribute: 190 Temperature_Celsius changed from 55 to 56 Aug 22 23:49:27
> linux-office smartd[3547]: Device: /dev/sda, SMART Usage Attribute: 194
> Temperature_Celsius changed from 45 to 44 Aug 22 23:49:27 linux-office
> smartd[3547]: Device: /dev/sdb, SMART Usage Attribute: 194
> Temperature_Celsius changed from 125 to 127 Aug 23 00:00:01
> linux-office /usr/sbin/cron[4912]: (root) CMD ( test
> -x /usr/lib/secchk/security-control.sh
> && /usr/lib/secchk/security-control.sh daily &) Aug 23 00:19:26
> linux-office smartd[3547]: Device: /dev/sda, 2 Currently unreadable
> (pending) sectors Aug 23 00:19:26 linux-office smartd[3547]:
> Device: /dev/sda, 2 Offline uncorrectable sectors Aug 23 00:48:53
> linux-office syslog-ng[2138]: STATS: dropped 0 Aug 23 00:49:26 linux-office
> smartd[3547]: Device: /dev/sda, 2 Currently unreadable (pending) sectors
> Aug 23 00:49:26 linux-office smartd[3547]: Device: /dev/sda, 2 Offline
> uncorrectable sectors Aug 23 01:19:26 linux-office smartd[3547]:
> Device: /dev/sda, 2 Currently unreadable (pending) sectors Aug 23 01:19:26
> linux-office smartd[3547]: Device: /dev/sda, 2 Offline uncorrectable
> sectors Aug 23 01:48:53 linux-office syslog-ng[2138]: STATS: dropped 0 Aug
> 23 01:49:26 linux-office smartd[3547]: Device: /dev/sda, 2 Currently
> unreadable (pending) sectors Aug 23 01:49:26 linux-office smartd[3547]:
> Device: /dev/sda, 2 Offline uncorrectable sectors --------------------
>
> I booted up in Mint light to run a e2fsck on the drive this came back
> clean when run but when opening the drive shows unreadable sectors.
> My question can i run the e2fsck on bootup?
>
> This may also be relivant the name of the drive a square (see image as
> I cant create name.)
> 'http://www.kungfu.dyndns.org/drivename.jpg
> ’ (http://www.kungfu.dyndns.org/drivename.jpg)
> Cheers
>
> Dave
>
>
You could try forcing the drive to perform a long-type surface scan which
should find and ‘move/remap’ the bad sectors.
Boot system using rescue disk (or mint, I suppose), just don’t want to be
using ‘sda’ at all during test.
Type the command:
smartctl -t long /dev/sda
This should display an expected duration of testing… go find something else
to do for AT LEAST that period of time. Then reboot machine and see if that
has helped any. The ‘long-type’ scan causes the drive’s internal processor
to attempt to read, then write every sector. If it finds an error, it tries
to fix it, and then ‘remaps’ it so that a reserved good sector is used in its
place. This is all internal to the drive, no software or program is needed
to handle any remappings… actually, they’ll be totally transparent to a
user, with possibly a tiny detectable delay as the drive automatically uses
the remapped sector during reads or writes.
it didn’t appear to find any issues but I do get a different output on the messageslog.
Aug 25 13:06:05 linux-office smartd[3467]: smartd version 5.37 [i686-suse-linux-gnu] Copyright (C) 2002-6 Bruce Allen
Aug 25 13:06:05 linux-office smartd[3467]: Home page is http://smartmontools.sourceforge.net/
Aug 25 13:06:05 linux-office smartd[3467]: Opened configuration file /etc/smartd.conf
Aug 25 13:06:05 linux-office smartd[3467]: Drive: DEVICESCAN, implied '-a' Directive on line 27 of file /etc/smartd.conf
Aug 25 13:06:05 linux-office smartd[3467]: Configuration file /etc/smartd.conf was parsed, found DEVICESCAN, scanning devices
Aug 25 13:06:05 linux-office smartd[3467]: Problem creating device name scan list
Aug 25 13:06:05 linux-office smartd[3467]: Device: /dev/sda, opened
Aug 25 13:06:05 linux-office smartd[3467]: Device /dev/sda: ATA disk detected behind SAT layer
Aug 25 13:06:05 linux-office smartd[3467]: Try adding '-d sat' to the device line in the smartd.conf file.
Aug 25 13:06:05 linux-office smartd[3467]: For example: '/dev/sda -a -d sat'
Aug 25 13:06:05 linux-office smartd[3467]: Device: /dev/sdb, opened
Aug 25 13:06:05 linux-office smartd[3467]: Device /dev/sdb: ATA disk detected behind SAT layer
Aug 25 13:06:05 linux-office smartd[3467]: Try adding '-d sat' to the device line in the smartd.conf file.
Aug 25 13:06:05 linux-office smartd[3467]: For example: '/dev/sdb -a -d sat'
Aug 25 13:06:05 linux-office smartd[3467]: Device: /dev/sdc, opened
Aug 25 13:06:05 linux-office smartd[3467]: Device /dev/sdc: ATA disk detected behind SAT layer
Aug 25 13:06:05 linux-office smartd[3467]: Try adding '-d sat' to the device line in the smartd.conf file.
Aug 25 13:06:05 linux-office smartd[3467]: For example: '/dev/sdc -a -d sat'
Aug 25 13:06:05 linux-office smartd[3467]: Device: /dev/sda, opened
Aug 25 13:06:06 linux-office smartd[3467]: Device: /dev/sda, not found in smartd database.
Aug 25 13:06:06 linux-office smartd[3467]: Device: /dev/sda, is SMART capable. Adding to "monitor" list.
Aug 25 13:06:06 linux-office smartd[3467]: Device: /dev/sdb, opened
Aug 25 13:06:06 linux-office smartd[3467]: Device: /dev/sdb, found in smartd database.
Aug 25 13:06:07 linux-office smartd[3467]: Device: /dev/sdb, is SMART capable. Adding to "monitor" list.
Aug 25 13:06:07 linux-office smartd[3467]: Device: /dev/sdc, opened
Aug 25 13:06:07 linux-office smartd[3467]: Device: /dev/sdc, found in smartd database.
Aug 25 13:06:07 linux-office sshd[3516]: Server listening on 0.0.0.0 port 22.
Aug 25 13:06:07 linux-office kernel: vboxdrv: Trying to deactivate the NMI watchdog permanently...
Aug 25 13:06:07 linux-office kernel: vboxdrv: Successfully done.
Aug 25 13:06:07 linux-office smartd[3467]: Device: /dev/sdc, is SMART capable. Adding to "monitor" list.
Aug 25 13:06:07 linux-office smartd[3467]: Monitoring 3 ATA and 0 SCSI devices
Aug 25 13:06:07 linux-office smartd[3467]: Device: /dev/sda, 2 Currently unreadable (pending) sectors
Aug 25 13:06:07 linux-office smartd[3467]: Sending warning via /usr/lib/smartmontools/smart-notify to root@localhost ...
Aug 25 13:06:08 linux-office smartd[3467]: Warning via /usr/lib/smartmontools/smart-notify to root@localhost produced unexpected output (52 bytes) to STDOUT/STDERR: method return sender=:1.9 -> dest=:1.10 uint16 0
Aug 25 13:06:08 linux-office smartd[3467]: Warning via /usr/lib/smartmontools/smart-notify to root@localhost: successful
Aug 25 13:06:08 linux-office smartd[3467]: Device: /dev/sda, 2 Offline uncorrectable sectors
Aug 25 13:06:08 linux-office smartd[3467]: Sending warning via /usr/lib/smartmontools/smart-notify to root@localhost ...
Aug 25 13:06:08 linux-office smartd[3467]: Warning via /usr/lib/smartmontools/smart-notify to root@localhost produced unexpected output (52 bytes) to STDOUT/STDERR: method return sender=:1.9 -> dest=:1.11 uint16 0
Aug 25 13:06:08 linux-office smartd[3467]: Warning via /usr/lib/smartmontools/smart-notify to root@localhost: successful
Aug 25 13:06:09 linux-office smartd[3606]: smartd has fork()ed into background mode. New PID=3606.
Aug 25 13:36:09 linux-office smartd[3606]: Device: /dev/sda, 2 Currently unreadable (pending) sectors
Aug 25 13:36:09 linux-office smartd[3606]: Device: /dev/sda, 2 Offline uncorrectable sectors
Aug 25 13:36:09 linux-office smartd[3606]: Device: /dev/sda, SMART Prefailure Attribute: 7 Seek_Error_Rate changed from 81 to 82
Aug 25 13:36:09 linux-office smartd[3606]: Device: /dev/sda, SMART Usage Attribute: 190 Temperature_Celsius changed from 54 to 53
Aug 25 13:36:09 linux-office smartd[3606]: Device: /dev/sda, SMART Usage Attribute: 194 Temperature_Celsius changed from 46 to 47
Aug 25 13:36:09 linux-office smartd[3606]: Device: /dev/sda, SMART Usage Attribute: 195 Hardware_ECC_Recovered changed from 78 to 69
Aug 25 13:36:09 linux-office smartd[3606]: Device: /dev/sdb, SMART Usage Attribute: 194 Temperature_Celsius changed from 125 to 119
my next step is backup the contents of the drive to my other drives and either reinstall and reformat the drive…???
>
> Over the past week or so the machine has been a little slow and has had
> a total lockup( this is the first time I have had a full lockup on the
> linux machine) This meant I had to reset the machine but all seems
> fine… check
>
> This is a part of the messages log:
>
>
> Code:
> --------------------
> Aug 22 23:49:27 linux-office smartd[3547]: Device: /dev/sda, 2
> Currently unreadable (pending) sectors
> Aug 22 23:49:27 linux-office smartd[3547]: Device: /dev/sda, 2 Offline
> uncorrectable sectors Aug 22 23:49:27 linux-office smartd[3547]: Device:
> /dev/sda, SMART Usage Attribute: 190 Temperature_Celsius changed from 55
> to 56 Aug 22 23:49:27 linux-office smartd[3547]: Device: /dev/sda, SMART
> Usage Attribute: 194 Temperature_Celsius changed from 45 to 44 Aug 22
> 23:49:27 linux-office smartd[3547]: Device: /dev/sdb, SMART Usage
> Attribute: 194 Temperature_Celsius changed from 125 to 127 Aug 23
> 00:00:01 linux-office /usr/sbin/cron[4912]: (root) CMD ( test -x
> /usr/lib/secchk/security-control.sh &&
> /usr/lib/secchk/security-control.sh daily &) Aug 23 00:19:26
> linux-office smartd[3547]: Device: /dev/sda, 2 Currently unreadable
> (pending) sectors Aug 23 00:19:26 linux-office smartd[3547]: Device:
> /dev/sda, 2 Offline uncorrectable sectors Aug 23 00:48:53 linux-office
> syslog-ng[2138]: STATS: dropped 0 Aug 23 00:49:26 linux-office
> smartd[3547]: Device: /dev/sda, 2 Currently unreadable (pending) sectors
> Aug 23 00:49:26 linux-office smartd[3547]: Device: /dev/sda, 2 Offline
> uncorrectable sectors Aug 23 01:19:26 linux-office smartd[3547]: Device:
> /dev/sda, 2 Currently unreadable (pending) sectors Aug 23 01:19:26
> linux-office smartd[3547]: Device: /dev/sda, 2 Offline uncorrectable
> sectors Aug 23 01:48:53 linux-office syslog-ng[2138]: STATS: dropped 0
> Aug 23 01:49:26 linux-office smartd[3547]: Device: /dev/sda, 2 Currently
> unreadable (pending) sectors Aug 23 01:49:26 linux-office smartd[3547]:
> Device: /dev/sda, 2 Offline uncorrectable sectors
> --------------------
>
> I booted up in Mint light to run a e2fsck on the drive this came back
> clean when run but when opening the drive shows unreadable sectors.
> My question can i run the e2fsck on bootup?
>
> This may also be relivant the name of the drive a square (see image as
> I cant create name.)
> 'http://www.kungfu.dyndns.org/drivename.jpg
> ’ (http://www.kungfu.dyndns.org/drivename.jpg)
> Cheers
>
> Dave
>
>
I had a drive with bad blocks last week. It was a Maxtor 320GB. Ran smartctl
short version found no errors. Then I ran the long version and it did not
find anything. I went to the Seagate site (they own Maxtor) and found a
command line diagnostic for Linux (their support personal did not no about
it). It ran the short test (generic test) with no errors but the long test
spotted the errors after 2 minutes of running. Seagate is replacing the
drive for free since its under warranty.
This diagnostic only runs on Seagate drives so old Maxtor drive cannot be
tested with it. The Seagate drives start with model numbers STxxxxxx and
the Maxtors with a model number STM if they were made by Seagate.
The Diagnostic works on my openSUSE 11.0 installation and on a 10.3 I ran it
off of when the 11.0 drive failed.
>
> ok after running the
> Code:
> --------------------
> sudo smartctl -s onlong /dev/hda
> --------------------
> it didn’t appear to find any issues but I do get a different output on
> the messageslog.
I thought I had written to perform the ‘long’ test:
smartctl -t long /dev/hda
Which is an offline test, takes quite some time, and can often fix any errors.
The ‘online’ tests are not as comprehensive.
Not sure what that command line you’ve given would perform actually…
mint@mint:~$ sudo smartctl -a /dev/hda
smartctl version 5.37 [i686-pc-linux-gnu] Copyright (C) 2002-6 Bruce Allen
Home page is http://smartmontools.sourceforge.net/
=== START OF INFORMATION SECTION ===
Device Model: MAXTOR STM3320820A
Serial Number: 5QF2TKNT
Firmware Version: 3.AAE
User Capacity: 320,072,933,376 bytes
Device is: Not in smartctl database [for details use: -P showall]
ATA Version is: 7
ATA Standard is: Exact ATA specification draft version not indicated
Local Time is: Tue Aug 26 20:01:32 2008 BST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
General SMART Values:
Offline data collection status: (0x82) Offline data collection activity
was completed without error.
Auto Offline Data Collection: Enabled.
Self-test execution status: ( 121) The previous self-test completed having
the read element of the test failed.
Total time to complete Offline
data collection: ( 430) seconds.
Offline data collection
capabilities: (0x5b) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
Offline surface scan supported.
Self-test supported.
No Conveyance Self-test supported.
Selective Self-test supported.
SMART capabilities: (0x0003) Saves SMART data before entering
power-saving mode.
Supports SMART auto save timer.
Error logging capability: (0x01) Error logging supported.
General Purpose Logging supported.
Short self-test routine
recommended polling time: ( 1) minutes.
Extended self-test routine
recommended polling time: ( 115) minutes.
SMART Attributes Data Structure revision number: 10
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x000f 111 090 006 Pre-fail Always - 200698658
3 Spin_Up_Time 0x0003 096 096 000 Pre-fail Always - 0
4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 68
5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 0
7 Seek_Error_Rate 0x000f 082 062 030 Pre-fail Always - 168465087
9 Power_On_Hours 0x0032 093 093 000 Old_age Always - 6888
10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0
12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 76
187 Unknown_Attribute 0x0032 100 100 000 Old_age Always - 0
189 Unknown_Attribute 0x003a 100 100 000 Old_age Always - 0
190 Temperature_Celsius 0x0022 054 049 045 Old_age Always - 824967214
194 Temperature_Celsius 0x0022 046 051 000 Old_age Always - 46 (Lifetime Min/Max 0/13)
195 Hardware_ECC_Recovered 0x001a 059 049 000 Old_age Always - 222465314
197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 2
198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 2
199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0
200 Multi_Zone_Error_Rate 0x0000 100 253 000 Old_age Offline - 0
202 TA_Increase_Count 0x0032 100 253 000 Old_age Always - 0
SMART Error Log Version: 1
No Errors Logged
SMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
# 1 Extended offline Completed: read failure 90% 6886 8901493
# 2 Extended offline Completed: read failure 90% 6858 8901492
SMART Selective self-test log data structure revision number 1
SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS
1 0 0 Not_testing
2 0 0 Not_testing
3 0 0 Not_testing
4 0 0 Not_testing
5 0 0 Not_testing
Selective self-test flags (0x0):
After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.
I dont really understand any of that output but from the Seek_Error_Rate it doesnt look good plus the 2 sectors still show as pending… in mint will have to see what happens when the machine is rebooted into suse
The drive passed away today due to a total system freeze up again… wouldnt boot up at all I am unable to format the drive as it is unresponsive I have checked the warrenty and its covered till 2010 so sending it back.
Many thanks for the help on smartd I am adding the info from the logs to maxtor.
>
> This is the result from the smartctl scan
>
>
> Code:
> --------------------
> mint@mint:~$ sudo smartctl -a /dev/hda
> smartctl version 5.37 [i686-pc-linux-gnu] Copyright (C) 2002-6 Bruce
> Allen Home page is http://smartmontools.sourceforge.net/
>
> === START OF INFORMATION SECTION ===
> Device Model: MAXTOR STM3320820A
> Serial Number: 5QF2TKNT
> Firmware Version: 3.AAE
> User Capacity: 320,072,933,376 bytes
> Device is: Not in smartctl database [for details use: -P showall]
> ATA Version is: 7
> ATA Standard is: Exact ATA specification draft version not indicated
> Local Time is: Tue Aug 26 20:01:32 2008 BST
> SMART support is: Available - device has SMART capability.
> SMART support is: Enabled
>
> === START OF READ SMART DATA SECTION ===
> SMART overall-health self-assessment test result: PASSED
>
> General SMART Values:
> Offline data collection status: (0x82) Offline data collection activity
> was completed without error.
> Auto Offline Data Collection: Enabled.
> Self-test execution status: ( 121) The previous self-test completed
> having the read element of the test failed.
> Total time to complete Offline
> data collection: ( 430) seconds.
> Offline data collection
> capabilities: (0x5b) SMART execute Offline immediate.
> Auto Offline data collection on/off support.
> Suspend Offline collection upon new
> command.
> Offline surface scan supported.
> Self-test supported.
> No Conveyance Self-test supported.
> Selective Self-test supported.
> SMART capabilities: (0x0003) Saves SMART data before entering
> power-saving mode.
> Supports SMART auto save timer.
> Error logging capability: (0x01) Error logging supported.
> General Purpose Logging supported.
> Short self-test routine
> recommended polling time: ( 1) minutes.
> Extended self-test routine
> recommended polling time: ( 115) minutes.
>
> SMART Attributes Data Structure revision number: 10
> Vendor Specific SMART Attributes with Thresholds:
> ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE
> UPDATED WHEN_FAILED RAW_VALUE
> 1 Raw_Read_Error_Rate 0x000f 111 090 006 Pre-fail Always
> - 200698658
> 3 Spin_Up_Time 0x0003 096 096 000 Pre-fail Always
> - 0
> 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always
> - 68
> 5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always
> - 0
> 7 Seek_Error_Rate 0x000f 082 062 030 Pre-fail Always
> - 168465087
> 9 Power_On_Hours 0x0032 093 093 000 Old_age Always
> - 6888
> 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always
> - 0
> 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always
> - 76
> 187 Unknown_Attribute 0x0032 100 100 000 Old_age Always
> - 0
> 189 Unknown_Attribute 0x003a 100 100 000 Old_age Always
> - 0
> 190 Temperature_Celsius 0x0022 054 049 045 Old_age Always
> - 824967214
> 194 Temperature_Celsius 0x0022 046 051 000 Old_age Always
> - 46 (Lifetime Min/Max 0/13)
> 195 Hardware_ECC_Recovered 0x001a 059 049 000 Old_age Always
> - 222465314
> 197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always
> - 2
> 198 Offline_Uncorrectable 0x0010 100 100 000 Old_age
> Offline - 2
> 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always
> - 0
> 200 Multi_Zone_Error_Rate 0x0000 100 253 000 Old_age
> Offline - 0
> 202 TA_Increase_Count 0x0032 100 253 000 Old_age Always
> - 0
>
> SMART Error Log Version: 1
> No Errors Logged
>
> SMART Self-test log structure revision number 1
> Num Test_Description Status Remaining
> LifeTime(hours) LBA_of_first_error
> # 1 Extended offline Completed: read failure 90% 6886
> # 8901493
> # 2 Extended offline Completed: read failure 90% 6858
> # 8901492
>
> SMART Selective self-test log data structure revision number 1
> SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS
> 1 0 0 Not_testing
> 2 0 0 Not_testing
> 3 0 0 Not_testing
> 4 0 0 Not_testing
> 5 0 0 Not_testing
> Selective self-test flags (0x0):
> After scanning selected spans, do NOT read-scan remainder of disk.
> If Selective self-test is pending on power-up, resume after 0 minute
> delay.
>
> --------------------
>
>
> I dont really understand any of that output but from the
> Seek_Error_Rate it doesnt look good plus the 2 sectors still show as
> pending… in mint will have to see what happens when the machine is
> rebooted into suse
>
> Dave
>
>
Interesting, the drive I mentioned in my early post was also a Maxtor
STM3320620A. (320GB). I had another one fail Wednesday morning, same model,
etc. Both were purchased last Aug (07). Was yours purchased in that time
frame. I Had the same systoms your showing. I wonder if they had a bad
production run? The diagnostic I mentioned will run on these STM model
drive since they are actually Seagate Barracuda drives.
Yea end of last year I bought the drive had been running fine up until about 2 weeks 3 weeks ago… I ran the software from the website and it did fix the errors. But to be honest I dont really know if i trust the drive the warrenty is till something like 10/08/2010 so it may well be from the same batch.
>
> Hi Russ,
>
> Yea end of last year I bought the drive had been running fine up until
> about 2 weeks 3 weeks ago… I ran the software from the website and it
> did fix the errors. But to be honest I dont really know if i trust the
> drive the warrenty is till something like 10/08/2010 so it may well be
> from the same batch.
>
> Dave…
>
> Im all sorted now though
>
>
I had another corrupt partition on a totally different Maxtor drive this
morning. I wonder if it is openSUSE 11.0 or my motherboard. I bought mine
in Aug 2007 and warranty runs out in Aug 2010. Seagate all ready replaced,
it, received it on Tuesday.
