On Tue, 3 Jan 2006 12:25 pm, Gayn Winters wrote: > > [mailto:[EMAIL PROTECTED] On Behalf Of > > Russell J. Wood > > Sent: Monday, January 02, 2006 3:54 PM > > To: freebsd-questions@freebsd.org > > Subject: Re: Disk error messages (ad0: HARD READ ERROR blk# > > xxxxxx) > > > > On Mon, Jan 02, 2006 at 11:15:08PM +0000, [EMAIL PROTECTED] wrote: > > > Hi there, > > > > > > On my screen, there were messages like the followings > > > > comeing up. I have to > > > > > reboot mutiple times to get it boot up normally. Does this > > > > mean I have to > > > > > replace the disk which is a relatively new disk (1-2 > > > > years)? Any simple way to > > > > > fix it and to avoid the time consuming task? > > > > > > > > > ad0: 39205MB <Maxtor 6EXXXXX> [79656/16/63] at ata0-master > > > WDMA2 ad0: HARD READ ERROR blk# 131199 > > > ad0: HARD READ ERROR blk# 131199 status=59 error=40 > > > ad0: DMA problem fallback to PIO mode > > > ad0: HARD READ ERROR blk# 11272319 status=59 error=40 > > > ad0: HARD READ ERROR blk# 11272319 status=59 error=40 > > > ad0: HARD READ ERROR blk# 11272319 status=59 error=40 > > > ad0: HARD READ ERROR blk# 131199 status=59 error=40 > > > ad0: HARD READ ERROR blk# 3473535 status=59 error=40 > > > ad0: HARD READ ERROR blk# 9240703 status=59 error=40 > > > ad0: HARD READ ERROR blk# 17367167 status=59 error=40 > > > ad0: HARD READ ERROR blk# 17760383 status=59 error=40 > > > > I suspect that you have bad sectors on your hard disk drive > > (and many of > > them). A good tool to use is Segate's Seatools > > (http://www.seagate.com/support/seatools/index.html). Just > > burn the Seatools Desktop edition to CDROM and boot from it. > > > > - Russell > > After you've checked for loose cables, you might want to take > the drive out and check it in another system (using the > Seagate or other such tools). If indeed the problem is with > DMA, the drive might be ok but the MB is flakey. Perhaps the > PC or MB manufacturer has diagnosics with which you can zero > into the latter ugly possiblity. In any case, get yourself a > backup asap (at least of the user data so that you can recover > from a fresh installation.) Unless you are getting other > types of errors, it is probably still possible to copy the > drive with dd using bs=512b, and this would be your quickest > fix of a hard drive problem. Run fsck on your new disk after > the copy. >
dd is generally not a good choice for copying disks (although it does sort of work). The new disk will appear unclean when copied from a live fs and may in fact have an odd instance of a file which has not yet been physically updated. And it just takes too long since you copy empty space as well as real data. Instead slice, partition the new disk and create newfs on the new partitions. And then pipe dump (using the snapshot option) through to restore for each fs on the disks. I have (successfully) used this approach extensively for cloning systems. Malcolm _______________________________________________ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
