check to see if the drive mfgr has a firmware update for your disks
Ted
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Jack Barnett
Sent: Wednesday, May 09, 2007 1:15 AM
To: freebsd-questions@freebsd.org
Subject: Re: Disk problems?
hrm
hrm... ?
Doing it again:
twa0: INFO: (0x04: 0x000B): Rebuild started: unit=0
twa0: ERROR: (0x04: 0x003A): Drive power on reset detected: port=0
twa0: ERROR: (0x04: 0x003A): Drive power on reset detected: port=1
twa0: ERROR: (0x04: 0x003A): Drive power on reset detected: port=0
twa0: ERROR:
6.2 Release/stable
(synced source as of yesterday, rebuilt and still getting it)
On 5/7/07, Peter A. Giessel [EMAIL PROTECTED] wrote:
On 2007/05/07 11:16, Jack Barnett seems to have typed:
I have a 3ware (AMCC) 9500S-4LP RAID card and 4 disks in 2 Mirror 1
arrays:
Unit 1: 2 x 80 gigs
Unit
Martin Kruse Jensen [EMAIL PROTECTED] writes:
I'm having some problems with my FreeBSD 5.3 server, running on an AMD
using IDE disks. The disk is having some problems:
# dmesg
ad0: FAILURE - READ_DMA timed out
ad0: TIMEOUT - READ_DMA retrying (2 retries left) LBA=18986207
ad0: FAILURE -
Back up those HD right now before you lose all the data and then
replace them with new ones.
There is nothing you can do with them in FreeBSD.
Check the HD mfg web site for daig program which runs under ms/dos.
But in most cases this daig program will just confirm HD has bad
sectors and tell you
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
orville weyrich wrote:
Before doing anything to your hard drive, check out
your computer's power supply -- if they go off
tolerance on voltages, you may start getting disk
errors -- often the first sign of power supply
problems.
Hmmm, Ok, I can see that. The errors are confined to one slice on
10 matches
Mail list logo