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

Bug#1024346: cdrom: debian-11.5.0-amd64-netinst.iso boots to Grub CLI on Dell Optiplex 5090







------- Original Message -------
On Thursday, November 24th, 2022 at 20:47, Steve McIntyre <steve@einval.com> wrote:


> 
> 
> On Sun, Nov 20, 2022 at 02:59:10AM +0000, r@tekhax.io wrote:
> 
> > Thanks for the detailed message. I started everything over to try to reproduce the problem.
> 
> 
> Thanks for that!
> 
> > I wiped out the NVMe drive again (wipefs -a and dd if=/dev/zero
> > of=/dev/sdb bs=512 count=100000), and re-installed Pop!OS 22.04
> > non-NVidia version, which was successful. The computer was operating
> > normally and booting into Pop!OS, no problem.
> 
> 
> OK, cool.
> 
> > I then downloaded a new Debian 11.5.0 netinst ISO, checked the
> > SHA512, wrote it to the USB drive with extra parameters mentioned
> > earlier.
> > 
> > I powered off the computer, inserted the USB 3.0 stick into a USB 3.0
> > port and powered on. I hit F12 to reach the Dell one-time boot menu
> > and chose the USB stick to boot from.
> > 
> > It immediately boots into the Grub CLI as I described before. So
> > either the presence of the Pop!OS partition or the presence of the
> > entry in the UEFI boot table seems to be confusing the Debian USB
> > stick.
> 
> 
> Right.
> 
> By pure lucky coincidence, yesterday another Debian developer saw a
> very similar issue on a Lenovo machine (see bug #1024720), and we
> debugged his problem together. I'm thinking that you may have another
> instance here. Could you please check for me: does the Pop!OS
> installation include a file in the path "/.disk/info" on any of its
> partitions?
> 
> If so, that will be the cause of the problem here. If so, if you
> (temporarily) rename that file then you should find that the Debian
> installer will work just fine.
> 
> --
> Steve McIntyre, Cambridge, UK. steve@einval.com
> "...In the UNIX world, people tend to interpret `non-technical user'
> as meaning someone who's only ever written one device driver." -- Daniel Pead

That seems to have been the problem. Thanks!


Reply to: