Re: Hard Drive Issues
On Tue, Nov 07, 2006 at 04:49:08PM -0500, Richard McIntyre wrote: Tom Judge wrote: Richard McIntyre wrote: I'm having a similar problem, Oct 13 03:01:31 tco1 kernel: ad2: FAILURE - READ_DMA status=51READY,DSC,ERROR error=40UNCORRECTABLE LBA=181778119 Oct 13 07:11:15 tco1 kernel: ad2: FAILURE - READ_DMA status=51READY,DSC,ERROR error=40UNCORRECTABLE LBA=181778119 I'm assuming that particular sector on the drive is dying, I have backed everything up on the drive, can anyone give me more information, should the drive simply be replaced or is it possible that this is simply a TOC error and could be corrected by newfs to the drive? I'm guessing it will need to be replaced, output of smartctl is below Thanks ~Richard Error 7742 occurred at disk power-on lifetime: 16036 hours (668 days + 4 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 04 c7 b6 d5 ea Error: UNC 4 sectors at LBA = 0x0ad5b6c7 = 181778119 etc Looks like you disk is on its way out, from the look of the above errors, I would try dd'ing the disk onto a new disk the running an fsck to make sure everything is ok. I wouldnt hold out much hope for recovering the data on that sector though. Tom J All, I've put a new disk into the system, The current disk is 200 GB, the new disk is 250 GB. If I run the command: dd if=/dev/ad2 of=/dev/ad3 conv=noerror Will this copy the (changing the appropriate device names of course) the disk as a whole? Yes, but it is not the best way to do it. Will I lose the 50 GB difference? Yes you will. (NOTE I swapped a couple of lines of you message for clarity in responding) The drive is two partitions, one 100GB and the remainder on the other partition. The files contained are backups of my virtual hosted sites and the apache directories (including the apache/bin files). Any suggestions? I've read a good deal of forums online but they seem to be contradicting. 1/2 say I will loose the remainder of the drive space, 1/2 say that dd is not the best way to go. (there is roughly 35 GB of data actually on the device). I agree that dd is not the way to go. It doesn't do what you want it to do. It makes a sector for sector copy and you really want functionally identical filesystems and couldn't care less about the sector layout - only the file integrity. dd does nothing for file integrity and only gets the filesystems right by accident. Is there another way? (like the dump, tar, or just plain copy command?) You should fdisk, bsdlabel and newfs the new disk the way you want it. If it is to be bootable, use -B switch on fdisk. If it is to be the only slice on the disk also use -I fdisk -BI ad3 Then do two bsdlabels - one to mark it and put in the slice boot code the other to create the partitions. bsdlabel -w -B ad3s1 bsdlabel -e ad3s1 That second bsdlabel will cause an edit session to open and you edit the partitions the way you want - maybe like the old one. Lets say you make the following: a: for root b: for swap d: for /tmp e: for /usr f: for /home look at your present disk with bsdlabel to see what it already has set up.Just running bsdlabel on a slice without any other parameters will cause it to print out its information, so try: bsdlabel ad2s1 Ignore all the stuff above where it displays the partition information. Use a star (*) for the size and offset of the last partition and it will just make it all the rest of the slice (drive if you made it one slice). Then use newfs(8) to create a filesystem on each partition you created with bsdlabel, except for swap. Swap doesn't get newfs-ed. Taking the defaults is probably good enough. Create new mount points for the new disk as needed, for example: mkdir /newroot mkdir /newusr mkdir /newhome Mount the new filesystems, given the above, do: mount /ad3s1a /newroot mount /ad3s1e /newusr mount /ad3s1f /newhome New copy the old file systems using dump/restore cd /newroot dump 0af - / | restore -rf - cd /newusr dump 0af - /usr | restore -rf - cd /newhome dump 0af - /home | restore -rf - Generally you wouldn't bother copying /tmp, but you could. This procedure will get you the copies you want which using dd will not. It will also correctly use up the whole drive which using dd will not. Your drive, no doubt, has a different layout than my examples above, but the process will be the same, just with appropriate name changes. If dump is unable to read some part of a file system due to a bad sector on the disk, then dd will also not be able to do it properly while reading the whole disk either. You will then have to play around trying to remove the file that is bad so dump will not attempt to read it, or, much more difficult, try to follow the
Re: Hard Drive Issues
Tom Judge wrote: Richard McIntyre wrote: I'm having a similar problem, Oct 13 03:01:31 tco1 kernel: ad2: FAILURE - READ_DMA status=51READY,DSC,ERROR error=40UNCORRECTABLE LBA=181778119 Oct 13 07:11:15 tco1 kernel: ad2: FAILURE - READ_DMA status=51READY,DSC,ERROR error=40UNCORRECTABLE LBA=181778119 I'm assuming that particular sector on the drive is dying, I have backed everything up on the drive, can anyone give me more information, should the drive simply be replaced or is it possible that this is simply a TOC error and could be corrected by newfs to the drive? I'm guessing it will need to be replaced, output of smartctl is below Thanks ~Richard Error 7742 occurred at disk power-on lifetime: 16036 hours (668 days + 4 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 04 c7 b6 d5 ea Error: UNC 4 sectors at LBA = 0x0ad5b6c7 = 181778119 etc Looks like you disk is on its way out, from the look of the above errors, I would try dd'ing the disk onto a new disk the running an fsck to make sure everything is ok. I wouldnt hold out much hope for recovering the data on that sector though. Tom J All, I've put a new disk into the system, The current disk is 200 GB, the new disk is 250 GB. If I run the command: dd if=/dev/ad2 of=/dev/ad3 conv=noerror Will this copy the (changing the appropriate device names of course) the disk as a whole? Will I lose the 50 GB difference? Is there another way? (like the dump, tar, or just plain copy command?) The drive is two partitions, one 100GB and the remainder on the other partition. The files contained are backups of my virtual hosted sites and the apache directories (including the apache/bin files). Any suggestions? I've read a good deal of forums online but they seem to be contradicting. 1/2 say I will loose the remainder of the drive space, 1/2 say that dd is not the best way to go. (there is roughly 35 GB of data actually on the device). FreeBSD tco1.thecompanyonline.com 5.3-RELEASE FreeBSD 5.3-RELEASE #0: Mon May 2 22:32:50 EDT 2005 [EMAIL PROTECTED]:/usr/src/sys/i386/compile/TCO1.2005.05.02.001 i386 Thank you for the help! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Hard Drive Issues
On Nov 7, 2006, at 1:49 PM, Richard McIntyre wrote: Tom Judge wrote: Richard McIntyre wrote: I'm having a similar problem, Oct 13 03:01:31 tco1 kernel: ad2: FAILURE - READ_DMA status=51READY,DSC,ERROR error=40UNCORRECTABLE LBA=181778119 Oct 13 07:11:15 tco1 kernel: ad2: FAILURE - READ_DMA status=51READY,DSC,ERROR error=40UNCORRECTABLE LBA=181778119 I'm assuming that particular sector on the drive is dying, I have backed everything up on the drive, can anyone give me more information, should the drive simply be replaced or is it possible that this is simply a TOC error and could be corrected by newfs to the drive? I'm guessing it will need to be replaced, output of smartctl is below Thanks ~Richard Error 7742 occurred at disk power-on lifetime: 16036 hours (668 days + 4 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 04 c7 b6 d5 ea Error: UNC 4 sectors at LBA = 0x0ad5b6c7 = 181778119 etc Looks like you disk is on its way out, from the look of the above errors, I would try dd'ing the disk onto a new disk the running an fsck to make sure everything is ok. I wouldnt hold out much hope for recovering the data on that sector though. Tom J All, I've put a new disk into the system, The current disk is 200 GB, the new disk is 250 GB. If I run the command: dd if=/dev/ad2 of=/dev/ad3 conv=noerror Will this copy the (changing the appropriate device names of course) the disk as a whole? Will I lose the 50 GB difference? Is there another way? (like the dump, tar, or just plain copy command?) The drive is two partitions, one 100GB and the remainder on the other partition. The files contained are backups of my virtual hosted sites and the apache directories (including the apache/bin files). Any suggestions? I've read a good deal of forums online but they seem to be contradicting. 1/2 say I will loose the remainder of the drive space, 1/2 say that dd is not the best way to go. (there is roughly 35 GB of data actually on the device). FreeBSD tco1.thecompanyonline.com 5.3-RELEASE FreeBSD 5.3-RELEASE #0: Mon May 2 22:32:50 EDT 2005 [EMAIL PROTECTED]:/ usr/src/sys/i386/compile/TCO1.2005.05.02.001 i386 Thank you for the help! Too bad you can't just mount the disk image and grab files on demand :(... You should be able to expand the disk though if I remember correctly using the tunefs command... don't have my terminal right in front of me though to confirm whether or not this is the case though.. -Garrett ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Hard Drive Issues
On Tue, Nov 07, 2006 at 04:49:08PM -0500, Richard McIntyre wrote: Tom Judge wrote: I've put a new disk into the system, The current disk is 200 GB, the new disk is 250 GB. If I run the command: dd if=/dev/ad2 of=/dev/ad3 conv=noerror Will this copy the (changing the appropriate device names of course) the disk as a whole? Will I lose the 50 GB difference? Yes. Yes. Is there another way? (like the dump, tar, or just plain copy command?) Yes. I would manually use /usr/bin/sysinstall to prepare the new drive with the desired partitions, sized appropriately. Now is the time to rethink your previous partitioning. Maybe /home should be a separate partition? How about /var/mail? Webserver space? Etc. Manually mount the new drive somewhere, typically /mnt is used. So your new drive's usr filesystem will be at /mnt/usr, and root at /mnt, and etc at /mnt/etc, and home at /mnt/home (if you use a /home partition). Really should be running single user at this point. Use dump to read the old drive one partition at a time piped thru stdout into restore. Double check the following as I'm typing off the top of my head: # dump -0af - /| ( cd /mnt; restore -rf - ) # dump -0af - /etc | ( cd /mnt/etc; restore -rf - ) # dump -0af - /var | ( cd /mnt/var; restore -rf - ) If you are splitting /usr/home out into /home make this symbolic link so that restore puts /usr/home in /mnt/home, otherwise skip this command. #ln -s ../home /mnt/usr # dump -0af - /usr | ( cd /mnt/usr; restore -rf - ) You should get the gist of things by now. Repeat for any other filesystem. Edit the contents of /mnt/etc/fstab before rebooting. -- David Kelly N4HHE, [EMAIL PROTECTED] Whom computers would destroy, they must first drive mad. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Hard Drive Issues
Thinking about this a bit more. Don't mount all your new partitions before starting dump. Only mount the new root at /mnt. I think you *can* mount them all in advance but there are two sets of mode bits which apply to a mounted filesystem, those of the filesystem, and those of its mount point. I think if you let restore create the mount points you will most accurately clone the permissions. /tmp is particularly different. On Nov 7, 2006, at 5:44 PM, David Kelly wrote: Use dump to read the old drive one partition at a time piped thru stdout into restore. Double check the following as I'm typing off the top of my head: # dump -0af - /| ( cd /mnt; restore -rf - ) In copying / you should now have the mount points for other filesystems. # mount /dev/newdisk_etc /mnt/etc # dump -0af - /etc | ( cd /mnt/etc; restore -rf - ) # mount /dev/newdisk_var /mnt/var # dump -0af - /var | ( cd /mnt/var; restore -rf - ) ... -- David Kelly N4HHE, [EMAIL PROTECTED] Whom computers would destroy, they must first drive mad. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Hard Drive Issues
David Kelly wrote: On Thu, Oct 12, 2006 at 06:54:53PM +0100, Spiros Papadopoulos wrote: Since as you say everything is working, maybe it is a good idea to take a look and run the fsck command at least it may give you some more information, which you can post in order to get better answers That too, but first I'd start with sysutils/smartmontools and see what the drive and its built-in log says. I'm having a similar problem, Oct 13 03:01:31 tco1 kernel: ad2: FAILURE - READ_DMA status=51READY,DSC,ERROR error=40UNCORRECTABLE LBA=181778119 Oct 13 07:11:15 tco1 kernel: ad2: FAILURE - READ_DMA status=51READY,DSC,ERROR error=40UNCORRECTABLE LBA=181778119 I'm assuming that particular sector on the drive is dying, I have backed everything up on the drive, can anyone give me more information, should the drive simply be replaced or is it possible that this is simply a TOC error and could be corrected by newfs to the drive? I'm guessing it will need to be replaced, output of smartctl is below Thanks ~Richard uname -a FreeBSD 5.3-RELEASE FreeBSD 5.3-RELEASE #0: Mon May 2 22:32:50 EDT 2005 [EMAIL PROTECTED]:/usr/src/sys/i386/compile/TCO1.2005.05.02.001 i386 My output of smartmontools is: smartctl -a -s on /dev/ad2 smartctl version 5.36 [i386-portbld-freebsd5.3] Copyright (C) 2002-6 Bruce Allen Home page is http://smartmontools.sourceforge.net/ === START OF INFORMATION SECTION === Model Family: Seagate Barracuda 7200.7 and 7200.7 Plus family Device Model: ST3200822A Serial Number:5LJ0LW2T Firmware Version: 3.01 User Capacity:200,049,647,616 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:Fri Oct 13 14:56:23 2006 EDT SMART support is: Available - device has SMART capability. SMART support is: Disabled === START OF ENABLE/DISABLE COMMANDS SECTION === SMART 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: ( 0) The previous self-test routine completed without error or no self-test has ever been run. 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. No General Purpose Logging support. Short self-test routine recommended polling time:( 1) minutes. Extended self-test routine recommended polling time:( 111) 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 051 048 006Pre-fail Always - 22488920 3 Spin_Up_Time0x0003 097 097 000Pre-fail Always - 0 4 Start_Stop_Count0x0032 100 100 020Old_age Always - 21 5 Reallocated_Sector_Ct 0x0033 100 100 036Pre-fail Always - 1 7 Seek_Error_Rate 0x000f 084 060 030Pre-fail Always - 328020832 9 Power_On_Hours 0x0032 082 082 000Old_age Always - 16043 10 Spin_Retry_Count0x0013 100 100 097Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020Old_age Always - 22 194 Temperature_Celsius 0x0022 030 040 000Old_age Always - 30 195 Hardware_ECC_Recovered 0x001a 051 048 000Old_age Always - 22488920 197 Current_Pending_Sector 0x0012 100 100 000Old_age Always - 1 198 Offline_Uncorrectable 0x0010 100 100 000Old_age Offline - 1 199 UDMA_CRC_Error_Count
Re: Hard Drive Issues
On Oct 13, 2006, at 12:03 PM, Richard McIntyre wrote: I'm having a similar problem, Oct 13 03:01:31 tco1 kernel: ad2: FAILURE - READ_DMA status=51READY,DSC,ERROR error=40UNCORRECTABLE LBA=181778119 Oct 13 07:11:15 tco1 kernel: ad2: FAILURE - READ_DMA status=51READY,DSC,ERROR error=40UNCORRECTABLE LBA=181778119 I'm assuming that particular sector on the drive is dying, I have backed everything up on the drive, can anyone give me more information, should the drive simply be replaced or is it possible that this is simply a TOC error and could be corrected by newfs to the drive? I'm guessing it will need to be replaced, output of smartctl is below You can try doing a dd if=/dev/ad2 of=/dev/null bs=64k in order to read all of the sectors on the disk and get a better feel for how well it is doing. But it certainly appears that your drive has run into enough errors that it no longer has spare sectors available to replace the failing sectors-- you should replace it soon. -- -Chuck ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Hard Drive Issues
Richard McIntyre wrote: I'm having a similar problem, Oct 13 03:01:31 tco1 kernel: ad2: FAILURE - READ_DMA status=51READY,DSC,ERROR error=40UNCORRECTABLE LBA=181778119 Oct 13 07:11:15 tco1 kernel: ad2: FAILURE - READ_DMA status=51READY,DSC,ERROR error=40UNCORRECTABLE LBA=181778119 I'm assuming that particular sector on the drive is dying, I have backed everything up on the drive, can anyone give me more information, should the drive simply be replaced or is it possible that this is simply a TOC error and could be corrected by newfs to the drive? I'm guessing it will need to be replaced, output of smartctl is below Thanks ~Richard Error 7742 occurred at disk power-on lifetime: 16036 hours (668 days + 4 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 04 c7 b6 d5 ea Error: UNC 4 sectors at LBA = 0x0ad5b6c7 = 181778119 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- c8 00 04 c7 b6 d5 ea 00 15:22:37.737 READ DMA c8 00 04 9b b4 e1 ea 00 15:22:37.493 READ DMA c8 00 04 97 b4 e1 ea 00 15:22:37.251 READ DMA c8 00 04 a7 b4 e1 ea 00 15:22:37.002 READ DMA c8 00 04 a3 b4 e1 ea 00 15:22:36.761 READ DMA Error 7741 occurred at disk power-on lifetime: 16032 hours (668 days + 0 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 04 c7 b6 d5 ea Error: UNC 4 sectors at LBA = 0x0ad5b6c7 = 181778119 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- c8 00 04 c7 b6 d5 ea 00 11:08:40.154 READ DMA 35 00 20 df ff 2b 40 00 11:08:40.145 WRITE DMA EXT 35 00 20 1f d5 16 40 00 11:08:44.953 WRITE DMA EXT ca 00 20 3f c0 92 ef 00 11:08:40.258 WRITE DMA ca 00 20 df 85 81 ef 00 11:08:40.250 WRITE DMA Error 7740 occurred at disk power-on lifetime: 16012 hours (667 days + 4 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 04 c7 b6 d5 ea Error: UNC 4 sectors at LBA = 0x0ad5b6c7 = 181778119 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- c8 00 04 c7 b6 d5 ea 00 15:49:49.473 READ DMA c8 00 04 9b b4 e1 ea 00 15:49:49.220 READ DMA c8 00 04 97 b4 e1 ea 00 15:49:52.420 READ DMA c8 00 04 a7 b4 e1 ea 00 15:49:52.175 READ DMA c8 00 04 a3 b4 e1 ea 00 15:49:51.929 READ DMA Error 7739 occurred at disk power-on lifetime: 16008 hours (667 days + 0 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 04 c7 b6 d5 ea Error: UNC 4 sectors at LBA = 0x0ad5b6c7 = 181778119 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- c8 00 04 c7 b6 d5 ea 00 11:35:56.771 READ DMA 35 00 20 bf e7 39 40 00 11:35:56.765 WRITE DMA EXT 35 00 20 7f 6b 2e 40 00 11:35:56.749 WRITE DMA EXT 35 00 20 3f 0d c7 40 00 11:35:56.740 WRITE DMA EXT 35 00 20 1f 4f c1 40 00 11:35:56.732 WRITE DMA EXT Error 7738 occurred at disk power-on lifetime: 15989 hours (666 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 04 c7 b6 d5 ea Error: UNC 4 sectors at LBA = 0x0ad5b6c7 = 181778119 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- c8 00 04 c7 b6 d5 ea 00 16:16:27.719 READ DMA c8 00 04 9b b4 e1 ea 00 16:16:27.468 READ DMA c8 00 04 97 b4 e1 ea 00 16:16:30.682 READ DMA c8 00 04 a7 b4 e1 ea 00 16:16:30.440 READ DMA c8 00 04 a3 b4 e1 ea 00 16:16:30.174 READ DMA Looks like you disk is on its way out, from the look of the above errors, I would try dd'ing the disk onto a new disk the running an fsck to make sure everything is ok. I wouldnt hold out much hope for recovering the data on that sector though. Tom J ___
Re: Hard Drive Issues
On Fri, Oct 13, 2006 at 03:03:31PM -0400, Richard McIntyre wrote: David Kelly wrote: On Thu, Oct 12, 2006 at 06:54:53PM +0100, Spiros Papadopoulos wrote: Since as you say everything is working, maybe it is a good idea to take a look and run the fsck command at least it may give you some more information, which you can post in order to get better answers That too, but first I'd start with sysutils/smartmontools and see what the drive and its built-in log says. I'm having a similar problem, [...] I'm guessing it will need to be replaced, output of smartctl is below [...] SMART support is: Available - device has SMART capability. SMART support is: Disabled Download the Seagate Tools CD, boot it, and enable SMART. Let the drive repair itself. Problem is that the problem has gone on long enough that the data in that block is totally lost. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 04 c7 b6 d5 ea Error: UNC 4 sectors at LBA = 0x0ad5b6c7 = 181778119 What you need to do is figure out what file occupied that LBA and deal with its corruption. If part of the filesystem metadata then fsck will deal with it as best as can be. The Seagate tools will replace the bad block with a spare held in reserve. The spare will answer to the old's LBA. If SMART had been enabled in the first place the drive should have exchanged the block for a spare before the data was lost without bothering you. Doesn't always catch it in time. This sort of thing happens all the time. Thats why the tool is smart *mon*, its a monitor that you can watch inside the drive to see if its recovering from errors and on its last legs. Death is usually pronounced when the drive runs out of spare blocks for repair. Thats usually when a problem is first noticed. -- David Kelly N4HHE, [EMAIL PROTECTED] Whom computers would destroy, they must first drive mad. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Hard Drive Issues
On Fri, Oct 13, 2006 at 03:03:31PM -0400, Richard McIntyre wrote: David Kelly wrote: On Thu, Oct 12, 2006 at 06:54:53PM +0100, Spiros Papadopoulos wrote: Since as you say everything is working, maybe it is a good idea to take a look and run the fsck command at least it may give you some more information, which you can post in order to get better answers That too, but first I'd start with sysutils/smartmontools and see what the drive and its built-in log says. I'm having a similar problem, Oct 13 03:01:31 tco1 kernel: ad2: FAILURE - READ_DMA status=51READY,DSC,ERROR error=40UNCORRECTABLE LBA=181778119 Oct 13 07:11:15 tco1 kernel: ad2: FAILURE - READ_DMA status=51READY,DSC,ERROR error=40UNCORRECTABLE LBA=181778119 I'm assuming that particular sector on the drive is dying, I have backed everything up on the drive, can anyone give me more information, should the drive simply be replaced or is it possible that this is simply a TOC error and could be corrected by newfs to the drive? I'm guessing it will need to be replaced, output of smartctl is below [...] I ran into similar issues with what I believe was an identical Seagate drive. The customer service folks at Seagate weren't too interested in discussing the output from smartmontools and insisted the only supported method of monitoring drive health was using their own DOS utility (available on their website). So before replacing the drive, I decided to give it a go. The results were hardly informative as the the utility is designed on a PASS/FAIL model. It failed, of course, but the REPLACE THIS DRIVE IMMEDIATELY warning message helped confirm things for me. Soon thereafter I needed to set up a Windows box and didn't have a drive I was willing to spare, so I used the defective one which I still had lying around. Oddly enough, the setup went fine and still works to this day. Go figure. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Hard Drive Issues
On Thu, Oct 12, 2006 at 10:27:13AM -0400, Justin wrote: Greetings, I'm getting the following errors on the terminal: ad1: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=186691903 ad1: FAILURE - READ_DMA status=51READY,DCS,ERROR error=84ICRC,ABORTED LBA=186691903 g_vfs_done():ad1s1d[READ(offset=95586222080, length=49152)]error = 5 And similar, with the LBA number, offset number, and error=84 changes to error=10. The hard disk drives and data seem to be remaining intact and working. Can someone direct me as to what these errors mean, and if they are serious? Hmmm.I don't know all the disk codes and messages, but my practice is to be really nervous about disks and data and any time new error messages show up, just replace the disk. They are so much cheaper than the data that might get lost. Hopefully someone else can give you specific information, but that is my general perspective. jerry Regards, Justin P. Michel ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [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: Hard Drive Issues
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Justin wrote: Greetings, I'm getting the following errors on the terminal: ad1: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=186691903 ad1: FAILURE - READ_DMA status=51READY,DCS,ERROR error=84ICRC,ABORTED LBA=186691903 g_vfs_done():ad1s1d[READ(offset=95586222080, length=49152)]error = 5 And similar, with the LBA number, offset number, and error=84 changes to error=10. The hard disk drives and data seem to be remaining intact and working. Can someone direct me as to what these errors mean, and if they are serious? Regards, Justin P. Michel Based on your error message it appears that data is getting corrupted in transit on whatever channel you're using for your drives. Have you tried using the disk on another channel by chance, or tried another disk on the same channel? - -Garrett -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFLl456CkrZkzMC68RApN2AJ4/ltFmC3SJCCh1eER+Q+Ehh3yTUwCfU5xl 7xaFtfqG4hIR6+F8quyJWS4= =sYIE -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Hard Drive Issues
Garrett Cooper [EMAIL PROTECTED] writes: Justin wrote: Greetings, I'm getting the following errors on the terminal: ad1: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=186691903 ad1: FAILURE - READ_DMA status=51READY,DCS,ERROR error=84ICRC,ABORTED LBA=186691903 g_vfs_done():ad1s1d[READ(offset=95586222080, length=49152)]error = 5 And similar, with the LBA number, offset number, and error=84 changes to error=10. The hard disk drives and data seem to be remaining intact and working. Can someone direct me as to what these errors mean, and if they are serious? Regards, Justin P. Michel Based on your error message it appears that data is getting corrupted in transit on whatever channel you're using for your drives. Have you tried using the disk on another channel by chance, or tried another disk on the same channel? -Garrett Or cables; any chance you've broken (over-bent) an ATA cable lately? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Hard Drive Issues
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Lowell Gilbert wrote: Garrett Cooper [EMAIL PROTECTED] writes: Justin wrote: Greetings, I'm getting the following errors on the terminal: ad1: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=186691903 ad1: FAILURE - READ_DMA status=51READY,DCS,ERROR error=84ICRC,ABORTED LBA=186691903 g_vfs_done():ad1s1d[READ(offset=95586222080, length=49152)]error = 5 And similar, with the LBA number, offset number, and error=84 changes to error=10. The hard disk drives and data seem to be remaining intact and working. Can someone direct me as to what these errors mean, and if they are serious? Regards, Justin P. Michel Based on your error message it appears that data is getting corrupted in transit on whatever channel you're using for your drives. Have you tried using the disk on another channel by chance, or tried another disk on the same channel? -Garrett Or cables; any chance you've broken (over-bent) an ATA cable lately? True.. forgot about that . - -Garrett -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFLne96CkrZkzMC68RAtLoAJwKwjpHHyrUpjE8E6r7hJnGYb6iggCggBLq 4GNastrONxN0d5PFuksa6bo= =CanV -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Hard Drive Issues
On 12/10/06, Justin [EMAIL PROTECTED] wrote: Greetings, I'm getting the following errors on the terminal: ad1: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=186691903 ad1: FAILURE - READ_DMA status=51READY,DCS,ERROR error=84ICRC,ABORTED LBA=186691903 g_vfs_done():ad1s1d[READ(offset=95586222080, length=49152)]error = 5 And similar, with the LBA number, offset number, and error=84 changes to error=10. The hard disk drives and data seem to be remaining intact and working. Can someone direct me as to what these errors mean, and if they are serious? Regards, Justin P. Michel Since as you say everything is working, maybe it is a good idea to take a look and run the fsck command at least it may give you some more information, which you can post in order to get better answers ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- Spiros Papadopoulos ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Hard Drive Issues
On Thu, Oct 12, 2006 at 06:54:53PM +0100, Spiros Papadopoulos wrote: Since as you say everything is working, maybe it is a good idea to take a look and run the fsck command at least it may give you some more information, which you can post in order to get better answers That too, but first I'd start with sysutils/smartmontools and see what the drive and its built-in log says. -- David Kelly N4HHE, [EMAIL PROTECTED] Whom computers would destroy, they must first drive mad. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
