Op Fri, 17 Jul 2015 20:34:59 -0500, schreef David Wright:
Also, my advice in this post applies only when the disk size is bigger
than 2 TiB, and 2 TB 2 TiB.
Although I was being flippant, isn't that a bit short-sighted? Currently
a 2TB external desktop (Seagate, Staples regular price) is
Op Thu, 16 Jul 2015 20:53:54 +0200, schreef Pascal Hambourg:
Linux4Bene a écrit :
Could it be that grub is confused by the mdadm 0.9 metadata at the end
of the disk?
Maybe. This is typically the kind of problem which can happen with the
0.9 superblocks. Why are you using this obsolete
Op Thu, 16 Jul 2015 15:01:16 -0400, schreef Gary Dale:
On 16/07/15 08:00 AM, Linux4Bene wrote:
Op Thu, 16 Jul 2015 10:58:15 +, schreef Linux4Bene:
snip
Could it be that grub is confused by the mdadm 0.9 metadata at the end
of the disk? When I dd'ed, it was only the 40 GB at the start
Op Sun, 19 Jul 2015 15:36:07 +, schreef Linux4Bene:
Well, I have tried so many configs to get this dedicated server up and
running, that I tried a whole bunch of scenarios.
The OVH rescue system only loads raid partitions of the type 0.9.
It didn't look like it wanted to read my type 1.2
David Wright a écrit :
Quoting Pascal Hambourg (pas...@plouf.fr.eu.org):
David Wright a écrit :
Quoting Pascal Hambourg (pas...@plouf.fr.eu.org):
May I also ask why you created a separate /boot ?
Perhaps he read your
https://lists.debian.org/debian-user/2015/07/msg00717.html
Not without a
David Wright a écrit :
Quoting Pascal Hambourg (pas...@plouf.fr.eu.org):
May I also ask why you created a separate /boot ?
Perhaps he read your
https://lists.debian.org/debian-user/2015/07/msg00717.html
Not without a time machine.
Also, my advice in this post applies only when the disk
Quoting Pascal Hambourg (pas...@plouf.fr.eu.org):
David Wright a écrit :
Quoting Pascal Hambourg (pas...@plouf.fr.eu.org):
May I also ask why you created a separate /boot ?
Perhaps he read your
https://lists.debian.org/debian-user/2015/07/msg00717.html
Not without a time
On 16/07/15 08:00 AM, Linux4Bene wrote:
Op Thu, 16 Jul 2015 10:58:15 +, schreef Linux4Bene:
snip
Could it be that grub is confused by the mdadm 0.9 metadata at the end of
the disk? When I dd'ed, it was only the 40 GB at the start of the disk,
not at the end. Any way I can remove this error
installing grub, I get this error:
error: found two disks with the index 0 for RAID md2.
error: superfluous RAID member (2 found).
error: found two disks with the index 0 for RAID md2.
error: superfluous RAID member (2 found).
error: found two disks with the index 0 for RAID md2.
error: superfluous
Op Thu, 16 Jul 2015 10:58:15 +, schreef Linux4Bene:
snip
Could it be that grub is confused by the mdadm 0.9 metadata at the end of
the disk? When I dd'ed, it was only the 40 GB at the start of the disk,
not at the end. Any way I can remove this error and not having my LVM
data destroyed?
Quoting Pascal Hambourg (pas...@plouf.fr.eu.org):
May I also ask why you created a separate /boot ?
Perhaps he read your https://lists.debian.org/debian-user/2015/07/msg00717.html
:)
Cheers,
David.
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of
Linux4Bene a écrit :
Could it be that grub is confused by the mdadm 0.9 metadata at the end of
the disk?
Maybe. This is typically the kind of problem which can happen with the
0.9 superblocks. Why are you using this obsolete format ? You should use
the newer 1.x format, specifically 1.2
On Wed, Jun 13, 2012 at 6:36 PM, Steve Dowe s...@warpuniversal.co.uk wrote:
On 13/06/12 23:15, Tom H wrote:
Since metadata 1.1 or 1.2 stores the metadata at the beginning rather
than at the end, perhaps using a partitioned mdraid device with that
metada works with squeeze.
Good idea. I'll
out many more of those error messages:
error: superfluous RAID member (5 found).
repeats 17 times
So it does point to grub being at fault somewhere, rather than the initrd.
Have I missed something blindingly obvious?
Thanks again,
Steve
--
Steve Dowe
Warp Universal Limited
http://warp2.me
, as when it
boots I see an error flash up quickly:
error: superfluous RAID member (5 found)
It appears that the initramfs then gets loaded, the RAID detection fails and
it then looks for the LVM volume group, which it can't find (as the LVM
group exists on the RAID device).
I don't believe
, as when it
boots I see an error flash up quickly:
error: superfluous RAID member (5 found)
It appears that the initramfs then gets loaded, the RAID detection fails and
it then looks for the LVM volume group, which it can't find (as the LVM
group exists on the RAID device). I see this output
). But I must be doing
something wrong with the disk set up stage in the installer, as when it
boots I see an error flash up quickly:
error: superfluous RAID member (5 found)
It appears that the initramfs then gets loaded, the RAID detection fails and
it then looks for the LVM volume group
flash up quickly:
error: superfluous RAID member (5 found)
It appears that the initramfs then gets loaded, the RAID detection
fails and it then looks for the LVM volume group, which it can't find
(as the LVM group exists on the RAID device). I see this output:
Loading, please wait...
mdadm
On Wed, Jun 13, 2012 at 2:41 PM, Gary Dale garyd...@rogers.com wrote:
For example, Squeeze has problems with booting from partitioned RAID arrays.
After running update-initramfs and update-grub, I find that the UUID for the
partitions has been replaced with the UUID for the array, so that the
On 13/06/12 19:07, Tom H wrote:
On Wed, Jun 13, 2012 at 12:40 PM, Christofer C. Bell
christofer.c.b...@gmail.com wrote:
I don't believe you can boot from a striped volume (raid5 being a
stripe + parity). I found some instructions that may allow this to
work but requires packing a non-standard
On 13/06/12 19:56, Tom H wrote:
On Wed, Jun 13, 2012 at 2:41 PM, Gary Dale garyd...@rogers.com wrote:
For example, Squeeze has problems with booting from partitioned RAID arrays.
After running update-initramfs and update-grub, I find that the UUID for the
partitions has been replaced with the
On Wed, Jun 13, 2012 at 4:37 PM, Steve Dowe s...@warpuniversal.co.uk wrote:
On 13/06/12 19:56, Tom H wrote:
On Wed, Jun 13, 2012 at 2:41 PM, Gary Dale garyd...@rogers.com wrote:
For example, Squeeze has problems with booting from partitioned RAID
arrays.
After running update-initramfs and
On 13/06/12 23:15, Tom H wrote:
Since metadata 1.1 or 1.2 stores the metadata at the beginning rather
than at the end, perhaps using a partitioned mdraid device with that
metada works with squeeze.
Good idea. I'll boot it up with a live CD and report back soon.
--
Steve Dowe
Warp Universal
23 matches
Mail list logo
