Re: grub-pc error when upgrading from buster to bullseye

2024-02-13 Thread John Boxall
On 2024-02-12 15:14, Greg Wooledge wrote: According to it uses debconf's database. That page includes instructions for viewing the device and changing it. I had just

Re: grub-pc error when upgrading from buster to bullseye

2024-02-12 Thread Greg Wooledge
On Mon, Feb 12, 2024 at 09:04:01PM +0100, Thomas Schmitt wrote: > Hi, > > John Boxall wrote: > > I am aware that the label and uuid (drive and partition) are replicated on > > the cloned drive, but I can't find the model number (in text format) stored > > anywhere on the drive. > > Maybe the

Re: grub-pc error when upgrading from buster to bullseye

2024-02-12 Thread Thomas Schmitt
Hi, John Boxall wrote: > I am aware that the label and uuid (drive and partition) are replicated on > the cloned drive, but I can't find the model number (in text format) stored > anywhere on the drive. Maybe the grub-pc package takes its configuration from a different drive which is attached to

Re: grub-pc error when upgrading from buster to bullseye

2024-02-12 Thread John Boxall
On 2024-02-12 09:34, Thomas Schmitt wrote: The disk/by-id file names are made up from hardware properties. I believe to see in the name at least: Manufacturer, Model, Serial Number. So you will have to find the configuration file which knows that /dev/disk/by-id address and change it either to

Re: grub-pc error when upgrading from buster to bullseye

2024-02-12 Thread Thomas Schmitt
Hi, John Boxall wrote: > Setting up grub-pc (2.06-3~deb11u6) ... > /dev/disk/by-id/ata-WDC_WDS100T2B0A-00SM50_21185R801540 does not > exist, so cannot grub-install to it! > What is confusing to me is that the error indicates the source SDD even > though I have updated the boot

grub-pc error when upgrading from buster to bullseye

2024-02-12 Thread John Boxall
I am attempting to upgrade my laptop (Thinkpad X230) from buster to bullseye and have run into the error below. In order to ensure that all goes well and not to lose all of the tweaks I have added over time, I am performing the upgrade first on a cloned HDD (via "dd") of the working SDD.