Sorry for the late reply, I did not see your post until now.
Le 14/05/2018 à 12:37, Niclas Arndt a écrit :
mdadm.conf says metadata=1.2.
So there is no risk that that the whole disk may be wrongly detected as
a RAID member instead of the last partition.
root@file2:~# blkid /dev/md2*
/dev/
__
From: Pascal Hambourg
Sent: Sunday, May 13, 2018 4:14 PM
To: debian-user@lists.debian.org
Subject: Re: Auto-assembled SW RAID in rescue mode
Le 11/05/2018 à 13:34, Niclas Arndt a écrit :
> At boot, I was prompted with a BIOS message saying that there was no boot
>
Le 11/05/2018 à 13:34, Niclas Arndt a écrit :
At boot, I was prompted with a BIOS message saying that there was no boot
device.
No, a BIOS upgrade doesn't modify fstab. I believe that EFI has anti-tampering
mechanisms that might have been triggered by the BIOS upgrade. (At least it's
currentl
Pascal Hambourg
Sent: Friday, May 11, 2018 9:15 AM
To: debian-user@lists.debian.org
Subject: Re: Auto-assembled SW RAID in rescue mode
Le 10/05/2018 à 23:30, Niclas Arndt a écrit :
>
> I received unofficial BIOS files from Gigabyte with new versions of Intel ME
> and CPU microcode. After upgr
Le 10/05/2018 à 23:30, Niclas Arndt a écrit :
I received unofficial BIOS files from Gigabyte with new versions of Intel ME
and CPU microcode. After upgrade, several Stretch machines no longer boot.
(Fresh installation works without any problem.)
What happened at boot time ?
I doubt that all
Hello,
I have a question that I suspect comes from the way rescue mode auto RAID
assembly and grub restoration work.
I received unofficial BIOS files from Gigabyte with new versions of Intel ME
and CPU microcode. After upgrade, several Stretch machines no longer boot.
(Fresh installation wor
6 matches
Mail list logo
