Hello all,

All the previous postings about moving one's root file system has been
very useful. I'm trying to set up RAID on my new SMP box.  I've solved a
number of problems: how to autodetect RAID devices, added the missing raid
modules to initrd, etc.

My RAID devices are now autodetected and started on boot. So I copied my /
partition, ran lilo, etc. as follows:

mount /dev/md0 /mnt/raid
tar --one-file-system -cf - / | tar -C /mnt/raid -xvf -

changed /mnt/raid/etc/lilo.conf -> root=/dev/md0
changed /mnt/raid/etc/fstab     -> /dev/md0 / ....

mounted my boot partition under /mnt/raid/boot

lilo -r /mnt/raid -C /etc/lilo.conf

This appears to have worked correctly, as upon reboot /dev/md0 is
correctly autodetected and started, I get:

fsck: /dev/md0: clean ...
rc.sysinit: Checking root filesystem succeeded
rc.sysinit: Remounting root file-system in read-write mode succeeded

ohter file systems (not yet raid) successfully mounted

then:

atd[xxx]: Error redirecting I/O: Permission denied
atd: atd startup failed

Then, if in runlevel 5:

X starts to come up, flashes, fails, and then repeats this
indefinitely.  I can't switch virtual terminals, but I can telnet in.
df shows that /dev/md0 is mounted as /, attempting to run atd logs
the same error.  Upon shutting down, I get:

xfs: shutdown failed
atd: shutdown failed

The permission denied for atd is perplexing. I poked around a little,
and tried changing permissions on /dev/md0 to match other filesystem
devices (ie group -> disk and permissions to 640), but got the same
result.  I'm guessing that if I can solve the atd permission denied
problem, that the X problem will go away also.

Did I screw up the options on the tar copy? Everything appears to be
correct, w/correct permissions, etc. Device files must be OK, or I
wouldn't have gotten this far...

Any ideas?

BTW, I am running RH6.0, updated with most of the RedHat updates (except
Netscape and Gnome).  Thus I am running the RH 2.2.5-22smp kernel, which
upgraded fine.  I did all the neccessary mkinitrd and lilo stuff, and the
system boots fine with a non-RAID / partition.

Simon Hill ([EMAIL PROTECTED])
Operating Systems Specialist
Department of Utilities 
University of Texas

---------------------------------------------------------------------------
Send administrative requests to [EMAIL PROTECTED]

Reply via email to