Florian Philipp lists at binarywings.net writes:
Your boot partition is not by any chance a logical partition and
therefore would be (hd0,4) and not (hd0,0)?
grub root (hd0,4)
Error 22: No such partition
No?
You can try to use 0.90 metadata by specifying it while creating the
RAID with
Florian Philipp lists at binarywings.net writes:
You can try to use 0.90 metadata by specifying it while creating the
RAID with mdadm. I'm using it myself because AFAIK this is the only way
for grub to handle a single RAID containing partitions instead of
partitions containing RAIDs.
Not
Am 14.04.2011 14:56, schrieb James:
Florian Philipp lists at binarywings.net writes:
Your boot partition is not by any chance a logical partition and
therefore would be (hd0,4) and not (hd0,0)?
grub root (hd0,4)
Error 22: No such partition
No?
You can try to use 0.90 metadata
James wireless at tampabay.rr.com writes:
Not sure what this inconsistency is tell me:
I rebooted, using a minimal CD. Dmesg has this information:
md: bindsda1
md: bindsdb3
md: bindsda2
md: bindsda3
md/raid1:md126: active with 2 out of 2 mirrors
md126: detected capacity change from 0 to
Am 14.04.2011 15:41, schrieb James:
James wireless at tampabay.rr.com writes:
Not sure what this inconsistency is tell me:
I rebooted, using a minimal CD. Dmesg has this information:
md: bindsda1
md: bindsdb3
md: bindsda2
md: bindsda3
md/raid1:md126: active with 2 out of 2
Hi,
Just picking the last post I read here. OP. You may want to read this:
http://grub.enbug.org/LVMandRAID
I know little about LVM and nothing about RAID but found that howto that
is pretty straight foreword on how it should work. Also, make sure you
are using a version of grub that can
On Thu, Apr 14, 2011 at 7:56 AM, James wirel...@tampabay.rr.com wrote:
OK, so, I've rebooted and got the md1, md2, md3 renamed by
(whatever) to md125 md127 and md126, respectively.
The name of the array probably got weird because your hostname doesn't
match the homehost of the array. The array
Dale rdalek1967 at gmail.com writes:
http://grub.enbug.org/LVMandRAID
Not using lvm at all. Simple raid1
on /boot, /, and swap partitions.
I do not need the added complexity of LVM
on a simple raid array; I perfectly capable
of follow explicit instructions(syntax) and
still screwing things
Florian Philipp lists at binarywings.net writes:
I don't think the missing partition table is your problem.
OK, let's assume you are correct, ignoring .
However, you might be onto something with the changed sector offset. But
I don't know enough of this to help you.
Well if I have to
Am 14.04.2011 17:07, schrieb James:
Florian Philipp lists at binarywings.net writes:
I don't think the missing partition table is your problem.
OK, let's assume you are correct, ignoring .
However, you might be onto something with the changed sector offset. But
I don't know enough
James wrote:
Dalerdalek1967at gmail.com writes:
http://grub.enbug.org/LVMandRAID
Not using lvm at all. Simple raid1
on /boot, /, and swap partitions.
I do not need the added complexity of LVM
on a simple raid array; I perfectly capable
of follow explicit instructions(syntax) and
Florian Philipp lists at binarywings.net writes:
Are you sure sda1 and sdb1 are not in use? Did the kernel activate the
already present RAID? Then you have to deactivate it. Use
mdadm --stop /dev/md*
AHh!
livecd ~ # mdadm --stop /dev/md*
mdadm: error opening /dev/md: Is a
Dale rdalek1967 at gmail.com writes:
http://www.gentoo.org/doc/en/gentoo-x86+raid+lvm2-quickinstall.xml
http://en.gentoo-wiki.com/wiki/RAID/Software
That talks about using RAID tho. I don't think you have to be using LVM
to use that guide. It just talks about both in one place.
Am 14.04.2011 18:29, schrieb James:
Florian Philipp lists at binarywings.net writes:
Are you sure sda1 and sdb1 are not in use? Did the kernel activate the
already present RAID? Then you have to deactivate it. Use
mdadm --stop /dev/md*
AHh!
livecd ~ # mdadm --stop
*Head scratch* This, uhm, looks odd. No clue what to make of it.
Ahhh,
Don't give up just yet?
I issued these commands:
mdadm --create /dev/md127 --level=1 --raid-devices=2
--metadata=0.90 /dev/sda1 /dev/sdb1
mdadm --create /dev/md125 --level=1 --raid-devices=2
--metadata=0.90 /dev/sda3
Florian Philipp lists at binarywings.net writes:
livecd ~ # mdadm --stop /dev/md*
mdadm: error opening /dev/md: Is a directory
mdadm: stopped /dev/md1
mdadm: stopped /dev/md125
mdadm: stopped /dev/md126
mdadm: stopped /dev/md127
mdadm: stopped /dev/md3
mdadm: stopped /dev/md4
Am 14.04.2011 22:19, schrieb James:
*Head scratch* This, uhm, looks odd. No clue what to make of it.
Ahhh,
Don't give up just yet?
I issued these commands:
mdadm --create /dev/md127 --level=1 --raid-devices=2
--metadata=0.90 /dev/sda1 /dev/sdb1
mdadm --create /dev/md125
Am 12.04.2011 18:53, schrieb James:
James wireless at tampabay.rr.com writes:
Everything I try within grub indicated the filesystem is unknown.
This stumps me
http://bugs.gentoo.org/show_bug.cgi?id=250829
Bug above looks like this grub support of ext4 was
flushed out and fixed some
Dale writes:
Same here. I use ext3 and reiserfs, depending on what it is, but /boot
is always ext2. Why, it works well with grub and has for many many
years and most likely will for many years to come as well.
As for making things the same, that my not always be a good idea
either. I
Stroller stroller at stellar.eclipse.co.uk writes:
James, if I'm not wrong (legacy) sys-boot/grub-0.97-r10
does not have drivers for ext4. Not sure if there's
a patch for it, or if grub2 can boot from ext4.
Mick, that's what I was wondering.
No evidence either way, that I could find
Neil Bothwick neil at digimed.co.uk writes:
If /boot is on a separate partition, you should be using
It is.
find /grub/stage1
grub find /grub/stage1
Error 15: File not found
grub find /boot/grub/stage1
Error 15: File not found
If the symlink is there for boot - /boot -- and it is by
On Tuesday 12 April 2011 15:10:52 James wrote:
Stroller stroller at stellar.eclipse.co.uk writes:
There's no need for extents on such a small partition,
nor journalling (because you write to /boot so
rarely, the likelihood of a power failure when you're
doing so is minuscule).
Yea,
Peter Humphrey wrote:
On Tuesday 12 April 2011 15:10:52 James wrote:
Strollerstrollerat stellar.eclipse.co.uk writes:
There's no need for extents on such a small partition,
nor journalling (because you write to /boot so
rarely, the likelihood of a power failure when you're
On Tuesday 12 April 2011 09:57:26 Dale wrote:
Peter Humphrey wrote:
On Tuesday 12 April 2011 15:10:52 James wrote:
Strollerstrollerat stellar.eclipse.co.uk writes:
There's no need for extents on such a small partition,
nor journalling (because you write to /boot so
rarely, the
On Tuesday 12 April 2011 15:57:26 Dale wrote:
As for making things the same, that my not always be a good idea
either.
I might add a quotation from Ralph Waldo Emerson: a foolish preoccupation with
consistency is the hobgoblin of small minds.
--
Rgds
Peter
James wireless at tampabay.rr.com writes:
I've found GRUB's handling of symlinks to be variable at best. Try
searching for the real file.
All the files are in /boot/grub:
(chroot) slam grub # ls
defaultgrub.conf minix_stage1_5 stage2.old
device.map grub.conf.bak
26 matches
Mail list logo
