On Fri, 2003-07-25 at 07:47, Leonard den Ottolander wrote:
> Oops. Yes, slipped my mind for a sec ;-). Probably not a second
> machine there so you could have setup mutual serial consoles.
Not at the moment, no. It's colo'd at an ISP, and if I need to ever
work on it, it has to be disconnected
Hi Ricky,
> Since the system is remote, I'm not sure how to do that without looking
> at the syslogs.
Oops. Yes, slipped my mind for a sec ;-). Probably not a second
machine there so you could have setup mutual serial consoles.
> No problem. I'll see what happens with editing the linuxrc scri
On Wed, 2003-07-23 at 23:39, Peter Kiem wrote:
> VMWare DOES support emulating IDE drives. Check out
> http://www.vmware.com/support/ws4/doc/new_guest_steps_ws.html
>
> If you select "custom" in configuration you can specify IDE drives instead
> of the default SCSI drives.
VMware Workstation doe
On Thu, 2003-07-24 at 08:16, Leonard den Ottolander wrote:
> Yeah, but I think you already compared the two images and came to the
> conclusion that they are identical. In that case creating a ramdisk by
> hand does not solve anything. O yes, I did suggest you edited linuxrc
> in the ramdisk to
Hi Ricky,
> The last recommendation I noticed was to try and create a custom ramdisk
> to force it to load the raid1 module.
Yeah, but I think you already compared the two images and came to the
conclusion that they are identical. In that case creating a ramdisk by
hand does not solve anything
Just a side note
> I've recreated the situation on a VMware virtual machine I set up. The
> only difference is that I have no control over the type of hard-drives
> are "emulated", per se, as it only allows SCSI. The real machine has
VMWare DOES support emulating IDE drives. Check out
http://w
On Wed, 2003-07-23 at 10:20, Leonard den Ottolander wrote:
> I am sorry nobody else jumps in. Problem with waiting such a long time
> with your replies is it makes that I already forgot what the precise
> problem was, what you have already tried to solve it, and what I did
> recommend you to tr
Hi Ricky,
> :( Seems like I'm talking to myself...
I am sorry nobody else jumps in. Problem with waiting such a long time
with your replies is it makes that I already forgot what the precise
problem was, what you have already tried to solve it, and what I did
recommend you to try.
> BTW: I
On Tue, 2003-07-22 at 10:07, Ricky Boone wrote:
> Haven't seen a response from anyone concerning this issue, so ... *bump* :)
:( Seems like I'm talking to myself...
> Dunno... it really looks like the RAM-disk is the answer...
BTW: I've tried the following:
# mkinitrd --preload raid1 --wit
Haven't seen a response from anyone concerning this issue, so ... *bump* :)
I am still quite a n00b when it comes to the kernel, but someone mentioned
making a new RAM-disk to include the RAID-1 module using mkinitrd. Since
the machine in question is a remote box, screwing around with something
On Thu, 2003-06-26 at 15:39, Leonard den Ottolander wrote:
> What happens if you run raidstart /dev/md0 by hand? Getting the same errors?
# raidstart /dev/md0
/dev/md0: File exists
--
Ricky Boone <[EMAIL PROTECTED]>
Planetfurry.com
--
redhat-list mailing list
unsubscribe mailto:[EMAIL PROTEC
My apologies for the delay. Real life and everything, ya know... :|
On Fri, 2003-07-04 at 18:11, Leonard den Ottolander wrote:
> That looks like the initrd.img is usable - although I don't know what
> "raidautorun" is, can you locate this script in the filesystem?
No, I'm not sure where it is.
Hi Ricky,
Missed this post, so one more comment on it:
> > Not sure, but I would think it's not a problem, since you are running
> > on a live file system, so there are probably open files. Maybe if you'ld
> > remount / ro the file system is reported as clean.
>
> I've tried forcing an fsck on
Hi Ricky,
> Both 2.4.9 and 2.4.20 have the same linuxrc script. The first module
> that is loaded is the raid1 module (insmod /lib/raid1.o). Later it
> starts the raid on the partitions (raidautorun /dev/md0).
That looks like the initrd.img is usable - although I don't know what
"raidautorun"
On Fri, 2003-07-04 at 15:20, Leonard den Ottolander wrote:
> You could check if the initrd for 2.4.20 actually loads the appropriate raid
> modules (compare it with the contents of the old one).
Both 2.4.9 and 2.4.20 have the same linuxrc script. The first module
that is loaded is the raid1 mod
Hi Ricky,
> Okay. lilo.conf uses an initrd image for both the 2.4.9-34 kernel, as well as
> the 2.4.20-18.7 copy.
You could check if the initrd for 2.4.20 actually loads the appropriate raid
modules (compare it with the contents of the old one).
You should know the initrd.img is a gzipped fi
Hi again,
> Any tips as to what I should
> look for when recreating the image, if necessary?
Include the appropriate modules. man mkinitrd.
Bye,
Leonard.
--
How clean is a war when you shoot around nukelar waste?
Stop the use of depleted uranium ammo!
End all weapons of mass destruction.
--
> I'm going to try arranging the directives for 2.4.20-18.7 in the same
> order as 2.4.9-34.
Rats. It didn't work. :| Same errors as before.
I'm going to check out the man page for mkinitrd, but it seems like there
is already one in /boot for the newer kernel. Any tips as to what I should
loo
> Good question, because it probably answers why you are having problems
> in the first place.
>
> Since you are using / raid you need a initrd.img that holds and loads
> the
> (new) raid modules before / is mounted. Check your lilo.conf or
> grub.conf to verify that you did use an initrd before.
Hi Ricky,
> > What happens if you run raidstart /dev/md1 by hand? Getting the same errors?
>
> Can I do this with the / partition already mounted?
Good question, because it probably answers why you are having problems in the
first place.
Since you are using / raid you need a initrd.img that
On Thu, 2003-06-26 at 15:39, Leonard den Ottolander wrote:
> What happens if you run raidstart /dev/md1 by hand? Getting the same errors?
Can I do this with the / partition already mounted?
BTW: I've updated nearly all rpm's available on up2date, including the
kernel. I'm still getting the fol
> Before you upgrade the kernel, did you upgrade raidtools to the latest
> version? Plus did you do all the other updates?
The raidtools RPM that's installed is version 0.90-24, which I'm assuming
is the latest since up2date doesn't mention it. As for all the other
updates, I'd have to say I've o
Hi Ricky,
> The system is running Red Hat Linux 7.2. I am using Software-RAID for the root
> partition (/dev/hda3 and /dev/hdd1 as /dev/md0 RAID-1), and a standard ext3
> partition for /boot. I am also using kernel-2.4.9-34, but would like to
> upgrade as soon as possible.
Before you upgrade t
23 matches
Mail list logo
