On 2021-03-26 02:59, deloptes wrote:
Gary Dale wrote:
Perhaps it only works with virgin drives? Mine had been removed from
another machine where they had been part of a different array. I zeroed
the superblocks before creating the new array.
I doubt that - IMO should be either the BIOS or the
On 2021-03-26 00:04, Felix Miata wrote:
Gary Dale composed on 2021-03-25 21:19 (UTC-0400):
From what I read in looking for solutions, the problem is common. I
even tried one workaround of zapping any existing partition table on the
drives. Nothing worked.
Hello,
On Fri, Mar 26, 2021 at 02:31:21PM -0400, Gary Dale wrote:
> I'm not convinced that the problem is the BIOS writing a partition
> table. In your link the last post talks about zapping the
> partition table to stop the behaviour. This suggests the BIOS/UEFI
> was restoring the backup
Hello,
On Mon, Mar 22, 2021 at 06:20:56PM -0400, Gary Dale wrote:
> I've found many other people complaining about similar issues when using
> whole disks to create mdadm RAID arrays. Some of these complaints go back
> many years, so this isn't new.
Any time I've seen this problem pursued (as
Gary Dale wrote:
> Perhaps it only works with virgin drives? Mine had been removed from
> another machine where they had been part of a different array. I zeroed
> the superblocks before creating the new array.
I doubt that - IMO should be either the BIOS or the drives, or a combination
of both
On 2021-03-25 21:14, Gary Dale wrote:
On 2021-03-23 08:44, deloptes wrote:
deloptes wrote:
A friend told me that he found out it is a problem in some BIOSes with
UEFI that can not handle a boot of md UEFI partition.
Perhaps it also depends how they handle the raid of a whole disk.
Are you
On 2021-03-23 11:45, Reco wrote:
Hi.
On Tue, Mar 23, 2021 at 01:44:23PM +0100, deloptes wrote:
IMO the problem is that if it is not a partition the mdadm can not
assemble as it is looking for a partition,
My mdadm.conf says:
# by default (built-in), scan all partitions
On 2021-03-23 08:44, deloptes wrote:
deloptes wrote:
A friend told me that he found out it is a problem in some BIOSes with
UEFI that can not handle a boot of md UEFI partition.
Perhaps it also depends how they handle the raid of a whole disk.
Are you trying to boot from that raid?
Forgot to
On 2021-03-23 08:29, deloptes wrote:
Gary Dale wrote:
It's not just me but a lot of other people have been having the same
problem. It's been reported many times as I discovered after trying to
use whole disks. Moreover, the fixes that I'd used in the past don't
seem to work reliably without
Gary Dale composed on 2021-03-25 21:19 (UTC-0400):
> From what I read in looking for solutions, the problem is common. I
> even tried one workaround of zapping any existing partition table on the
> drives. Nothing worked.
Hi.
On Tue, Mar 23, 2021 at 01:44:23PM +0100, deloptes wrote:
> IMO the problem is that if it is not a partition the mdadm can not
> assemble as it is looking for a partition,
My mdadm.conf says:
# by default (built-in), scan all partitions (/proc/partitions) and all
# containers for MD
deloptes wrote:
> A friend told me that he found out it is a problem in some BIOSes with
> UEFI that can not handle a boot of md UEFI partition.
> Perhaps it also depends how they handle the raid of a whole disk.
> Are you trying to boot from that raid?
Forgot to ask what is in your
Gary Dale wrote:
> It's not just me but a lot of other people have been having the same
> problem. It's been reported many times as I discovered after trying to
> use whole disks. Moreover, the fixes that I'd used in the past don't
> seem to work reliably without partitions.
A friend told me
On 2021-03-22 18:49, Andy Smith wrote:
Hi Gary,
On Mon, Mar 22, 2021 at 06:20:56PM -0400, Gary Dale wrote:
I suggest that, since it appears the developers can't get this work
reliably, that the option to use the whole disk be removed and mdadm insist
on using partitions. At the very least,
I've spent a few days experimenting with using whole disks in a RAID 5
array and have come to the conclusion that it simply doesn't work well
enough to be used.
The main problem I had was that mdadm seems to have problems assembling
the array when it uses entire disks instead of partitions.
Hi Gary,
On Mon, Mar 22, 2021 at 06:20:56PM -0400, Gary Dale wrote:
> I suggest that, since it appears the developers can't get this work
> reliably, that the option to use the whole disk be removed and mdadm insist
> on using partitions. At the very least, mdadm --create should issue a
> warning
16 matches
Mail list logo
