Date: Thu, 2 Jan 2003 21:50:40 +0100 From: Andreas Ntaflos <ant@overclockers.at> To: freebsd-stable@freebsd.org Subject: Saving a partially rotten IBM DTLA-307030 Harddisk Message-ID: <20030102205040.GC22880@Deadcell.ant>
next in thread | raw e-mail | index | archive | help
Hello list (sorry for crossposting, hope I am doing the right thing),
I've got the following problem which I hope someone could help me with: One
of my boxes running FreeBSD 4.7-STABLE has an IBM DTLA-307030 (30GB) which
worked very well for more than 2 years now, but I think it starts rotting
away according the following:
* The security output shows something like this every day since Dec 11:
-------8<------
Checking setuid files and devices:
find: /usr/home/user1/path/to/file1: Input/Output error
find: /usr/home/user1/path/to/file2: Input/Output error
.
.
[snip, lots of similar blahs]
.
.
find: /usr/home/user1/path/to/file17: Input/Output error
------->8------
So I know that it is just a specific area on the disk that seems to be
done for, which corresponds to the following console messages:
* ad4: READ command timeout tag=0 serv=0 - resetting
ata2: resetting devices .. done
ad4: READ command timeout tag=0 serv=0 - resetting
ata2: resetting devices .. done
ad4: READ command timeout tag=0 serv=0 - resetting
ata2: resetting devices .. done
swap_pager: indefinite wait buffer: device: #ad/0x20021, blkno: 1656,
size: 4096
ad4: READ command timeout tag=0 serv=0 - resetting
ad4: trying fallback to PIO mode
ata2: resetting devices .. done
ad4s1h: hard error reading fsbn 62679087 of 29163648-29163679 (ad4s1 bn
62679087; cn 3901 tn 151 sn 9) status=59 error=40
ad4s1h: hard error reading fsbn 62679087 of 29163648-29163679 (ad4s1 bn
62679087; cn 3901 tn 151 sn 9) status=59 error=40
* trying to `rm -rf` the affected directories and files results in the
same messages:
rm: /usr/home/user1/path/to/file1: Input/Output error
rm: /usr/home/user1/path/to/file2: Input/Output error
ad4s1h: hard error reading fsbn 62679087 of 29163648-29163679 (ad4s1 bn
62679087; cn 3901 tn 151 sn 9) status=59 error=40
ad4s1h: hard error reading fsbn 62679087 of 29163648-29163679 (ad4s1 bn
62679087; cn 3901 tn 151 sn 9) status=59 error=40
As can be seen, the data in that affected area is virtually lost, but
luckily not very important. So my question is, what can I do to get
the disk fully operational again? Some time ago I read that writing binary
zeroes there could be used as some kind of low-level-format to get rid of
the bad sectors. If this would be of any use, how would I accomplish to
dd /dev/zero to just that specific part of the disk, leaving the rest
intact? Is that possible at all? Or are there any other ways to solve that
problem, apart from buying a new disk or low-level-formating the whole
thing?
I would really appreciate any help or hints on that.
Kind regards
--
Andreas "ant" Ntaflos | "A cynic is a man who knows the price of
ant@overclockers.at | everything, and the value of nothing."
Vienna, AUSTRIA | Oscar Wilde
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030102205040.GC22880>