Date: Wed, 31 May 2000 12:51:15 +0100 From: Steve Roome <steve@sse0691.bri.hp.com> To: freebsd-questions@freebsd.org Subject: hard read error Message-ID: <20000531125115.G41986@moose.bri.hp.com>
next in thread | raw e-mail | index | archive | help
Firstly, apologies if this seems like a stupid question... I've just started getting "bad blocks" cropping up on a newish drive (it's a 34gb IBM IDE drive - <6 months old), I also, very recently upgraded from 3.4-stable to 4.0-release. [More info at end] I very rarely boot to DOS/Windows and mainly use the DOS partition from FreeBSD... some bad blocks appeared tody when DOS failed to boot and DOS scandisk seems to think they're bad. ( I thought they were remapped by the drive - and if they show up at all, then it's a really dead disk with a lot of bad blocks ? ) Although, is it possible that FreeBSD has written something wrong into the DOS partition which has caused DOS to think that there is something wrong with the disk and mark the sectors/clusters/blocks of disk bad - even if they're not. Or, has DOS just confused itself... Or, sad case, does the following give unmistakable proof that I should invest in a new disk ( and try and get a refund on this one ? unlikely! ) (Normally I'd replace any disk as soon as it starts developing bad blocks, but in this case I'm a bit concerned that there may be another solution.) (Also, I'm not subscribed to this list so please cc me on replies) Thanks in advance, Steve Roome ...from system only recently booted... # more /etc/fstab # Device Mountpoint FStype Options Dump Pass# /dev/ad0s1b none swap sw 0 0 /dev/ad0s1a / ufs rw 1 1 /dev/ad0s1g /home ufs rw 2 2 /dev/ad0s3e /space ufs rw 2 2 /dev/ad0s1f /usr ufs rw 2 2 /dev/ad0s1e /var ufs rw 2 2 /dev/acd0c /cdrom cd9660 ro,noauto 0 0 proc /proc procfs rw 0 0 kern /kern kernfs rw 0 0 #/dev/ad0s2c /dos msdos rw,-u1000 0 0 #Taken DOS out due to bad blocks appearing... # dd if=/dev/ad0s2c of=/dev/null bs=2048k ad0: HARD READ ERROR blk# 19485247ata0-master: WARNING: WAIT_READY active=ATA_AC TIVE_ATA ad0: DMA problem fallback to PIO mode ad0: DMA problem fallback to PIO mode ad0: DMA problem fallback to PIO mode ad0: DMA problem fallback to PIO mode ad0: DMA problem fallback to PIO mode ad0: DMA problem fallback to PIO mode ad0: DMA problem fallback to PIO mode ad0: DMA problem fallback to PIO mode ad0: DMA problem fallback to PIO mode ad0: DMA problem fallback to PIO mode ad0: HARD READ ERROR blk# 19485407 status=59 error=40 ad0: DMA problem fallback to PIO mode dd: /dev/ad0s2c: Input/output error 744+0 records in 744+0 records out 1560281088 bytes transferred in 74.819467 secs (20853945 bytes/sec) # May 31 11:15:16 snuggly /kernel: ad0: HARD READ ERROR blk# 19485247ata0-master : WARNING: WAIT_READY active=ATA_ACTIVE_ATA May 31 11:15:16 snuggly /kernel: ad0: HARD READ ERROR blk# 19485247ata0-master: WARNING: WAIT_READY active=ATA_ACTIVE_ATA May 31 11:15:18 snuggly /kernel: ad0: DMA problem fallback to PIO mode May 31 11:15:18 snuggly /kernel: ad0: DMA problem fallback to PIO mode May 31 11:15:18 snuggly last message repeated 9 times May 31 11:15:18 snuggly /kernel: ad0: HARD READ ERROR blk# 19485407 status=59 er ror=40 May 31 11:15:18 snuggly last message repeated 9 times May 31 11:15:18 snuggly /kernel: ad0: HARD READ ERROR blk# 19485407 status=59 er ror=40 May 31 11:15:18 snuggly /kernel: ad0: DMA problem fallback to PIO mode May 31 11:15:18 snuggly /kernel: ad0: DMA problem fallback to PIO mode # ###### now it does it agin in PIO mode - so it really is knackered, or marked ###### bad anyway ?? # dd if=/dev/ad0s2c of=/dev/null bs=2048k ad0: HARD READ ERROR blk# 19485407 status=59 error=40 dd: /dev/ad0s2c: Input/output error 744+0 records in 744+0 records out 1560281088 bytes transferred in 158.577372 secs (9839242 bytes/sec) # May 31 11:21:13 snuggly /kernel: ad0: HARD READ ERROR blk# 19485407 status=59 error=40 May 31 11:21:13 snuggly /kernel: ad0: HARD READ ERROR blk# 19485407 status=59 er ror=40 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000531125115.G41986>