[...]
PS: I don't suppose anyone knows a real good simple blow by blow total
newby dialog, as to how to realiably and correctly create and setup Jails
on FreeBSD 8.0? All the man pages I've found so far, are way over my
head. Good "Reference" material admittedly, but no good as an
instruction
On 5 Jun 2011 at 16:55, Michael Powell wrote:
> per...@pluto.rain.com wrote:
> [snip]
> >
> > Power supplies do fail occasionally, and not always in obvious
> > ways such as failing to turn on at all. The output voltages may be
> > a little too high or too low, or they may be correct but with
>
per...@pluto.rain.com wrote:
[snip]
>
> Power supplies do fail occasionally, and not always in obvious
> ways such as failing to turn on at all. The output voltages may
> be a little too high or too low, or they may be correct but with
> excessive ripple or electrical noise; or the supply may be
p messing with the blessed things!
I have a sick Land Rover to fix too. Gearbox rear oil seal, also rear
drive shaft UJ's. At least I can use big hammers on that sometimes...
(Therapy!) Oh, the grass needs cutting, and I'm now also under
instruction to change the bed, when the cat's
On 06/05/2011 03:48 AM, per...@pluto.rain.com wrote:
Kaya Saman wrote:
Did you apply any updates shortly before it started to fail?
No updates! I did however, install unrar through ports.
Intuitively, that seems unlikely to have triggered the problem.
This doesn't sou
so much
nicer if you don't have to keep messing with the blessed things!
I have a sick Land Rover to fix too. Gearbox rear oil seal, also rear
drive shaft UJ's. At least I can use big hammers on that sometimes...
(Therapy!) Oh, the grass needs cutting, and I'm now also under
Kaya Saman wrote:
> > Did you apply any updates shortly before it started to fail?
>
> No updates! I did however, install unrar through ports.
Intuitively, that seems unlikely to have triggered the problem.
> I remember on other boards that went on me in the past with
> capacitor issues, a bunc
[...]
Hmmm Hard drives do not like heat! Check the PSU voltages with a
meter, for accuracy and ripple. Failing SMPS's can do all sorts of odd
things.
Capacitor problems. Been there done that. They can be changed for very
low cost, other than your time.
DaveB
You might guess by know, I k
On 4 Jun 2011 at 10:52, Kaya Saman wrote:
> Many thanks for the response!
>
> On 06/04/2011 02:00 AM, per...@pluto.rain.com wrote:
> > Kaya Saman wrote:
> >
> >
> >> I have an ancient pre-HT PIV machine with<500MB RAM.
> >> ...
> >> Everything was running fine until round about 2 days
> >> a
On 3 Jun 2011 at 15:09, Kaya Saman wrote:
> Hi,
>
> I have an ancient pre-HT PIV machine with <500MB RAM.
>
> The system has an extra PCI->SATA card installed so I can make use of
> modern high capacity drives.
>
> Everything was running fine until round about 2 days ago when the
> system star
Many thanks for the response!
On 06/04/2011 02:00 AM, per...@pluto.rain.com wrote:
Kaya Saman wrote:
I have an ancient pre-HT PIV machine with<500MB RAM.
...
Everything was running fine until round about 2 days
ago when the system started locking up on me?
... is there anyway to fix the
Kaya Saman wrote:
> I have an ancient pre-HT PIV machine with <500MB RAM.
> ...
> Everything was running fine until round about 2 days
> ago when the system started locking up on me?
>
> ... is there anyway to fix the kernel error quickly?
Did you apply any updates shortly before it started to f
Hi,
I have an ancient pre-HT PIV machine with <500MB RAM.
The system has an extra PCI->SATA card installed so I can make use of
modern high capacity drives.
Everything was running fine until round about 2 days ago when the system
started locking up on me?
Current drive configuration for
On 12/28/08, jerome wrote:
> Hi Paul,
>
> The patch worked (almost).
>
> At first a program accessing a disk that reported an uncorrectable error,
> the program just segfaulted.
>
> Another instance let to the situation that I was only able to ping the
> server.
> No ssh or console access was poss
B. Mahol [mailto:one...@gmail.com]
To: jerome [mailto:jer...@code-monkey.nl]
Cc: freebsd-questions@freebsd.org
Sent: Mon, 22 Dec 2008 13:15:12 +0100
Subject: Re: disk error / reboot / 6.3
On 12/22/08, jerome wrote:
> Hi Paul,
>
> The server resets while running, like pressing
Hi Paul,
Ok, thanks.
Will let you know the outcome.
-Jerome
_
From: Paul B. Mahol [mailto:one...@gmail.com]
To: jerome [mailto:jer...@code-monkey.nl]
Cc: freebsd-questions@freebsd.org
Sent: Mon, 22 Dec 2008 13:15:12 +0100
Subject: Re: disk error / reboot / 6.3
On 12/22/08, jerome
On 12/22/08, jerome wrote:
> Hi Paul,
>
> The server resets while running, like pressing the reset button...
Try this patch:
--- src/sys/dev/ata/ata-queue.c 2008/10/27 09:26:24 1.74
+++ src/sys/dev/ata/ata-queue.c 2008/11/27 03:37:46 1.75
@@ -357,7 +357,7 @@ ata_completed(void *context,
Hi Paul,
The server resets while running, like pressing the reset button...
-Jerome
_
From: Paul B. Mahol [mailto:one...@gmail.com]
To: jerome [mailto:jer...@code-monkey.nl]
Cc: freebsd-questions@freebsd.org
Sent: Mon, 22 Dec 2008 00:35:04 +0100
Subject: Re: disk error / reboot / 6.3
On 12/21/08, jerome wrote:
> Hi,
>
> We are running 6.3 on a fileserver with a couple of data disks.
>
> Once the server encounters an error on a data disk (os disk is separate) the
> server will reset itself without warning.
It just reset or it panic? There is known panic on bad block on some Fr
Hi,
We are running 6.3 on a fileserver with a couple of data disks.
Once the server encounters an error on a data disk (os disk is separate) the
server will reset itself without warning.
We can usually identify the problem disk with a smartctl, the disk will show
'Offline u
Bill Moran wrote:
> Zbigniew Szalbot wrote:
> > [...]
> > Jun 14 01:13:38 relay kernel: ad12: FAILURE - READ_DMA48
> > status=51 error=40 LBA=374468863
> [...]
>
> Replace the hard drive. Every modern hard drive keeps extra space available
> to "remap" bad sectors. This happens magicall
Hello,
As a last resort, you could also try:
atacontrol reinit ata6
and try reattaching again
Thank you Manolis - you have been more than patient with me!
Unfortunately, the result is still the same. OK. I am going to ask our
hosting company to replace the drive. Again, many thanks for yo
Zbigniew Szalbot wrote:
Hello one last time,
Manolis Kiagias:
Ok, ad12 is missing, so it seems it was detached but not reattached.
try again:
atacontrol attach ata6
$ sudo atacontrol attach ata6
atacontrol: ioctl(IOCATAATTACH): File exists
Thank you all for a lot of suggestions!
Zbignie
Hello one last time,
Manolis Kiagias:
Ok, ad12 is missing, so it seems it was detached but not reattached.
try again:
atacontrol attach ata6
$ sudo atacontrol attach ata6
atacontrol: ioctl(IOCATAATTACH): File exists
Thank you all for a lot of suggestions!
Zbigniew Szalbot
smime.p7s
Des
Zbigniew Szalbot wrote:
Hello,
Manolis Kiagias:
Try
atacontrol status ar0
ar0: ATA RAID1 status: DEGRADED
subdisks:
0 ad10 ONLINE
1 MISSING
Since you haven't actually removed/replaced ad12 you may simply have
to continue with:
atacontrol rebuild ar0
I'll try it now. Thanks
Hello,
Manolis Kiagias:
Try
atacontrol status ar0
Since you haven't actually removed/replaced ad12 you may simply have to
continue with:
atacontrol rebuild ar0
atacontrol rebuild ar0
atacontrol: ioctl(IOCATARAIDREBUILD): Input/output error
So it looks like it cannot be done?
Zbigniew S
Hello,
Manolis Kiagias:
Try
atacontrol status ar0
ar0: ATA RAID1 status: DEGRADED
subdisks:
0 ad10 ONLINE
1 MISSING
Since you haven't actually removed/replaced ad12 you may simply have to
continue with:
atacontrol rebuild ar0
I'll try it now. Thanks!
Zbigniew Szalbot
smi
Zbigniew Szalbot wrote:
Hi Manolis,
Yes, it is ata6
Give it a try, if the problem is serious enough, it will probably not
even finish rebuild :(
Detaching and ataching went well but when I issued
atacontrol addspare ar0 ad12
it said
atacontrol: ioctl(IOCATARAIDADDSPARE): Device busy
I am n
Hi Manolis,
Yes, it is ata6
Give it a try, if the problem is serious enough, it will probably not
even finish rebuild :(
Detaching and ataching went well but when I issued
atacontrol addspare ar0 ad12
it said
atacontrol: ioctl(IOCATARAIDADDSPARE): Device busy
I am not sure if that means I s
(Write errors is however usually a strong indication that the drive should
be replaced ASAP.)
he got read error... but your sentence alone is true of course.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/free
Zbigniew Szalbot wrote:
Hello Manolis,
I understand you are using the ataraid (ar) driver. I always use
gmirror, but it seems they pointed you to the right place in the
handbook.
Look at section 18.4.3 - you would probably need to do something like:
# atacontrol list
ATA channel 6:
Mas
On Mon, Jun 16, 2008 at 04:41:15PM +0200, Wojciech Puchar wrote:
> >
> > Replace the hard drive. Every modern hard drive keeps extra space available
> > to "remap" bad sectors. This happens magically behind the scenes without
> > you ever knowing about it. Once you've hit "uncorrectable" errors,
Hello Manolis,
I understand you are using the ataraid (ar) driver. I always use
gmirror, but it seems they pointed you to the right place in the handbook.
Look at section 18.4.3 - you would probably need to do something like:
# atacontrol list
ATA channel 6:
Master: ad12 Serial ATA v1.0
Replace the hard drive. Every modern hard drive keeps extra space available
to "remap" bad sectors. This happens magically behind the scenes without
you ever knowing about it. Once you've hit "uncorrectable" errors, it means
no. usually it means that there was an error when writing that sect
Zbigniew Szalbot wrote:
Dear all,
Bill Moran:
My understanding is that RAID 1 no longer works because of this
error. There is a bad sector on HD (Offline uncorrectable sectors)
and the best we can do is replace the drive? Does it make sense to
try to turn RAID 1 on ignoring this error (however
Dear all,
Bill Moran:
My understanding is that RAID 1 no longer works because of this
error. There is a bad sector on HD (Offline uncorrectable sectors)
and the best we can do is replace the drive? Does it make sense to
try to turn RAID 1 on ignoring this error (however, this is done in
BIOS so
In response to Zbigniew Szalbot <[EMAIL PROTECTED]>:
>
> A couple of days ago smartd let me know about a disk problem.
>
> Jun 14 01:13:38 relay kernel: ad12: FAILURE - READ_DMA48
> status=51 error=40 LBA=374468863
> Jun 14 01:13:38 relay kernel: ar0: WARNING - mirror protection lost.
> RAID1 a
Hello,
I'd like to ask your advice. We have RAID 1 / SATA turned on in BIOS.
A couple of days ago smartd let me know about a disk problem.
Jun 14 01:13:38 relay kernel: ad12: FAILURE - READ_DMA48
status=51 error=40 LBA=374468863
Jun 14 01:13:38 relay kernel: ar0: WARNING - mirror protection lo
On Sat, Feb 16, 2008 at 07:30:37PM +0100, Peter Boosten wrote:
> Brian A. Seklecki wrote:
>> On Sat, 2008-02-16 at 17:59 +0100, Peter Boosten wrote:
>>> Hi all,
>>>
>>> Just found these messages in my logfile. Is it something to worry about?
>>> I've never seen them before upgrading to 6.3.
>>>
>
On Sat, 16 Feb 2008, Peter Boosten wrote:
Brian, thanks for your answer (and sugggestion).
Isn't a drive supposed to mark a bad sector as bad and ignore it (that is:
They ship with a certain number of unallocated sectors to reassign failed
ones to (I dont think ATA/IDE disks have a way to as
Brian A. Seklecki wrote:
On Sat, 2008-02-16 at 17:59 +0100, Peter Boosten wrote:
Hi all,
Just found these messages in my logfile. Is it something to worry about?
I've never seen them before upgrading to 6.3.
ra kernel: ad0: TIMEOUT - READ_DMA48 retrying (1 retry left) LBA=281550271
ra kernel:
On Sat, 2008-02-16 at 17:59 +0100, Peter Boosten wrote:
> Hi all,
>
> Just found these messages in my logfile. Is it something to worry about?
> I've never seen them before upgrading to 6.3.
>
> ra kernel: ad0: TIMEOUT - READ_DMA48 retrying (1 retry left) LBA=281550271
> ra kernel: ad0: FAILURE
Hi all,
Just found these messages in my logfile. Is it something to worry about?
I've never seen them before upgrading to 6.3.
ra kernel: ad0: TIMEOUT - READ_DMA48 retrying (1 retry left) LBA=281550271
ra kernel: ad0: FAILURE - READ_DMA48 status=51
error=4 LBA=281550271
ra kernel: g_vfs_done():
On Tue, Aug 21, 2007 at 01:04:38AM +0200, Wojciech Puchar wrote:
> ad4: FAILURE - READ_DMA48 status=51
> error=40 LBA=465628608
> g_vfs_done():ad4a[READ(offset=238401650688, length=638976)]error = 5
>
> how can i find (UFS2) what file uses that block?
[I took the liberty to change the subject fo
ad4: FAILURE - READ_DMA48 status=51
error=40 LBA=465628608
g_vfs_done():ad4a[READ(offset=238401650688, length=638976)]error = 5
how can i find (UFS2) what file uses that block?
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/
"Grant Peel" <[EMAIL PROTECTED]> writes:
> Is there any way to figure out the files that are not being read using the
> DUMP error output below?
>
> DUMP: read error from /dev/da0s1g: Input/output error: [block 42718592]:
> count=8192
> DUMP: read error from /dev/da0s1g: Input/output error:
Is there any way to figure out the files that are not being read using the DUMP
error output below?
DUMP: read error from /dev/da0s1g: Input/output error: [block 42718592]:
count=8192
DUMP: read error from /dev/da0s1g: Input/output error: [sector 42718594]:
count=512
DUMP: read error from
After much revision I finally have a tool that does a pretty good job
of identifying the usage of an LBA. Its not perfect, but its
normally only used with a disk with a bad sector. It no longer needs
the complete source distribution but can be built from the normal
libraries. It has been
On Tue, 3 Jan 2006 12:25 pm, Gayn Winters wrote:
> > [mailto:[EMAIL PROTECTED] On Behalf Of
> > Russell J. Wood
> > Sent: Monday, January 02, 2006 3:54 PM
> > To: freebsd-questions@freebsd.org
> > Subject: Re: Disk error messages (ad0: HARD READ ERROR blk#
> >
> [mailto:[EMAIL PROTECTED] On Behalf Of
> Russell J. Wood
> Sent: Monday, January 02, 2006 3:54 PM
> To: freebsd-questions@freebsd.org
> Subject: Re: Disk error messages (ad0: HARD READ ERROR blk# xx)
>
>
> On Mon, Jan 02, 2006 at 11:15:08PM +, [EMAIL PROTEC
On Mon, Jan 02, 2006 at 11:15:08PM +, [EMAIL PROTECTED] wrote:
> Hi there,
>
> On my screen, there were messages like the followings comeing up. I have to
> reboot mutiple times to get it boot up normally. Does this mean I have to
> replace the disk which is a relatively new disk (1-2 years)
On Monday 02 January 2006 02:15 pm, [EMAIL PROTECTED] wrote:
> Hi there,
>
> On my screen, there were messages like the followings comeing up. I have to
> reboot mutiple times to get it boot up normally. Does this mean I have to
> replace the disk which is a relatively new disk (1-2 years)? Any sim
Hi there,
On my screen, there were messages like the followings comeing up. I have to
reboot mutiple times to get it boot up normally. Does this mean I have to
replace the disk which is a relatively new disk (1-2 years)? Any simple way to
fix it and to avoid the time consuming task?
ad0: 3920
D]> wrote:
> I am sure there is an easy solution to this but here
> is my problem, and it is driving me nuts.
>
> The error message on boot is "Non-system disk or
> disk
> error". I only get this message if I do a warm
> reboot
> with no power off. If I halt
I am sure there is an easy solution to this but here
is my problem, and it is driving me nuts.
The error message on boot is "Non-system disk or disk
error". I only get this message if I do a warm reboot
with no power off. If I halt the system and power off
and restart it boot
hi all...
suddenly today out of nowhere this happens (log below) and now i get
vchkpw core dumps every few minutes or so. vchkpw is authorization module
for vpopmail... does this mean the disk where vpopmail lives - ad2 - is
already craping up?! thanks...
here is the log:
Aug 31 22:53:33 c
eciated
The question isn't completely clear, but I think the FAQ entry for
"How do I move my system over to my huge new disk?" is probably what
you're looking for.
http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/disks.html#NEW-HUGE-DISK
>
> I cut and pasted Aftabs&#x
Hi all,
I am a FreeBSD newbie... would like to know more about backing up the whole
FreeBSD system to a new hard disk.
What is the most convenient method of backing up to a new harddisk?
any pointers appreciated
I cut and pasted Aftabs' reply to Disk Error thread ...
Thanks in ad
Doug Hardie wrote:
I doubt that its dying. There is only one bad sector. The drive is in
constant use. Its ran at 100% for almost 12 hours while copying the
files and no errors were detected. Its always the same sector with the
error.
Just as a note, hard drives now come with a number of "sp
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] Behalf Of Doug Hardie
> Sent: Sunday, March 06, 2005 10:24 PM
> To: Aftab Jahan Subedar
> Cc: FreeBSD Questions
> Subject: Re: Disk Error
>
>
> I doubt that its dying. There is onl
I doubt that its dying. There is only one bad sector. The drive is in
constant use. Its ran at 100% for almost 12 hours while copying the
files and no errors were detected. Its always the same sector with the
error.
On Mar 7, 2005, at 09:54, Aftab Jahan Subedar wrote:
ASAP
1. fsck -y
2. tun
ASAP
1. fsck -y
2. tunefs ( enable softupdate)
3. backup to new hard disk
4. remove this faulty hard disk
Your hard disk is dyeing .
Doug Hardie wrote:
I have been getting the following disk errors consistently for the
last month.
ad2s1e: hard error reading fsbn 6934399 of 3467168-3467295 (ad2s1
I have been getting the following disk errors consistently for the last
month.
ad2s1e: hard error reading fsbn 6934399 of 3467168-3467295 (ad2s1 bn
6934399; cn 431 tn 164 sn 52) status=59 error=40
spec_getpages:(#ad/0x20014) I/O read failure: (error=5) bp 0xc5678f94
vp 0xcb5f3a80
Hi,
I have a scsi controller:
iir0: mem 0xfc2f-0xfc2f3fff irq 20 at
device 8.0 on pci4
Yestarday I have taken this messages from my dmesg output:
iir0: SCSI-B, ID 0: last status 0x0107. I/O status: SELECTION_TIMEOUT
iir0: SCSI-B, ID 0: Check cables, termination, termpower, LVDS op
Hi all,
I am completely stumped by this one. I have a new MSI 1u P1-1000 server:
2.4GHz P4, 1GB Ram, with a 40GB IDE (38166MB [77545/16/63])
hard drive on the primary master channel.
Here's the problem, I can install 4.9-Stable, but when I finish and
reboot the machine the bios reports
On Tuesday, 23 September 2003 at 11:21:49 -0700, John Fox wrote:
> Hello,
>
> Three IDE drives multiplexed together to make one large "partition"
> (for mounting as /usr/local).
>
> We were messing with hardware in the box and when we rebooted
> vinum spat out errors about defective objects and the
On Tuesday, 23 September 2003 at 11:29:44 -0700, John Fox wrote:
> Maybe it'll help if I give some more comprehensive information:
>
> vinum -> l
> 3 drives:
> D ide0e State: up Device /dev/ad0s1e Avail: 0/8063 MB (0%)
> D ide2e State: up Device /dev
Maybe it'll help if I give some more comprehensive information:
vinum -> l
3 drives:
D ide0e State: up Device /dev/ad0s1e Avail: 0/8063 MB (0%)
D ide2e State: up Device /dev/ad2s1e Avail: 0/4031 MB (0%)
D ide3e State: up D
Hello,
Three IDE drives multiplexed together to make one large "partition"
(for mounting as /usr/local).
We were messing with hardware in the box and when we rebooted
vinum spat out errors about defective objects and the boot
came to a halt. We figured we had left something loose or
unplugged on
T)
> >From: manee <[EMAIL PROTECTED]>
> >Subject: Re: hard disk error , run fsck manually
> >To: David Wolfskill <[EMAIL PROTECTED]>
> >Cc: [EMAIL PROTECTED]
>
>
> >i got , after running fsck -p
>
> >THE FOLLOWING FILE SYSTEM HAD AN UNEXPEC
--- Alex Zivenko <[EMAIL PROTECTED]> wrote:
> You need just run fsck. See the man page. I had this
> problem too. Only yesterday. All was fixed with
> fsck, I just gived root password and logged in in
> single user mode. Then I just runned fsck with some
> params.
>
thank you for your time. but
hi sirs,
thanks for your time indeed.
--- David Wolfskill <[EMAIL PROTECTED]> wrote:
> Reboot your system.
>
> During the 10-second "spinning propeller"
> count-down, press the space
> bar once. You should see the prompt
>
> boot>
>
>
> At that point, type
>
> boot -s
>
> and press "
On Saturday 28 June 2003 07:17 pm, manee wrote:
> hi sirs,
>
> i face problem of hard disk error because of the power
> downed during using the machine.
>
> once the power is coming, my machine stuck at
>
> file system is still dirty please run fsck manually.
>
> the
hi sirs,
i face problem of hard disk error because of the power
downed during using the machine.
once the power is coming, my machine stuck at
file system is still dirty please run fsck manually.
the partion that is dirty is /dev/ad0s2g, a home
partion one. i did run fsck /dev/ad0s2g several
Physician heal thyself...
I recreated my install disks and the problem disappeared...
Will
--- "W. J. Williams" <[EMAIL PROTECTED]> wrote:
> I keep getting the following error when trying to install FreeBSD 4.7
>
>
>
> ad0: 9773MB [19857/16/63] at ata0-master UDMA 33
> Mounting root from
I keep getting the following error when trying to install FreeBSD 4.7
ad0: 9773MB [19857/16/63] at ata0-master UDMA 33
Mounting root from ufs:/dev/md0c
md0s4: slice extends beyond end of disk: truncating from 5 to 8640
sectors
.
after this message the system just hangs.
I have low
Disk error 0x10 (lba=0x48)
Disk error 0x10 (lba=0x48)
No /boot/loader
>>FreeBSD/i386 BOOT
Default: 0:fd(0,a)/kernel
Boot:
Disk error 0x10 (lba=0x48)
No /
Hello all.
Does anybody know how can I figure out what "status=51 error=04" mean?
dmesg reported that regarding an (obviously) "bad" disk (due to power outage).
I didn't find anywhere in the Net a look-up table or something similar that
which possibly could give me a *precise*
78 matches
Mail list logo
