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 pro
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: (0x04
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
>
I have a 3ware (AMCC) 9500S-4LP RAID card and 4 disks in 2 Mirror 1 arrays:
Unit 1: 2 x 80 gigs
Unit 2: 2 x 400 gigs
Under windows this was working fine. Both disks where "healthy" and running
(I could test this by unplugging one or the other):
Under FreeBSD though, it says it's not working:
Ma
I would try moving the disk to another server and doing the fsck there. If
you get the same error you can try increasing the memory limits.
You could also try booting the live CD and run the fsck. If you do this
you may need to us sysctl to raise the memory limits if you get that error.
My power supply died and now my root file system seems to be having
major problems. I run fsck -y on it and after complaining about
dozens of sectors having problems being read and "Unexpected soft
update"s, fsck ends with:
fsck_ufs: cannot alloc 3962308096 bytes for inoinfo
Can anything be don
On 3/4/06 2:49 AM, "Gayn Winters" <[EMAIL PROTECTED]> wrote:
>> [mailto:[EMAIL PROTECTED] On Behalf Of Shane Ambler
>> Sent: Saturday, April 01, 2006 3:10 AM
>> To: FreeBSD Mailing Lists
>> Subject: Hard Disk problems
>>
>>
>> A few day
> You'll probably want to
> reread the section in the Handbook on Moving to a Larger Disk, since
> this is a good time to rethink the sizes of your partitions.
Sorry, this info is in FAQs 9.1 and 9.2 not in the Handbook.
http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/disks.html
-gayn
Brist
> [mailto:[EMAIL PROTECTED] On Behalf Of Shane Ambler
> Sent: Saturday, April 01, 2006 3:10 AM
> To: FreeBSD Mailing Lists
> Subject: Hard Disk problems
>
>
> A few days ago I started getting some disk errors and can't
> seem to find a
> reference to find a
A few days ago I started getting some disk errors and can't seem to find a
reference to find a way to fix them (other than the obvious re-format)
The daily security run output contains the following (abbreviated)
Checking setuid files and devices:
find: /usr/ports/databases/db43/work/db-4.3.28/d
(Please Cc: me on all replies.)
I bought a USB CF reader/writer. When I plug it in, the system sees it
as:
kernel: umass0: VIA Technologies Inc. USB 2.0 Card Reader, rev 2.00/0.03, addr
2
but no matter what I do the system cannot see the CF disk in the unit.
I then tried the same card in an
On Jan 2, 2006, at 10:31 AM, Anthony M. Agelastos wrote:
On Jan 1, 2006, at 11:28 PM, Anthony M. Agelastos wrote:
Hello all,
In doing some routine items on my FreeBSD box, it started behaving
oddly. I rebooted and to my surprise, I started receiving many
messages displaying information
On Jan 1, 2006, at 11:28 PM, Anthony M. Agelastos wrote:
Hello all,
In doing some routine items on my FreeBSD box, it started behaving
oddly. I rebooted and to my surprise, I started receiving many
messages displaying information regarding that /usr has issues. It
puts me directly into s
Hello all,
In doing some routine items on my FreeBSD box, it started behaving
oddly. I rebooted and to my surprise, I started receiving many
messages displaying information regarding that /usr has issues. It
puts me directly into single user mode and tells me to run fsck
manually. When I
@freebsd.org
Subject: Disk problems
Hi
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 - READ_DMA
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: FAILUR
Hi
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 - READ_DMA timed out
ad0: TIMEOUT - READ_DMA retryin
Heh, should've mentioned: I'm installing FreeBSD 5.3-RELEASE.
The disk only has one partition (and 10 GiB of unallocated space) right now by
the way, and that's the one Window's on. ad0s1 should represent that partition
if I'm reading the manual correctly.
>> Ulf Magnusson wrote:
>>Today I deci
Heh, should've mentioned; I'm installing FreeBSD 5.3
> Ulf Magnusson wrote:
>Today I decided to install FreeBSD, and so I grabbed a FreeBSD installation CD
>off the net. The first time I booted from the installation CD, everything
>went fine (seemingly), and I soon found myself in sysinstall. No
Today I decided to install FreeBSD, and so I grabbed a FreeBSD installation CD
off the net. The first time I booted from the installation CD, everything went
fine (seemingly), and I soon found myself in sysinstall. Not quite ready to
install at that point, and needing to shut down the system, I
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
http://www.garlof.de/kurt/linux/dd
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 510
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 ou
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, exc
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 t
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 510377
{REVISED POST}
Hello experts,
I have experienced so much problems installing FreeBSD 5.3BETA7 I guess
it's time for me to ask the experts.
I have two disks:
1. Maxtor (DiamondMax Plus 9)
120GB ATA/133
Mfg Date: 30 Jan 2004
Code: YAR41BW0
E-H011-02-3880 (3.5 SERIES)
2. Western D
In which log file should I look to find disk error messages, and which
variable controls the log level for this kind of Problems (if there is
any)
Background.
I have FreeBSD 5.2.1-RELEASE-p11 running and serving my windows client
a few samba shares. (2 shares from 2 physicaly different disks to be
Jesse Guardiani wrote:
> Howdy list,
>
> I'm running FreeBSD 5.1-RELEASE. I just bought a generic
> USB 1.1/2.0/firewire external drive enclosure for my 32gb
> Travelstar 12.5mm hard drive.
>
> The device shows up like this:
>
> Nov 18 14:06:16 trevarthan kernel: umass0: Acer Labs USB 2.0 Stora
Howdy list,
I'm running FreeBSD 5.1-RELEASE. I just bought a generic
USB 1.1/2.0/firewire external drive enclosure for my 32gb
Travelstar 12.5mm hard drive.
The device shows up like this:
Nov 18 14:06:16 trevarthan kernel: umass0: Acer Labs USB 2.0 Storage Device, rev
2.00/1.03, addr 3
Nov 18 1
Dear Sirs.
I use FreeBSD 5.0-CURRENT on several experimental systems. I try to test
new diskless and picobsd facilities and abilities of the newest FBSD
5.0-CURRENT stuff and I am a little bit disappointed.
First there is a little bug in the picobsd shell-script/command:
newfs does no longer sup
dennis wrote:
[ ... ]
Are these problems related to the new-ness of my mobo and chipset or am
I just doing something wrong? Is there a work around for the problem?
I want to dedicate the entire disk to the freebsd installation.
Try using MS-DOS' FDISK to create your partitions, and see whether
Hello, I am trying to install freebsd 5.0 on a Maxtor 52049U4 20G hard
drive. The disk is slaved on ide0. The fdisk will not let me create a
slice larger than 2G. Further more I can not create any number of slices
totaling more than 2G. The mobo is a MSI KT4 ulta with a VIA KT400
chipset.
Dmitry,
If you have the smart start CD that came with the server, it will have those
utiliies on it. If you do not, I suggest that you visit Compaq/HP's web
site, download the CD, burn it and use that. It contains a utility to
create a "system partition" on one of the drives. I HIGHLY recommend
34 matches
Mail list logo
