Re[2]: How severe is IDNF errors in SMART log?
Hello Norberto, Tuesday, April 4, 2006, 5:25:49 PM, you wrote: >> OR you need full backup and monitoring SMART two weeks every day. >> IDNF is a hard-bad what you can remap with Hitachi tool. >> http://www.hitachigst.com/hdd/support/downloads/dft32_v406_b00.iso NM> Thanks for the info :) IBM (AU) has issued an DOA on this laptop, so NM> they agree on your/mine assesment (once I read them the SMART info over NM> the phone they must have figured out it was cheaper to get a DOA than NM> keep paying someone to listen to all that ;) ) NM> Wednesday night, it started doing this little NM> tsttttsttt..tstt... like it was trying to re-spin or something NM> like this. HDD found bads and trying read/remap automatically. -- Best regards, Playnetmailto:[EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: How severe is IDNF errors in SMART log?
On Tue, 4 Apr 2006 15:47:35 +0400 Playnet <[EMAIL PROTECTED]> wrote: > Hello Norberto, > > Monday, April 3, 2006, 7:11:24 PM, you wrote: > > NM> I have a laptop with a 100GB Hitachi SATA drive. the SMART log > NM> shows the errors below (via 'sudo smartctl -a /dev/ad0' ). How > NM> badly damaged is the disk? > Do not remap disk, if you can change this disk. Try replace by > warranty. > If not, you need low-level format (with Hitachi tool) and check cables > and controller. wasn't the controller, as it the spin-up issues were happening on a USB dongle. same for cables (well, it's a laptop, so not sure how i'd change them anyway ) > OR you need full backup and monitoring SMART two weeks every day. > IDNF is a hard-bad what you can remap with Hitachi tool. > http://www.hitachigst.com/hdd/support/downloads/dft32_v406_b00.iso > Thanks for the info :) IBM (AU) has issued an DOA on this laptop, so they agree on your/mine assesment (once I read them the SMART info over the phone they must have figured out it was cheaper to get a DOA than keep paying someone to listen to all that ;) ) thx :) B ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: How severe is IDNF errors in SMART log?
Hello Norberto, Monday, April 3, 2006, 7:11:24 PM, you wrote: NM> I have a laptop with a 100GB Hitachi SATA drive. the SMART log shows NM> the errors below (via 'sudo smartctl -a /dev/ad0' ). How badly damaged NM> is the disk? Do not remap disk, if you can change this disk. Try replace by warranty. If not, you need low-level format (with Hitachi tool) and check cables and controller. OR you need full backup and monitoring SMART two weeks every day. IDNF is a hard-bad what you can remap with Hitachi tool. http://www.hitachigst.com/hdd/support/downloads/dft32_v406_b00.iso -- Best regards, Playnetmailto:[EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
How severe is IDNF errors in SMART log?
hi all, I have a laptop with a 100GB Hitachi SATA drive. the SMART log shows the errors below (via 'sudo smartctl -a /dev/ad0' ). How badly damaged is the disk? [...] Error 65535 occurred at disk power-on lifetime: 214 hours (8 days + 22 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 -- -- -- -- -- -- -- 10 51 08 50 11 00 e0 Error: IDNF 8 sectors at LBA = 0x1150 = 4432 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- 35 03 08 50 11 00 e0 00 2d+21:25:42.300 WRITE DMA EXT 35 03 08 48 11 00 e0 00 2d+21:25:42.200 WRITE DMA EXT 35 03 08 40 11 00 e0 00 2d+21:25:42.100 WRITE DMA EXT 35 03 08 38 11 00 e0 00 2d+21:25:42.100 WRITE DMA EXT 35 03 08 30 11 00 e0 00 2d+21:25:42.000 WRITE DMA EXT Error 65534 occurred at disk power-on lifetime: 214 hours (8 days + 22 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 -- -- -- -- -- -- -- 10 51 08 48 11 00 e0 Error: IDNF 8 sectors at LBA = 0x1148 = 4424 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- 35 03 08 48 11 00 e0 00 2d+21:25:42.200 WRITE DMA EXT 35 03 08 40 11 00 e0 00 2d+21:25:42.100 WRITE DMA EXT 35 03 08 38 11 00 e0 00 2d+21:25:42.100 WRITE DMA EXT 35 03 08 30 11 00 e0 00 2d+21:25:42.000 WRITE DMA EXT 35 03 08 28 11 00 e0 00 2d+21:25:42.000 WRITE DMA EXT [] (about 6 times, different LBA ranges, always 8 sectors, always WRITE DMA EXT) thanks! Beto ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
