On Tue, 30 May 2000, Michael Robinton wrote:
> The usual problem is that you are booting with a kernel that has not had
> rdev done directly on the kernel -- lilo won't do it for you when you use
> initrd or boot from an image file.
Yeah, I suspected that too, only to discover that the
> -Original Message-
> From: Dave Wreski [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, May 30, 2000 9:41 PM
> To: [EMAIL PROTECTED]
> Subject: Installing another SCSI controller
>
> Hi all. I've got raid0 working fine between three 9G scsi disks. I'd
> like to add an aha152x to drive a CD
>
> I am currently having problems mounting my root file system that
> is set up with RAID-1. The initrd image I am using conatins all the raid
> tools, and successfully starts all the raid devices, but then I get the
> familiar message "Kernel panic: VFS: Unable to mount root fs on 00:00".
Hi all. I've got raid0 working fine between three 9G scsi disks. I'd
like to add an aha152x to drive a CDRW. However, support for it is
compiled directly in the kernel, and it the driver gets loaded before the
aha294x driver controlling the hard disks.
I knew it would be too easy to simply ad
Hello,
I am currently having problems mounting my root file system that
is set up with RAID-1. The initrd image I am using conatins all the raid
tools, and successfully starts all the raid devices, but then I get the
familiar message "Kernel panic: VFS: Unable to mount root fs on
If you put / and /boot on raid then probably your swap
is also on raid. Does having swap on raid have any
significant impact on performance?
J.
--- Holger Kiehl <[EMAIL PROTECTED]> wrote:
> > After doing more reading and lurking on this
> maillist, I'm starting to get
> > the idea that hav
> this brings me back to my original post in this thread. I get an
> error when I try to specify the "real" device and the MBR does not
> get written. do I have to stop the raid for the boot partition and
> mount the partitions as individual sdx ? I would think that if I
> tell lilo to write the
[Wishart, Aaron M. (James Tower)]
> I have a raid5 file system consisting of 8, 9-gig quantum scsi drives (scsi
> id 0-6, 8). The drive with the scsi id of 1 failed. I replaced the drive
> and ran "raidhotadd /dev/scb /dev/md0" It appeared to run so I left for the
> weekend. When I came in thi
[Peter Hircock]
> d) raidhotadd /dev/md2 /dev/hdc3
> Don't have raidhot add.
raidhotadd is a symlink to raidstart that gets created when you do
the "make install". Might wanna check you've done that and then
check that the /sbin directory is in your path (or wherever you
installed the raidtools)
Hello
I had a drive failure on the second drive in a mirrored pair. After
rebooting the system ( and correcting the jumper settings). The drive came
back up fine. The boot and swap partitons came up fine, but the root
partition noticed the drives were out of sync and only used the f
> Luca Berra wrote:
> >
> > get the latest lilo from metalab, it understands raid
>
> But it does not really work.
> If I do a lilo with boot=/dev/md0 in my lilo.conf it does write to
> both disks. But booting from the second disk in the array is not
> possible. I always get "error: 0x80" or sim
I have a raid5 file system consisting of 8, 9-gig quantum scsi drives (scsi
id 0-6, 8). The drive with the scsi id of 1 failed. I replaced the drive
and ran "raidhotadd /dev/scb /dev/md0" It appeared to run so I left for the
weekend. When I came in this morning the syslogd was using 75% of the
> If I do a lilo with boot=/dev/md0 in my lilo.conf it does write to both
> disks. But booting from the second disk in the array is not possible.
> I always get "error: 0x80" or similar right after the LILO prompt.
> Any hints?
I find that `default=linux' (or whatever the actual default is)
and r
Luca Berra wrote:
>
> get the latest lilo from metalab, it understands raid
But it does not really work.
If I do a lilo with boot=/dev/md0 in my lilo.conf it does write to both
disks. But booting from the second disk in the array is not possible.
I always get "error: 0x80" or similar right after
What is the version and can't tell me where exactly the URL?
-Original Message-
From: Luca Berra [SMTP:[EMAIL PROTECTED]]
Sent: Tuesday, May 30, 2000 9:18 AM
To: [EMAIL PROTECTED]
Subject:Re: boot redundancy - writing lilo to each drive?
get the latest lilo from metalab,
It worked now after I re-build the initrd image with e following command:
mkinitrd --with=raid1 -f /boot/initrd-2.2.5-22.img 2.2.5-22
Now I want to move the root to the new raid device (/dev/md0). When rebooting, it
stopped at
LI
Here is the configuration:
1) Two disks with 4Gb of each.
2) /
get the latest lilo from metalab, it understands raid
L.
On Tue, May 30, 2000 at 03:22:29AM -0700, Gavin Clark wrote:
> Hi, I have a raid level 1 on 2 scsi drives and an IDE drive.
> I'm trying to set MBR on all my drives so if the first one goes down the
> system will still boot.
--
Luca Berra
Hi, I have a raid level 1 on 2 scsi drives and an IDE drive.
I'm trying to set MBR on all my drives so if the first one goes down the
system will still boot.
I followed advice from this list's archive and set up a lilo.conf file for
each drive:
lilo.conf.hda
lilo.conf.sda
lilo.conf.sdb
when I tr
Hi Christian,
On Tue, 30 May 2000, Christian [iso-8859-1] Müller wrote:
> Edward Schernau wrote:
> > What kinds of disks are you using? I'm seeing occasional
> > corruption on my Seagate 20MB ATA66 barracuda, and have
> > not ruled out the possibility of unstable ATA66 mode.
>
> I am using the
Edward Schernau wrote:
> What kinds of disks are you using? I'm seeing occasional
> corruption on my Seagate 20MB ATA66 barracuda, and have
> not ruled out the possibility of unstable ATA66 mode.
Hi Edward!
I am using these U160-SCSI-disks together with an Adaptec
39160-controller - not IDE:
20 matches
Mail list logo
