[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: 26th pass at installing 11-3, fails



On Saturday, 11 June 2022 08:40:15 EDT Andrew M.A. Cater wrote:
> On Sat, Jun 11, 2022 at 07:13:38AM -0400, gene heskett wrote:
> > On Friday, 10 June 2022 08:23:26 EDT gene heskett wrote:
> > > On Friday, 10 June 2022 02:45:20 EDT gene heskett wrote:
> > > > On Friday, 10 June 2022 00:45:19 EDT David Wright wrote:
> > > > > On Thu 09 Jun 2022 at 23:59:06 (-0400), gene heskett wrote:
> > > > > > On Thursday, 9 June 2022 21:13:53 EDT mick crane wrote:
> > > > > > > On 2022-06-09 22:15, gene heskett wrote:
> > > > > I don't recall seeing UUIDs in the d-i, perhaps because they're
> > > > > so
> > > > > long. I usually see the entries from /dev/disk/by-id/, or part
> > > > > thereof.
> > 
> > But thats not long enough to show whats beyond the samsung 870,
> > their's another alpha label that I'ds the tech in the drive, which
> > in this case would be positive ID of the correct drive, letters QVC,
> > not EVO like the earlier production raid drives which are all EVO's.
> > This drive I am trying to use for the next install, is plugged into
> > the socket labeled SATA6G_5 on this Z370-AII motherboard.  Is this a
> > problem? IDK.
> Shouldn't be.
> 
> Are you using UEFI / legacy MBR/BIOS to boot this drive ?
> 
> You can use a completely blank drive: although others suggest using
> gparted or similar beforehand, the partitioner is smart enough to do
> it for itself.
> 
> Grub is the _last_ thing to be written, more or less.
> 
> Grub-efi requires an ESP partition - which is FAT formatted - at the
> beginning of the disk and the rest can happily be one large LVM drive.
> 
> Note: For Bullseye, the default swap size is 1G. That shouldn't matter
> to you because you have swap on your RAID.
> 
> > > Based on that theory, I may repartition that drive with a 4gig
> > > /boot
> > > and the rest as one big / one, I have run into that a few times
> > > before.
> 
> That's effectively what LVM will do for you ...
> 
> > Welp, I did that, but the installer refuses to set the bootable flag
> > on that drive, it blinks the remote screen, but when its repainted,
> > its still off. I went thru the loop, even made a new gpt partition
> > table, but no joy. and all I have to show for it is a 5 megabyte
> > plus jpeg from my camera so you'll just have to take my word for it.
> 
> See above: how are you installing?
> 
> > I've not had a problem setting the bootable flag before.  What might
> > be the reason?
> > 
> > And it took 3 passes to get rebooted to the old drive because
> > something happened to the raid but it apparently fixed itself. The
> > bios, apparently didn't see /dev/sda at all the first time, and it
> > wasn't touched that I know of.
> > 
> > Thanks all, David Wright in particular.
> > 
> > > > Thanks David.
> > > > 
> > > > > But bear in mind that /dev/disk/ can be fully listed by the d-i
> > > > > from
> > > > > the very start, by switching to a shell on Alt-F2/3.
> > > > > 
> > > > > Cheers,
> > > > > David.
> > > > > 
> > > > > .
> > > > 
> > > > Cheers, Gene Heskett.
> > > 
> > > Cheers, Gene Heskett.
> > 
> > Cheers, Gene Heskett.
> 
> So: under UEFI boot and (encrypted) LVM, I have a partition layout
> something like this:
> 
> 537M - FAT - at the very beginning of the disk - the ESP partition -
> mounted as /boot/efi
> 
Is that now mandatory for 11.3? It ceretainly wasn't need for 11.0

> 512M - ext2 - mounted as /boot

No such /boot/efi visible here for the old boot:
gene@coyote:~$ ls -l /boot
total 49660
-rw-r--r-- 1 root root   236106 Mar 17 11:40 config-5.10.0-13-amd64
-rw-r--r-- 1 root root   236144 Apr 29 05:36 config-5.10.0-14-amd64
drwxr-xr-x 5 root root     4096 May 26 09:22 grub
-rw-r--r-- 1 root root 18273823 Apr 10 07:16 initrd.img-5.10.0-13-amd64
-rw-r--r-- 1 root root 18379218 May  2 17:28 initrd.img-5.10.0-14-amd64
drwx------ 2 root root    16384 Feb 19 12:09 lost+found
-rw-r--r-- 1 root root       83 Mar 17 11:40 System.map-5.10.0-13-amd64
-rw-r--r-- 1 root root       83 Apr 29 05:36 System.map-5.10.0-14-amd64
-rw-r--r-- 1 root root  6840768 Mar 17 11:40 vmlinuz-5.10.0-13-amd64
-rw-r--r-- 1 root root  6843648 Apr 29 05:36 vmlinuz-5.10.0-14-amd64
gene@coyote:~$ 
So I assumed I can re-install w/o the EFI bs.

And I did try ext2 for an fs choice. Made no difference, it would not set 
the bootable flag. Tried both fat16 and fat32 too. Spmething would not 
allow settiing the bootable flag.

let me see what gparted says, brb.
So I've redone the re-partitioning and formatting of that drive. gparted 
had no problem marking it other than not offering a choice of mount 
points, that was greyed out so I'll have to do that from the d-i for 
install attempt #28. As soon as I send this.



> 998G - LVM
> 
> 1G swap
> 
> Hope this helps, as ever,
> 
> Andy Cater
> 
> 
> 
> .


Cheers, Gene Heskett.
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis




Reply to: