rAID 1
Erik P. Olsen
erik at epo.dk
Wed Dec 12 21:41:22 UTC 2007
Please keep the original thread instead of creating new threads for the same issue.
--
Erik.
tony.chamberlain at lemko.com wrote:
> Here's a question.
> If it weren't correct, when you
> boot would it stop at the grub prompt?
>
> -----Original Message-----
>
>
> Message: 3
> Date: Tue, 11 Dec 2007 08:05:13 -0800
> From: Sean Bruno <sean.bruno at dsl-only.net>
> Subject: Re: raid1
> To: For users of Fedora <fedora-list at redhat.com>
> Message-ID: <1197389113.32026.1.camel at home-desk>
> Content-Type: text/plain
>
>
> On Tue, 2007-12-11 at 12:49 +0000, tony.chamberlain at lemko.com wrote:
> > This is of course a more recent installation.
> >
> > I just found that in /etc/cron.daily there is a file with a script
> > (directory name changed for confidentiality)
> >
> > cd /a/b/c/d
> > find . -name '*log*' -exec rm -f {} \;
> >
> > So if there is no /a/b/c/d it will stay in whatever directory it is in
> > (probably root). That is why like initlog, login_pam,so etc.
> > have been removed. I just don't know why the stuff in cron.daily
> > ran in the afternoon when in /etc/crontabit is set to go at like
> > 4:00 AM and this was installed much after 4:00 AM, so the
> > cron.daily really shouldn't have run until the next day.
> >
> >
> > Here is the output of the raid commands:
> >
> > /dev/md0:
> > Version : 00.90.01
> > Creation Time : Mon Dec 3 11:12:48 2007
> > Raid Level : raid1
> > Array Size : 104320 (101.89 MiB 106.82 MB)
> > Device Size : 104320 (101.89 MiB 106.82 MB)
> > Raid Devices : 2
> > Total Devices : 2
> > Preferred Minor : 0
> > Persistence : Superblock is persistent
> >
> > Update Time : Mon Dec 10 16:30:59 2007
> > State : clean
> > Active Devices : 2
> > Working Devices : 2
> > Failed Devices : 0
> > Spare Devices : 0
> >
> > UUID : 45d9ab4a:fc74db66:3a595fea:7e2afbdd
> > Events : 0.335920
> >
> > Number Major Minor RaidDevice State
> > 0 8 1 0 active
> > sync /dev/sda1
> > 1 8 17 1 active
> > sync /dev/sdb1
> >
> >
> > /dev/md1:
> > Version : 00.90.01
> > Creation Time : Mon Dec 10 09:58:53 2007
> > Raid Level : raid1
> > Array Size : 69537280 (66.32 GiB 71.21 GB)
> > Device Size : 69537280 (66.32 GiB 71.21 GB)
> > Raid Devices : 2
> > Total Devices : 2
> > Preferred Minor : 1
> > Persistence : Superblock is persistent
> >
> > Update Time : Tue Dec 11 06:36:51 2007
> > State : clean
> > Active Devices : 2
> > Working Devices : 2
> > Failed Devices : 0
> > Spare Devices : 0
> >
> > UUID : c44f476d:a1f38eb3:b74e1d2d:66efa904
> > Events : 0.21479
> >
> > Number Major Minor RaidDevice State
> > 0 8 2 0 active
> > sync /dev/sda2
> > 1 8 18 1 active
> > sync /dev/sdb2
> >
> >
> >
> >
> >
> >
> > ------------------------------
> >
> > Message: 5
> > Date: Mon, 10 Dec 2007 07:19:55 -0800
> > From: Sean Bruno <sean.bruno at dsl-only.net>
> > Subject: Re: Raid 1
> > To: For users of Fedora <fedora-list at redhat.com>
> > Message-ID: <1197299995.25236.3.camel at home-desk>
> > Content-Type: text/plain
> >
> >
> > On Mon, 2007-12-10 at 12:45 +0000, tony.chamberlain at lemko.com wrote:
> > >
> > >
> > > We put Raid 1 (software) on an IBM server. I installed some software
> > > and made sure everything
> > > worked. Then we realized we needed to set up grub so the machine
> > > would boot from either disk.
> > > So under Linux Rescue we went into grub and did
> > >
> > > device (hd0) /dev/sda
> > > root (hd0,0)
> > > setup (hd0)
> > >
> > > device (hd1) /dev/sdb
> > > root (hd1,0)
> > > setup (hd1)
> > >
> > > But then when we booted, everything failed. I noticed a commone
> > > message "initlog not found" so I looked on another machine and
> > > foiund it under /sbin but not on this one. So I copied it to /sbin
> > > and
> > > rebooted. It got a lot farther this time, but then got stuck on not
> > > being
> > > able to find a default theme.
> > >
> > > I also noticed that linux rescue puts the linux under /mnt/sysimage
> > > (so /etc is /mnt/sysimage/etc, /home is /mnt/sysimage/home, etc)
> > > but in addition to those there was still a /etc, /home, etc. I
> > > suppose
> > > one was the mirrored disk.
> > >
> > > So it sounds like we might not have done something correctly. Anyone
> > > have any idea? We did set up the whole raid system correctly during
> > > Linux installation on a different machine, and then used that
> > > anaconda-ks.cfg
> > > file for this one (removing the "#"'s where the raid stuff was
> > > commented out
> > > in the config file).
> >
> > Can you post the output of "mdadm --detail /dev/mdX" for each raid
> > device on your machine? It almost sounds like the RAID isn't working
> > for you.
> >
> > Sean
>
> So, does your system boot at all? Or does it fail when you try to boot
> off of one drive vs. another?
>
> Sean
>
>
>
> -
>
More information about the fedora-list
mailing list