* fd filesystem and RAID1
@ 2004-04-02 23:32 Ninti Systems
2004-04-05 0:58 ` Daniel Pittman
0 siblings, 1 reply; 5+ messages in thread
From: Ninti Systems @ 2004-04-02 23:32 UTC (permalink / raw)
To: RAID Linux
I've been able to do everything involved in setting up a simple RAID1
with 2 IDE disks on Slackware 9.1 except get it to actually keep working
on reboot.
I installed on one disk, built 'degraded' RAID1 devices on the second
disk, copied data, etc. I can hot add devices from the original disk to
the RAID arrays. RAID devices in /etc/fstab come up (in degraded mode)
on boot.
The problem is that hot-added devices never stick, the RAID arrays are
always degraded again on reboot.
mdadm complains of missing superblocks. I have read the man page but
can't see how to manage superblocks (create/delete) if this is even
possible.
I'm wondering if have to make the original install partitions type 'fd'
as well as those on the second disk?
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: fd filesystem and RAID1
2004-04-02 23:32 fd filesystem and RAID1 Ninti Systems
@ 2004-04-05 0:58 ` Daniel Pittman
2004-04-05 8:00 ` Ninti Systems
0 siblings, 1 reply; 5+ messages in thread
From: Daniel Pittman @ 2004-04-05 0:58 UTC (permalink / raw)
To: linux-raid
On 03 Apr 2004, Ninti Systems wrote:
> I've been able to do everything involved in setting up a simple RAID1
> with 2 IDE disks on Slackware 9.1 except get it to actually keep
> working on reboot.
>
> I installed on one disk, built 'degraded' RAID1 devices on the second
> disk, copied data, etc. I can hot add devices from the original disk
> to the RAID arrays. RAID devices in /etc/fstab come up (in degraded
> mode) on boot.
>
> The problem is that hot-added devices never stick, the RAID arrays are
> always degraded again on reboot.
>
> mdadm complains of missing superblocks. I have read the man page but
> can't see how to manage superblocks (create/delete) if this is even
> possible.
>
> I'm wondering if have to make the original install partitions type
> 'fd' as well as those on the second disk?
The kernel auto-discovery will only probe a partition that has type
'fd', so if you want both parts of the mirror to work, both need to be
type 'fd'.
Daniel
--
Democracy is ever eager for rapid progress, and the only
progress which can be rapid is progress made down hill.
-- Sir James Jeans
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: fd filesystem and RAID1
2004-04-05 0:58 ` Daniel Pittman
@ 2004-04-05 8:00 ` Ninti Systems
2004-04-05 9:08 ` Ninti Systems
0 siblings, 1 reply; 5+ messages in thread
From: Ninti Systems @ 2004-04-05 8:00 UTC (permalink / raw)
To: Daniel Pittman; +Cc: RAID Linux
Thanks for your patient replies Daniel. I'm not having a lot of luck
with RAID1 on Slackware, and will probably have to go back to RedHat9's
comfy GUI.
I have followed the instructions in your initial reply, but haven't been
able to set up even a non-root RAID device using mdadm that doesn't try
to resync on every reboot. This is with all fs types as 'fd'. The fault
lies with me of course, not your instructions. which I must be
misreading somehow.
I'm thinking of trying mkraid and using a startup script to get RAID
going. Or maybe just mirroring data to the second disk with rsync.
On Mon, 2004-04-05 at 10:28, Daniel Pittman wrote:
> On 03 Apr 2004, Ninti Systems wrote:
> > I've been able to do everything involved in setting up a simple RAID1
> > with 2 IDE disks on Slackware 9.1 except get it to actually keep
> > working on reboot.
> >
> > I installed on one disk, built 'degraded' RAID1 devices on the second
> > disk, copied data, etc. I can hot add devices from the original disk
> > to the RAID arrays. RAID devices in /etc/fstab come up (in degraded
> > mode) on boot.
> >
> > The problem is that hot-added devices never stick, the RAID arrays are
> > always degraded again on reboot.
> >
> > mdadm complains of missing superblocks. I have read the man page but
> > can't see how to manage superblocks (create/delete) if this is even
> > possible.
> >
> > I'm wondering if have to make the original install partitions type
> > 'fd' as well as those on the second disk?
>
> The kernel auto-discovery will only probe a partition that has type
> 'fd', so if you want both parts of the mirror to work, both need to be
> type 'fd'.
>
> Daniel
--
--------------------------------------
Ninti Systems: Smart IT Solutions
Michael Hall
Mobile: 0429 095 392
Ph/Fax: 08 8953 1442
Email: office at ninti dot com dot au
Web: http://ninti.com.au
--------------------------------------
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: fd filesystem and RAID1
2004-04-05 8:00 ` Ninti Systems
@ 2004-04-05 9:08 ` Ninti Systems
2004-04-05 14:48 ` Daniel Pittman
0 siblings, 1 reply; 5+ messages in thread
From: Ninti Systems @ 2004-04-05 9:08 UTC (permalink / raw)
To: Daniel Pittman; +Cc: RAID Linux
> >
> > The kernel auto-discovery will only probe a partition that has type
> > 'fd', so if you want both parts of the mirror to work, both need to be
> > type 'fd'.
I tried doing this to partitions on both IDE devices pre-install
(Slackware saw them all as md devices, install impossible), and I also
tried changing the original install disk's partitions over to 'fd' type
after copying their content to the md device (the second disk also all
'fd' type).
But whatever I do the arrays never have usable superblocks, are always
degraded and always want to resync on boot.
Thanks for all your help, but I'm starting to get over this RAID on
Slackware thing. I think I'll reconsider my distro (RedHat) or my backup
strategy (rsync).
Thanks again
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: fd filesystem and RAID1
2004-04-05 9:08 ` Ninti Systems
@ 2004-04-05 14:48 ` Daniel Pittman
0 siblings, 0 replies; 5+ messages in thread
From: Daniel Pittman @ 2004-04-05 14:48 UTC (permalink / raw)
To: office; +Cc: RAID Linux
On 05 Apr 2004, Ninti Systems wrote:
>> >
>> > The kernel auto-discovery will only probe a partition that has type
>> > 'fd', so if you want both parts of the mirror to work, both need to
>> > be type 'fd'.
>
> I tried doing this to partitions on both IDE devices pre-install
> (Slackware saw them all as md devices, install impossible), and I also
> tried changing the original install disk's partitions over to 'fd'
> type after copying their content to the md device (the second disk
> also all 'fd' type).
>
> But whatever I do the arrays never have usable superblocks, are always
> degraded and always want to resync on boot.
Hrm. I am sorry that things have proved to be such a challenge. One
thing to note, of course, is that a software RAID root file system is
much harder to use than any other partition done as software RAID.
You may have better luck by creating a couple of small partitions and
working with those as an "extra" drive, until you resolve the problems.
One final note: I found the 'mdadm' tool a *vast* improvement over the
traditional RAID tools for Linux.
> Thanks for all your help, but I'm starting to get over this RAID on
> Slackware thing. I think I'll reconsider my distro (RedHat) or my
> backup strategy (rsync).
RedHat certainly seems to offer good graphical tools for managing this
sort of thing, which can be very useful while you learn how things work.
There is nothing wrong with using a helping hand in software rather than
by email. :)
Good luck.
Daniel
--
All that you suspect about women's friendships is true. We talk about dick size.
-- Cynthia Heimel
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2004-04-05 14:48 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2004-04-02 23:32 fd filesystem and RAID1 Ninti Systems
2004-04-05 0:58 ` Daniel Pittman
2004-04-05 8:00 ` Ninti Systems
2004-04-05 9:08 ` Ninti Systems
2004-04-05 14:48 ` Daniel Pittman
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).