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

Bug#986387: marked as done (cdrom: Unsuccessful installation on Windows10-Dell-Latitude-Ultrabook. No grub.)

Your message dated Tue, 6 Apr 2021 00:12:51 +0100
with message-id <20210405231251.GI16000@tack.einval.com>
and subject line Re: Bug#986387: cdrom: Unsuccessful installation on Windows10-Dell-Latitude-Ultrabook. No grub.
has caused the Debian Bug report #986387,
regarding cdrom: Unsuccessful installation on Windows10-Dell-Latitude-Ultrabook. No grub.
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
986387: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986387
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: cdrom
Severity: important

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

Jigdone a debian-10.9.0-amd64-xfce-CD1 USB-Stick.  Booted a Dell Latitude
Ultrabook with preinstalled Windows 10 from aforesaid USB-Stick.  Performed
full installation including resizing the NTFS partition and including
installation of grub(2).  Rebooted.  No bootable media found.
On reboot via F12 I could select Windows Boot Manager to boot successfully into
Windows10.  But Grub or Linux are not available.

Windows10 recognises the resize of the NTFS partition, the
additional partitions sda4 (root) and sda5 (swap) are recognised as well.

UEFI booting presents a "normal" Windows 10.
Legacy booting says, no bootable media found.
Booting via UEFI-->Windows Bootmanager boots Windows 10.
Legacy AND UEFI booting Installation-USB-Stick work up to the point to
register the disk(s), and there it stops, it doesn't seem to recognise the
partition table, that the installer has written and is also reported by
Windows10.

It just presents an unformatted disk of MAX units to go on with.  But Windows
DatentrÀgerverwaltung does indeed see the created partitions.

I'm at a loss.

-- System Information:
Debian Release: 10.0
  APT prefers testing
  APT policy: (500, 'testing'), (500, 'stable')
Architecture: i386 (x86_64)

Kernel: Linux 5.9.0-5-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_AT@euro, LC_CTYPE=de_AT@euro (charmap=ISO-8859-15)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

--- End Message ---
--- Begin Message --- 
On Tue, Apr 06, 2021 at 12:06:53AM +0200, enno wrote:
>Oops, found mistake in my debian-live actions, dd'd to /dev/sdb1 instead of /dev/sdb.
>
>Now it seems to work.  Bugreport cancel.  Unless there are further problems...

OK, cool. Closing the bug then. Please re-open if you continue to have
problems. Thanks for following up!

-- 
Steve McIntyre, Cambridge, UK.                                steve@einval.com
"I've only once written 'SQL is my bitch' in a comment. But that code 
 is in use on a military site..." -- Simon Booth

--- End Message ---
Reply to: