Hi Benjamin, hi All
Benjamin, firstly Thanks for your effort ..
OK, and the question I was asking is answered: I took a Fedora 9 CD
for ppc, booted the affected machine, and found, Fedora has the tools
one needs for a disk recovery. smartctrl is there, plus dumpe2fs, and
even "less" (which I was badly missing, on the Debian installer, IIRC)
etc. etc. ... Looks nice ...
[note: the German keyboard on Fedora was missing the bar sign ("|")
.. so I chose an "US English" keyboard layout, that had some sign
similar to that .. ]
On Thu, Oct 02, 2008 at 12:49:36AM +0200, Benjamin Cama wrote:
> Le mercredi 01 octobre 2008 à 22:29 +0200, Wolfgang Pfeiffer a écrit :
> > Excerpt from the Debian install syslog, cut:
> >
> > kernel: hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
> > kernel: hda: dma_intr: error=0x40 { UncorrectableError }, LBAsect=76724680,
> > high=4, low=9615816, sector=76724680
> > kernel: ide: failed opcode was: unknown
> > kernel: end_request: I/O error, dev hda, sector 76724680
> > kernel: Buffer I/O error on device hda7, logical block 1
> > kernel: hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
> > kernel: hda: dma_intr: error=0x40 { UncorrectableError }, LBAsect=76724676,
> > high=4, low=9615812, sector=76724676
> > kernel: ide: failed opcode was: unknown
> > kernel: end_request: I/O error, dev hda, sector 76724676
> > kernel: Buffer I/O error on device hda7, logical block 0
> > kernel: hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
> > kernel: hda: dma_intr: error=0x40 { UncorrectableError }, LBAsect=76724680,
> > high=4, low=9615816, sector=76724680
> > kernel: ide: failed opcode was: unknown
> > kernel: end_request: I/O error, dev hda, sector 76724680
> >
> > ... and the errors on sectors 76724680 and 76724680 are reported again
> > and again ... and only these 2 sectors, IINM ..
>
> These are quite severe hardware errors,
Could this also be a simple file system damage?
I was hoping it was just something like that, because this hopefully
could be "fixed" with a reinstall, and with a previous low-level
formatting like
dd if=/dev/urandom of=/dev/hda (not being sure whether the syntax is
correct .. )
Oh, and the Fedora smartctrl found (surprise, surprise .. :) a failure on
LBA 76724676 and 76724678, too (please see the old log above) ...
I attach the log made on the broken machine via
smartctrl -a /dev/hda
> I would advise you to do some complete copy of your harddrive right
> now before it gets worse. Just dd your hda, or use some other
> recovery software (like http://www.garloff.de/kurt/linux/ddrescue/
> ). If only hda7 is affected, I think this is only the beginning,
> and if you have backups it would be better.
I've done some backup already for /home on hda6 ... and /etc on
hda7 (the failing partition) isn't that important ...
>
> > Failing hda7 is the root partition. hda6, not being listed here, with
> > quite a few errors, was recoverable ... tho it's not quite clear
> > whether this hda6 errors started while I was playing with the Debian
> > Installer (Etch, IIRC) ...
>
> This may not be related.
> Maybe you could try to run smartctl -a from here,
As I said: smartctrl is missing on the Debian installer, or at least I
didn't find it ...
> to get some (hopefully) "usefull" stats from it.
>
> > IIRC:
> > the installer later on didn't even see hda7, whereas mac-fdisk did
> > (took quite some time for it to finish the detection ...).
>
> What do you mean by "see hda7" ?
to "see" in the sense of to "detect" ...
mac-fdisk detected the damaged partition in the Debian installer, IIRC
..
>
> > "Apple Hardware Test" on the OS X install CD seems to hang/crash, or
> > simply does not load even after 15 Minutes or so ...
>
> Well, being on the same IDE controller might not help. Can you remove
> the HDD from your laptop for further analysis ?
No, not that easily .. It's a Powerbook5,8: if I manage to remove the
disk from it (there must be instructions somewhere on www) I'll
reinstall a new one. No time to waste, because my old tibook, where
I'm typing this email, is making strange noises already. Looks like
I'm in need of quick decisions, besides working hardware ... :)
>
> BTW, how old is your powerbook ?
a little more than 2.5 years. Still with the same disk installed that was
shipped with the machine ..
Regards, guys. And Thanks
Wolfgang
--
heelsbroke.blogspot.com
smartctl version 5.38 [powerpc-redhat-linux-gnu] Copyright (C) 2002-8 Bruce
Allen
Home page is http://smartmontools.sourceforge.net/
=== START OF INFORMATION SECTION ===
Model Family: Seagate Momentus 5400.2 series
Device Model: ST9808211A
Serial Number: 3LF2V7HB
Firmware Version: 3.07
User Capacity: 80,026,361,856 bytes
Device is: In smartctl database [for details use: -P show]
ATA Version is: 6
ATA Standard is: ATA/ATAPI-6 T13 1410D revision 2
Local Time is: Thu Oct 2 18:07:41 2008 UTC
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: ( 60) 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.
No General Purpose Logging support.
Short self-test routine
recommended polling time: ( 1) minutes.
Extended self-test routine
recommended polling time: ( 84) 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 055 052 034 Pre-fail Always
- 58741978
3 Spin_Up_Time 0x0003 095 094 000 Pre-fail Always
- 0
4 Start_Stop_Count 0x0032 098 098 020 Old_age Always
- 2170
5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always
- 14
7 Seek_Error_Rate 0x000f 080 060 030 Pre-fail Always
- 109426446
9 Power_On_Hours 0x0032 088 088 000 Old_age Always
- 10712
10 Spin_Retry_Count 0x0013 100 100 034 Pre-fail Always
- 0
12 Power_Cycle_Count 0x0032 099 099 020 Old_age Always
- 1427
192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always
- 1429
193 Load_Cycle_Count 0x0032 001 001 000 Old_age Always
- 2898441
194 Temperature_Celsius 0x0022 030 048 000 Old_age Always
- 30 (0 14 0 0)
195 Hardware_ECC_Recovered 0x001a 055 052 000 Old_age Always
- 58741978
197 Current_Pending_Sector 0x0012 095 095 000 Old_age Always
- 98
198 Offline_Uncorrectable 0x0010 095 095 000 Old_age Offline
- 98
199 UDMA_CRC_Error_Count 0x003e 200 199 000 Old_age Always
- 29
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
ATA Error Count: 4564 (device log contains only the most recent five errors)
CR = Command Register [HEX]
FR = Features Register [HEX]
SC = Sector Count Register [HEX]
SN = Sector Number Register [HEX]
CL = Cylinder Low Register [HEX]
CH = Cylinder High Register [HEX]
DH = Device/Head Register [HEX]
DC = Device Command Register [HEX]
ER = Error register [HEX]
ST = Status register [HEX]
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.
Error 4564 occurred at disk power-on lifetime: 10709 hours (446 days + 5 hours)
When the command that caused the error occurred, the device was active or
idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 01 c7 b9 92 e0 Error: UNC 1 sectors at LBA = 0x0092b9c7 = 9615815
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
25 00 01 c7 b9 92 e0 00 00:08:37.648 READ DMA EXT
25 00 02 c6 b9 92 e0 00 00:08:44.079 READ DMA EXT
ea 00 00 00 00 00 e0 00 00:08:37.659 FLUSH CACHE EXIT
25 00 08 80 06 00 e0 00 00:08:37.655 READ DMA EXT
25 00 08 80 06 00 e0 00 00:08:37.654 READ DMA EXT
Error 4563 occurred at disk power-on lifetime: 10709 hours (446 days + 5 hours)
When the command that caused the error occurred, the device was active or
idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 02 c6 b9 92 e0 Error: UNC 2 sectors at LBA = 0x0092b9c6 = 9615814
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
25 00 02 c6 b9 92 e0 00 00:08:37.648 READ DMA EXT
ea 00 00 00 00 00 e0 00 00:08:37.648 FLUSH CACHE EXIT
25 00 08 80 06 00 e0 00 00:08:37.659 READ DMA EXT
25 00 08 80 06 00 e0 00 00:08:37.655 READ DMA EXT
ea 00 00 00 00 00 e0 00 00:08:37.654 FLUSH CACHE EXIT
Error 4562 occurred at disk power-on lifetime: 10709 hours (446 days + 5 hours)
When the command that caused the error occurred, the device was active or
idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 01 c4 b9 92 e0 Error: UNC 1 sectors at LBA = 0x0092b9c4 = 9615812
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
25 00 01 c4 b9 92 e0 00 00:08:30.885 READ DMA EXT
25 00 01 0f 00 00 e0 00 00:08:30.884 READ DMA EXT
25 00 01 0e 00 00 e0 00 00:08:30.884 READ DMA EXT
25 00 01 0d 00 00 e0 00 00:08:30.883 READ DMA EXT
25 00 01 0c 00 00 e0 00 00:08:30.883 READ DMA EXT
Error 4561 occurred at disk power-on lifetime: 10709 hours (446 days + 5 hours)
When the command that caused the error occurred, the device was active or
idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 01 c4 b9 92 e0 Error: UNC 1 sectors at LBA = 0x0092b9c4 = 9615812
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
25 00 01 c4 b9 92 e0 00 00:08:24.420 READ DMA EXT
25 00 01 0f 00 00 e0 00 00:08:24.420 READ DMA EXT
25 00 01 0e 00 00 e0 00 00:08:24.420 READ DMA EXT
25 00 01 0d 00 00 e0 00 00:08:24.419 READ DMA EXT
25 00 01 0c 00 00 e0 00 00:08:24.419 READ DMA EXT
Error 4560 occurred at disk power-on lifetime: 10709 hours (446 days + 5 hours)
When the command that caused the error occurred, the device was active or
idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 01 c4 b9 92 e0 Error: UNC 1 sectors at LBA = 0x0092b9c4 = 9615812
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
25 00 01 c4 b9 92 e0 00 00:08:17.966 READ DMA EXT
25 00 01 0f 00 00 e0 00 00:08:17.966 READ DMA EXT
25 00 01 0e 00 00 e0 00 00:08:17.966 READ DMA EXT
25 00 01 0d 00 00 e0 00 00:08:17.966 READ DMA EXT
25 00 01 0c 00 00 e0 00 00:08:17.966 READ DMA EXT
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% 10709
76724676
# 2 Extended offline Completed: read failure 90% 10708
76724678
# 3 Extended offline Completed: read failure 90% 10707
76724676
# 4 Short offline Completed without error 00% 6076 -
# 5 Short offline Completed without error 00% 6076 -
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.
