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

Re: Debian Install CD, locks up computer system.



Le mercredi 13 janvier 2021 à 16:19:40-0500, brian.hood@hotmail.com a écrit :
> I am being run around in circles trying to get assistance.  I am being
> redirected by individuals and WEB pages having "ALL THE ANSWERS" and not
> needing to know the facts.
> 
> It is clear that I have encountered a serious and destructive problem.
> 
> 
> I have installed the "debian-10.7.0-amd64-DVD-1.iso" to a USB drive
> connected to a Lenovo T420 which was running Windows 10 Pro.
> 
> The system boots to Windows 10 on the C: drive with the option of booting to
> another device if I press F12 at booting.
> 
> I use F12 to boot to the CD Drive, "debian-10.7.0-amd64-DVD-1.iso".
> I installed as Debian to an attached USB external drive. I used the standard
> non graphical installer. Installation
> proceeded fine, I accepted all defaults and did not install any additional
> software/drivers.  After 'Install System' the installer opened the CD Drive
> and asked me to reboot.  The "Install Grub" never came up.
> 
> I rebooted and got the bios Boot Menu that would come up when I pressed F12
> came up without my pressing F12.  The boot device list now has "debian" now
> added to the top of the boot menu.  None of the items in the list boot their
> respective devices.
> 
> 
> The Menu Reads:
> 
> 	debian
> 	Windows Boot Manager
>         ATA HDD0: WDC WD3200BEKT-08PBMT1
> 	USB HDD: FUJISTU MHV2080AH
> 	ATAPI CD0: Optiarca DVD RW AD-7710H
> 
> item ATA...
> 	is my Drive containing the all the Windows 10 system, including the Windows
> Boot Manager
> 
> item USB...
> 	is my external drive containing the newly installed Debian 10
> 
> item ATAPI...
> 	in my CD Drive
> 
> 
> Additional Notes:
> 
> I have used the same process to install Debian version 2 through 8 to
> secondary drives.
> 
> Nothing in documentation that I have come across indicates that this "new"
> debian would alter the "bios" boot menu or in anyway effect the Windows 10
> operating systems drive.  By right it had no business doing so
> automatically.
> 
> I can see no reason for some-one to believe that this would happen.
> 
> This is a very destructive problem.
> 
> I am looking at $200.00 cost to have new system installed and the loss of
> everything on my Windows 10 System.
> 
> I am retired on a disability pension.  My background is system logistics.
> This install has altered the existing bios/Windows 10 System without
> notification.  This directly violates the standards set for Debian installs.
> 
> Please, forward this to anyone that might be able to provide assistance.
> 
> I would like help, direction as to how to reinstate the original boot
> sequence for my computer.
> 
> I believe the only party capable of addressing this issue is the team or
> person that setup the Debian installer for this CD.
> 
> PS:  This is a new problem and therefore there is no documentation in the
> historical archives that could possible address this issue.

Dear Brian,

For these matters, the debian-user mailing list is the right place to
go.

Indeed, the Community Team is a team which is here to handle
interactions between members of the Debian Community that go wrong, and
tries to have the Debian Code of Conduct followed by the members of the
community in their interactions.

For convenience, I cc-ed the list here.

As for your specific matter, Windows 10 being an UEFI system, Debian
installation has to accomodate for this, and if you used the basic
installer, it did indeed attempt to install grub and create the specific
entry. Probably something went south there.

If you indeed tried to boot "Debian", and it failed, I'd guess it's
because, while the grub binary is on the uefi part of your main disk
along with the windows bootloader and other potential stuff, the grub
configuration is on your external drive which is not yet seen properly
when you hit the "debian" entry choice (which is the one you should use,
as grub will also allow you to boot windows 10), but it's a wild guess.

I'll let some users to chime in, as I admit I'm not the best to help
people debug such issues over mail. :/ But I'll keep an eye.

Bests,

-- 
Pierre-Elliott Bécue
GPG: 9AE0 4D98 6400 E3B6 7528  F493 0D44 2664 1949 74E2
It's far easier to fight for one's principles than to live up to them.

Attachment: signature.asc
Description: PGP signature


Reply to: