Re: Drive Failure or User Error?

2006-08-21 Thread Jason Morgan
On Sun, Aug 20, 2006 at 03:22:45PM -0400, Lowell Gilbert wrote: > Jason Morgan <[EMAIL PROTECTED]> writes: > > > I was setting up a new server (6.1 i386 STABLE) - more specifically, I > > was mirroring the functioning server drive - when I suddenly got this: > > > > ad0 FAILURE - READ_DMA48 status

Re: Drive Failure or User Error?

2006-08-20 Thread Lowell Gilbert
Jason Morgan <[EMAIL PROTECTED]> writes: > I was setting up a new server (6.1 i386 STABLE) - more specifically, I > was mirroring the functioning server drive - when I suddenly got this: > > ad0 FAILURE - READ_DMA48 status=51 > error=40 LBA=611703808 > GEOM_MIRROR: Request failed (error=5). ad0[RE

Re: Drive Failure

2002-12-19 Thread Jerry McAllister
> > > > I dont know what this option means - does this matter? > > > > > > -B Install the `boot0' boot manager. This option causes MBR > > > code to > > > be replaced, without affecting the embedded slice table. > > > > Sounds like just what you said you wanted. > > > >

Re: Drive Failure

2002-12-19 Thread Noah Garrett Wallach
Sorry if this was verified before but this output from the boot0cfg command - looks okay right? typhoon# boot0cfg -B -v -b /mnt/ad2-root/boot/boot0 /dev/ad2 # flag start chs type end chs offset size 1 0x80 0: 1: 1 0xa5464: 15:63 63150136497

Re: Drive Failure

2002-12-19 Thread Noah Garrett Wallach
> > I dont know what this option means - does this matter? > > > > -B Install the `boot0' boot manager. This option causes MBR > > code to > > be replaced, without affecting the embedded slice table. > > Sounds like just what you said you wanted. Hi Jerry, What does "wit

Re: Drive Failure

2002-12-17 Thread Jerry McAllister
> > also how do I ID the second drive? Am I doing this correcly? > I don't know what you mean by ID-ing the second drive. jerry > > typhoon# fdisk -sv ad2 > /dev/ad2: 148945 cyl 16 hd 63 sec > PartStartSize Type Flags >1: 63 150136497 0xa5 0x80 > typhoon#

Re: Drive Failure

2002-12-17 Thread Jerry McAllister
> > > Try mounting and reading some of the stuff from that disk and > > see if you can get to it. > > > > Then try boot0cfg(8) > > > I dont know what this option means - does this matter? > > -B Install the `boot0' boot manager. This option causes MBR > code to > be

Re: Drive Failure

2002-12-17 Thread Jerry McAllister
> > So Jerry, > > > this is the proper output then? > > typhoon# fdisk -I -B -b /mnt/ad2-root/boot/boot0 ad2 > *** Working on device /dev/ad2 *** > typhoon# > > > some mount details seems relevant > > typhoon# fdisk -I -B -b /mnt/ad2-root/boot/boot0 ad2 I think you want -b /boot/boo

Re: Drive Failure

2002-12-17 Thread Noah Garrett Wallach
So Jerry, this is the proper output then? typhoon# fdisk -I -B -b /mnt/ad2-root/boot/boot0 ad2 *** Working on device /dev/ad2 *** typhoon# some mount details seems relevant typhoon# fdisk -I -B -b /mnt/ad2-root/boot/boot0 ad2 typhoon# mount /dev/ad0s1a on / (ufs, local) /dev/ad0s1

Re: Drive Failure

2002-12-17 Thread Jerry McAllister
> Hi, > > my current system drive is having difficulties some files that were > in great shape are now EBADF. This drive is known as ad0 (yup IDE) > > So I installed a new drive and have moved all files over to it. The > new drive is known as ad2. > > Is my fdisk usage here proper? Is this th