David M. Strang wrote:
I've read, and read, and read -- and I'm still not having ANY luck
booting completely from a raid1 device.
This is my setup...
sda1 is booting, working great. I'm attempting to transition to a
bootable raid1.
sdb1 is a 400GB partition -- it is type FD.
Disk /dev/sdb
On Sunday 27 November 2005 22:08:04, Ross Vandegrift wrote:
Well, more generally, it's used when something needs to happen before
the kernel can mount your root partiton. Sometimes this means DHCPing
for an IP and mounting an NFS drive, it often means loading kernel
modules. In your case, it me
On Sun, Nov 27, 2005 at 09:33:38PM -0500, David M. Strang wrote:
> I use CRUX (http://www.crux.nu) -- I compile my own kernel; from my breif
> exploration of initrd -- which debian has about a trillion web pages
> dedicated to raids and initrd -- the feeling / impression I had was that
> initrd
On Sunday 27 November 2005 21:20:22, Ross Vandegrift wrote:
Yes, you can absolutely boot from RAID1 with initrd. If you're not an
initrd wizard it will be difficult. You'll need to make sure that
your initrd has all the necessary device files, the modules for md,
the mdadm binary, and any share
On Sun, Nov 27, 2005 at 09:11:02PM -0500, David M. Strang wrote:
> + mdadm. Essentially, the end goal -- is if either drive fails, the system
> should not go down. So, I invoked the paritioned MD route; and created it
> on top of a single large partition for each drive. I'm still working out
> b
On Sunday November 27 2005 16:56:47, NeilBrown wrote:
Yes, do_mounts_md assumes v0.90.
The following patch will allow you to specify the version in the
kernel parameters, something like
md=d0,v1.0,/dev/sda,/dev/sdb
(though I haven't tested it).
However I'm not at all convinced that I want to
On Sunday November 27, [EMAIL PROTECTED] wrote:
>
> Just a quick update; I've been putting forth some due diligence on this --
> and it appears basically, that do_mounts_md.c is an antique. I've added a
> small debug line to md.c under md_import_device; and then also traced thru
> the do_mount
On Saturday 26 November 2005 23:32:51, David M. Strang wrote
Please forgive me for pinging you direct on this Neil; but I fear you are
the only one who can answer it.
I am a bit considered by this in the startup log:
Nov 26 21:47:35 xenogenesis kernel: md: raid1 personality registered as nr
3
On Saturday 26 November 2005 14:03:35, David M. Strang wrote:
On Saturday 26 November 2005 11:14:46, David M. Strang wrote:
> sdb1 is a 400GB partition -- it is type FD.
>
> Disk /dev/sdb: 400.0 GB, 400088457216 bytes
> 2 heads, 4 sectors/track, 97677846 cylinders
> Units = cylinders of 8 * 512 =
On Saturday 26 November 2005 11:14:46, David M. Strang wrote:
sdb1 is a 400GB partition -- it is type FD.
Disk /dev/sdb: 400.0 GB, 400088457216 bytes
2 heads, 4 sectors/track, 97677846 cylinders
Units = cylinders of 8 * 512 = 4096 bytes
Device Boot Start End Blocks Id Sy
On Saturday 26 November 2005 12:16:14, Guillaume Filion wrote:
Le 05-11-26, à 11:18, David M. Strang a écrit :
> md: invalid raid superblock magic on sdb1
Did you include the md and raid1 modules in mkinirtd.conf?
I'll admit that while I have my root on a raid1 device, I'm a bit confused
by th
Hello all --
I've read, and read, and read -- and I'm still not having ANY luck booting
completely from a raid1 device.
This is my setup...
sda1 is booting, working great. I'm attempting to transition to a bootable
raid1.
sdb1 is a 400GB partition -- it is type FD.
Disk /dev/sdb: 400.0 GB
12 matches
Mail list logo
