ry Steele
Sent: teisipäev, 2. juuli 2019 15:08
To: fully automatic installation for Linux
Subject: Re: MD devices are not wiped if LVM exists
Moving away from Andrew's WIPEDISKS script for a second, I have made a simple
script containing just
vgdisplay
The output from this is null,
Moving away from Andrew's WIPEDISKS script for a second, I have made a
simple script containing just
vgdisplay
The output from this is null, suggesting that FAI does not see any LVM
stuff at this stage, however after it has completed these bits of the
disk_config,
Executing: wipefs -af
Hey Jerry,
That indicates to me that the MD is still running for some reason. I
have occasionally had that as an intermittent fault, but I can't recall
what I did to resolve it.
Sorry,
Andrew
On Tue, 2019-07-02 at 11:34 +0100, Jerry Steele wrote:
> Hi Andrew,
>
> Many thanks for that, however,
Hi Andrew,
Many thanks for that, however, that seems to bring up another issue. During
the partitioning step, it is able to create all the underlying partitions,
but fails with:
Executing: yes | mdadm --create /dev/md0 --level=raid1 --force --run
--raid-devices=2 /dev/sda1 /dev/sdb1
(STDERR)
On Mon, 2019-07-01 at 16:10 +0200, Thomas Lange wrote:
> You can write a simple hook, which is then executed before
> task_partition. Therefore, create a shell script
> hooks/partition.DEFAULT
Hey,
Here is what I have as hooks/partition.WIPEDISKS it'll stop any MDs or
VGs that were started by
> On Mon, 1 Jul 2019 14:40:51 +0100, Jerry Steele
> said:
> If FAI is run against this machine again after its 1st install, I get the
following error:
> (STDERR) mdadm: Cannot get exclusive access to /dev/md1:Perhaps a running
process, mounted filesystem or active volume
This is my disk_config:
disk_config disk1
primary - 350 - -
primary swap 2G swap sw,pri=1
primary - 0- - -
disk_config disk2 sameas:disk1
disk_config raid fstabkey:uuid
raid1 /boot disk1.1,disk2.1 ext4 rw,noatime,errors=remount-ro
raid1 - disk1.3,disk2.3 - -
disk_config lvm fstabkey:uuid
vg
