Bug#925556: UEFI or not, can't mount /dev
Trying again with expert install and some different choices, and putting nomodeset in the grub finally booted it. I'll send new logs soon.
Bug#925556: UEFI or not, can't mount /dev
logs.gz Description: application/gzip
Bug#925556: UEFI or not, can't mount /dev
I tried installing again. (This time with no network.) The normal
graphical install. All goes fine, but in the logs there is one "Failed
to get":
$ grep -A 2 'Failed to get' syslog |cut -c 17-
base-installer: warning: Failed to get debconf answer
'base-installer/kernel/linux/initrd'.
base-installer: info: Setting do_initrd='yes'.
base-installer: info: Setting link_in_boot='no'.
Anyway, then from BIOS boot list
choosing the first item, booting stops at
choosing the last item, booting stops at
By the way, it might not be a good idea to hardwire the names /sda when
making grub stuff, as that might not always be where it is... maybe I
should try editing ("e" at the grub menu) and replace the a with b, c,
etc. until I hit a winner... and can boot(?) But then how would I go
about making sure it would boot the next time by itself.
P.S., a few days ago I tried and expert install, and recall a question,
Name: base-installer/initramfs-tools/driver-policy
Type: select
Choices: generic: include all available drivers, targeted: only include
drivers needed for this system
Description: Drivers to include in the initrd:
Extended_description: The primary function of an initrd is to allow the..
But I recall no matter how I answer it, it didn't make a bootable
system.
Bug#925556: UEFI or not, can't mount /dev
On Thu, Mar 28, 2019 at 12:37:52AM +0800, 積丹尼 Dan Jacobson wrote: >> "SM" == Steve McIntyre writes: >SM> Please attach the installer syslog so we have a chance to see what >SM> happened. On the installed system, that's in /var/log/installer/syslog > >What should I give at that >initramfs prompt you see >that would put it on the screen? >Then I could take a photograph of it. Sorry, it's much too big to fit in a single screen for a photo. Try booting the installer again in rescue mode, mount the rootfs on that system and copy the file off so you can send it from another machine. I appreciate that's more effort for you, but we don't have anything like enough information here to debug this problem yet. You're showing a system installed with Stretch, using defaults. I've personally run that installation lots of times when testing on release day and not seen any problems like this, so more information is needed from the log files. -- Steve McIntyre, Cambridge, UK.st...@einval.com Who needs computer imagery when you've got Brian Blessed?
Bug#925556: UEFI or not, can't mount /dev
> "SM" == Steve McIntyre writes: SM> Please attach the installer syslog so we have a chance to see what SM> happened. On the installed system, that's in /var/log/installer/syslog What should I give at that initramfs prompt you see that would put it on the screen? Then I could take a photograph of it.
Bug#925556: UEFI or not, can't mount /dev
On Wed, Mar 27, 2019 at 12:07:11PM +0800, 積丹尼 Dan Jacobson wrote: >LS> Clearly the initramfs was able to mount /dev and run fsck, but mounting >LS> it to /root/dev to transfer to the real rootfs failed due to a missing >LS> directory. > >So it booted, meaning it is not a >https://www.debian.org/releases/stretch/amd64/ch03s06.html.en#UEFI >problem... Please attach the installer syslog so we have a chance to see what happened. On the installed system, that's in /var/log/installer/syslog -- Steve McIntyre, Cambridge, UK.st...@einval.com Armed with "Valor": "Centurion" represents quality of Discipline, Honor, Integrity and Loyalty. Now you don't have to be a Caesar to concord the digital world while feeling safe and proud.
Bug#925556: UEFI or not, can't mount /dev
LS> Clearly the initramfs was able to mount /dev and run fsck, but mounting LS> it to /root/dev to transfer to the real rootfs failed due to a missing LS> directory. So it booted, meaning it is not a https://www.debian.org/releases/stretch/amd64/ch03s06.html.en#UEFI problem...
Bug#925556: UEFI or not, can't mount /dev
On Tue, Mar 26, 2019 at 07:13:21PM +, Steve McIntyre wrote: > On Wed, Mar 27, 2019 at 02:58:36AM +0800, 積丹尼 Dan Jacobson wrote: > >Package: debian-installer > > > >Guess what, seen with ASUS X370-A: > > Dan, you know better than this. A useful bug report needs much more > information. For a start, what image did you use to install with? This > looks like it *might* be on first boot after installation, but you're > leaving me to guess at that. How did you partition, etc.? Were there > any errors reported during installation? > > Please help us to help you... Well the picture appears to show root is sdb2 on a disk with sdb1 and sdb2 partitions, and it can't mount /dev apparently because there is no /dev directory on the root filesystem to mount it on. At least that's what it looks like in the picture. Clearly the initramfs was able to mount /dev and run fsck, but mounting it to /root/dev to transfer to the real rootfs failed due to a missing directory. -- Len Sorensen
Bug#925556: UEFI or not, can't mount /dev
On Wed, Mar 27, 2019 at 02:58:36AM +0800, 積丹尼 Dan Jacobson wrote: >Package: debian-installer > >Guess what, seen with ASUS X370-A: Dan, you know better than this. A useful bug report needs much more information. For a start, what image did you use to install with? This looks like it *might* be on first boot after installation, but you're leaving me to guess at that. How did you partition, etc.? Were there any errors reported during installation? Please help us to help you... -- Steve McIntyre, Cambridge, UK.st...@einval.com "You can't barbecue lettuce!" -- Ellie Crane
