At 08:12 PM 3/20/2006, Edwin D. Vinas wrote:
Hi,
After a power outage my FreeBSD-4.10 server's 40GB HDD had many
fragmentations and no matter how I repeatedly do fsck, the errors saying
hard error reading fsbn are still there. I tried doing fsck over and
over
but it seems this is already
fragmentations and no matter how I repeatedly do fsck, the errors saying
hard error reading fsbn are still there. I tried doing fsck over and over
but it seems this is already a hardware error and can no longer be
corrected. So my goal now is to recover my files!
First, I did a mount -a and was able
Hi,
After a power outage my FreeBSD-4.10 server's 40GB HDD had many
fragmentations and no matter how I repeatedly do fsck, the errors saying
hard error reading fsbn are still there. I tried doing fsck over and over
but it seems this is already a hardware error and can no longer be
corrected. So
On 3/20/06, Edwin D. Vinas [EMAIL PROTECTED] wrote:
Is there anyway to still recover my files? Is there a way I can edit fstab
to remove f option so I can't have those getty errors? Or is it possible
to mount the server's HDD in another FreeBSD machine?
Can't you boot from a FreeBSD CD then
Matt Navarre wrote:
After a power outage last night I rebooted my computer and fsck
complained of the following :
ad1s2e: hard error reading fsbn 5103776 (ad1s2 bn 5103776; cn 317 tn
177 sn 20) status=59 error=40
Then goes on for a while giving the same error on blocks 5103776 -
5103807
Matt Navarre [EMAIL PROTECTED] writes:
Now, on to the damaged sectors, how to recover the data? dd stops when
it hits bad blocks, so we can't use that to copy the slice. same with
dump(8) as far as I can tell. So. Download dd_rescue from
http://www.garlof.de/kurt/linux/ddrescue/
Just out of
Matt Navarre wrote:
Matt Navarre wrote:
After a power outage last night I rebooted my computer and fsck
complained of the following :
ad1s2e: hard error reading fsbn 5103776 (ad1s2 bn 5103776; cn 317 tn
177 sn 20) status=59 error=40
Then goes on for a while giving the same error on blocks
Lowell Gilbert wrote:
Matt Navarre [EMAIL PROTECTED] writes:
Now, on to the damaged sectors, how to recover the data? dd stops when
it hits bad blocks, so we can't use that to copy the slice. same with
dump(8) as far as I can tell. So. Download dd_rescue from
After a power outage last night I rebooted my computer and fsck
complained of the following :
ad1s2e: hard error reading fsbn 5103776 (ad1s2 bn 5103776; cn 317 tn
177 sn 20) status=59 error=40
Then goes on for a while giving the same error on blocks 5103776 -
5103807, except for block
there.
we'll see.
The power surge may have damaged your power supply.
orville.
--- Matt Navarre [EMAIL PROTECTED] wrote:
After a power outage last night I rebooted my
computer and fsck
complained of the following :
ad1s2e: hard error reading fsbn 5103776 (ad1s2 bn
5103776; cn 317 tn
177 sn 20
You could try using SpinRite.
http://www.grc.com
It now works with all filesystems and is up to version
6.
Mark
--- Tuc [EMAIL PROTECTED] wrote:
Problem is, unless it fails the Dell Power on
IDE test, they won't
replace it. :-/ Guess I just keep backing it up
until it fails
Tuc wrote:
[ ...and SMART status... ]
So is there something I should do?
Get a new hard drive, this one is not going to live much longer.
Problem is, unless it fails the Dell Power on IDE test, they won't
replace it. :-/ Guess I just keep backing it up until it fails totally.
Get a Dell
Problem is, unless it fails the Dell Power on IDE test, they won't
replace it. :-/ Guess I just keep backing it up until it fails totally.
Get a Dell diagnostic disk for your system, and run the hard drive test. It
ought to see the problems, which you can then report back to Dell in
/kernel: ad0s1e: hard error reading fsbn 29926527 of
9843232-9843263 (ad0s1 bn 29926527; cn 1862 tn 214 sn 15) status=59 error=40
Other files in /home/dcf were affected, also - many seemed to be related
to firefox, which had been running when the system froze/was rebooted.
I dropped to single user
On Sat, Oct 23, 2004 at 05:26:27PM -0500, David Fleck wrote:
Oct 23 16:58:12 grond /kernel: ad0s1e: hard error reading fsbn 29926527 of
9843232-9843263 (ad0s1 bn 29926527; cn 1862 tn 214 sn 15) status=59
error=40
Is this likely a one-time thing, or a symptom of creeping disk death
On Sun, 24 Oct 2004 [EMAIL PROTECTED] wrote:
On Sat, Oct 23, 2004 at 05:26:27PM -0500, David Fleck wrote:
Is this likely a one-time thing, or a symptom of creeping disk death?
(The 'hard error' messages only started after the reboot.)
You could try /usr/ports/sysutils/smartmontools to run
On Sat, Oct 23, 2004 at 07:18:29PM -0500, David Fleck wrote:
On Sun, 24 Oct 2004 [EMAIL PROTECTED] wrote:
On Sat, Oct 23, 2004 at 05:26:27PM -0500, David Fleck wrote:
Is this likely a one-time thing, or a symptom of creeping disk death?
(The 'hard error' messages only started after the
### Test 1:
# smartctl -a ad0 | more
### Test 2:
# smartctl -t offline ad0
then wait for offline selftests to complete, then again:
# smartctl -a ad0 | more
### Test 3:
# smartctl -t long ad0
again wait for selfttests to complete, then again:
# smartctl -a ad0 | more
Ok,
Tuc wrote:
ad0: FAILURE - READ_DMA status=51READY,DSC,ERROR error=40UNCORRECTABLE
LBA=11291
ad0: FAILURE - READ_DMA status=51READY,DSC,ERROR error=40UNCORRECTABLE
LBA=112977803
ad0: FAILURE - READ_DMA status=51READY,DSC,ERROR error=40UNCORRECTABLE
LBA=112977835
[ ...and SMART status... ]
Tuc wrote:
ad0: FAILURE - READ_DMA status=51READY,DSC,ERROR error=40UNCORRECTABLE
LBA=11291
ad0: FAILURE - READ_DMA status=51READY,DSC,ERROR error=40UNCORRECTABLE
LBA=112977803
ad0: FAILURE - READ_DMA status=51READY,DSC,ERROR error=40UNCORRECTABLE
LBA=112977835
[ ...and SMART
I started seeing the error messages in my logs. When I
googled the error some seem to think it may be a hardware
issue and some seem to think it's o/s specific. Trying to
see what's the general opinon. Running 4.9
Jun 13 00:30:26 santacruz /kernel: ad0s1h: hard error
reading fsbn 197442991
. If you post dmesg output and hardware details, I'm sure someone who's
familiar with that hardware will let you know if this is expected or not.
Jun 13 00:30:26 santacruz /kernel: ad0s1h: hard error
reading fsbn 197442991 of 26369632-26369887 (ad0s1 bn
197442991; cn 12290 tn 65 sn 46) status=59
: 88350MB IC35L090AVV207-0 [179505/16/63] at
ata0-master BIOSDMA
acd0: CDROM Compaq CRD-8322B at ata1-master PIO4
Mounting root from ufs:/dev/ad0s1a
ad0s1h: hard error reading fsbn 197442815 of
26369632-26369887 (ad0s1 bn 197442815; cn 12290 tn 62 sn 59)
trying PIO mode
ad0: DMA problem fallback to PIO
PIO4
Mounting root from ufs:/dev/ad0s1a
ad0s1h: hard error reading fsbn 197442815 of
26369632-26369887 (ad0s1 bn 197442815; cn 12290 tn 62 sn 59)
trying 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
it looks like I'll have to invest in that 3ware raid card
after all.
Thanks,
Kevin
-Original Message-
From: Bill Moran [mailto:[EMAIL PROTECTED]
Sent: Monday, June 14, 2004 11:35 AM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Re: Hard Drive going bad? (hard error reading fsbn
Greetings all,
Due to yesterday error on 4.9-RELEASE of FreeBSD.
snip
hard error reading fsbn
ad0: DMA problem fallback to PIO mode
libfreetype.a: Bad address
/snip
i tried changing some kernel paramaters
mainly these two
hw.ata.atapi_dma=1
hw.ata.ata_dma=1
However, that didn't
On Fri, 12 Mar 2004 09:59:17 +1100 (EST)
eodyna [EMAIL PROTECTED] wrote:
Greetings all,
Due to yesterday error on 4.9-RELEASE of FreeBSD.
snip
hard error reading fsbn
ad0: DMA problem fallback to PIO mode
libfreetype.a: Bad address
/snip
The two are completely unrelated
with the main error
msg:
large snip
further more, when i look in dmesg i get the
following:
ad0s1g: hard error reading fsbn 17696655 of
7946848-7946879 (ad0s1 bn 17696655; cn 18726 tn 9 sn
18) trying PIO mode
ad0: DMA problem fallback to PIO mode
ad0s1g: hard error reading fsbn 17696671 of
7946848
[ please don't post on top, it's hard to read ]
On Fri, 12 Mar 2004 11:33:08 +1100 (EST)
eodyna [EMAIL PROTECTED] wrote:
Hello,
Thanks for your response.
I dont think they are totally unrelated, because when
i try to install XFree86-4 and that particular library
it gets the error
i forgot to include the mailing list.
doh!
--- Ion-Mihai Tetcu [EMAIL PROTECTED] wrote:
[ please don't post on top, it's hard to read ]
sorry :/
Hello,
Thanks for your response.
I dont think they are totally unrelated, because
when
i try to install XFree86-4 and that
Hi all,
This morning I found this entry in the messages:
Oct 15 08:20:25 pippi /kernel: ad6: hard error reading fsbn 1783727 of 0-15 (ad6 bn
1783727; cn 1769 tn 9 sn 8) trying PIO
mode
Oct 15 08:20:27 pippi /kernel: ad6: DMA problem fallback to PIO mode
From searching around a bit I noticed
On Wed, Oct 15, 2003 at 02:50:14PM +0200, Marko Leer wrote:
Hi all,
This morning I found this entry in the messages:
Oct 15 08:20:25 pippi /kernel: ad6: hard error reading fsbn 1783727 of 0-15 (ad6 bn
1783727; cn 1769 tn 9 sn 8) trying PIO
mode
Oct 15 08:20:27 pippi /kernel: ad6: DMA
:/dev/ad0s2a
ad0s2g: hard error reading fsbn 153560175 of
36456416-36456543 (ad0s2 bn 1535601
75; cn 9558 tn 173 sn 6) status=59 error=40
ad0s2g: hard error reading fsbn 36456531 (ad0s2 bn
36456531; cn 2269 tn 80 sn 6)
status=59 error=40
ad0s2g: hard error reading fsbn 36456538 (ad0s2 bn
36456538; cn
hi
I get the same:
ad0s2f: hard error reading fsbn 3978952 of 1207492-1207495
(ad0s2 bn 3978952; cn 3947 tn 5 sn 61) status=59 error=40
every day. I believe it happens during the periodic daily scripts at night.
Is there a way to tell what file lives on that particular block
34 matches
Mail list logo
