Maxtor HDD can't mount in Ubuntu

[Nostrada]

Howdy,

I am totally stressed out. My UBuntu machine started freezing when copying stuff off my ext3 filesystem, and now the offending HDD seems to have gone for good?

I have attempted to use the smartctl tool but it doesn't make much sense to me.

This is the drive:
Model Family: Maxtor DiamondMax Plus 9 family
Device Model: Maxtor 6Y200P0
Firmware Version: YAR41BW0
User Capacity: 203,928,109,056 bytes

Here is dmesg:
[4299677.285000] hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
[4299677.286000] hdb: task_in_intr: error=0x01 { AddrMarkNotFound }, LBAsect=0, high=0, low=0, sector=0
[4299677.286000] ide: failed opcode was: unknown
[4299678.590000] hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
[4299678.590000] hdb: task_in_intr: error=0x40 { UncorrectableError }, LBAsect=0, high=0, low=0, sector=0
[4299678.590000] ide: failed opcode was: unknown
[4299678.590000] end_request: I/O error, dev hdb, sector 0
[4299678.590000] Buffer I/O error on device hdb, logical block 0

smartctl:
SMART Error Log Version: 1
ATA Error Count: 350 (device log contains only the most recent five errors)
...
Error 347 occurred at disk power-on lifetime: 5980 hours (249 days + 4 hours)
When the command that caused the error occurred, the device was in an unknown state.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
01 59 08 00 00 00 f0 Error: AMNF at LBA = 0x00000000 = 0

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
24 00 08 00 00 00 f0 08 00:12:27.392 READ SECTOR(S) EXT
24 00 08 00 00 00 f0 08 00:12:26.528 READ SECTOR(S) EXT
24 00 08 00 00 00 f0 08 00:12:24.560 READ SECTOR(S) EXT
10 00 ff 00 00 00 f0 08 00:12:24.544 RECALIBRATE [OBS-4]
24 00 08 00 00 00 f0 08 00:12:22.624 READ SECTOR(S) EXT

...
SMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
# 1 Short offline Completed: read failure 60% 5955 -
# 2 Short captive Completed: read failure 60% 5955 -

Patient dead for good?

 

[SparkyJJO]

I'm guessing if SMART is reporting failure then odds are the drive just decided to give up the ghost