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

Fw: Stretch/testing instllable, but not bootable upon installation



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


OK,

now I dd'ed the raw-image, made in vm-manager, onto my USB-stick and tried to boot my

thin-client from it, here is what I saw.

The yellow colour is real, I am not faking this, it's a defective monitor cable.

It does not matter much, my experience so far tells me that because of too tight

security-restrictions on Debian-Testing, the image would probably not

be usable anyway, i.e. no packages or software-updates would be installable, but

it normaly should boot up at least.




Begin forwarded message:

Date: Sat, 2 Apr 2016 14:06:46 +0200
From: Andreas Glaeser <bugs.andreas.glaeser@freenet.de>
To: debian-boot@lists.debian.org
Cc: "Lennart Sorensen" <lsorense@csclub.uwaterloo.ca>
Subject: Re: Stretch/testing instllable, but not bootable upon installation


- -----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Thu, 31 Mar 2016 11:43:24 -0400
"Lennart Sorensen" <lsorense@csclub.uwaterloo.ca> wrote:

> On Thu, Mar 31, 2016 at 09:57:51AM +0200, Andreas Glaeser wrote:
> > /dev/sdc1 was my -boot-partition from a previous attempt with BTRFS, as I installed
> > on a legacy thin-client, tere was only the internal flash-disk present besides the
> > USB-key I installed on. As far as I know the installer uses UUIDs by default anyway,
> > maybe there is something wrong with initramfs.
> > At installation-time there was a second USB-key with the current netinstall-image.
> > BTRFS used to work fine for me for several years already, that's why I feel there are
> > roadblocks set up in front of me. Should I report it as a GRUB-bug??  
> 
> I really don't know if it is a grub bug or a debian installer bug.
> Since it asks for sdc2, that sounds like something the installer should
> have taken care of, so probably not grub's fault.
> 

Hello again,

in order to exclude any hardware-failure, I retried GRUB-installation on BTRFS in KVM

with virt-manager, and it's no problem there, so it is USB-specific, I guess, see my

attached screenshots.

Greetings 

Andreas
- -----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iEUEARECAAYFAlb/td4ACgkQ5+rBHyUt5wtfYwCY86ECJE1jqGpgcsBROorCISSm
FwCgnqcfmFkbimXnoKeJR6c3IFibE+s=
=gWM1
- -----END PGP SIGNATURE-----
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iEYEARECAAYFAlb/1TcACgkQ5+rBHyUt5wt3IQCcDAth4jFxTOkjZyL/+SCXlGwG
ez4An1+XCVJZMAYxnJF4bsauFwejnIVV
=n++K
-----END PGP SIGNATURE-----

Attachment: vmm-usb-boot.JPG
Description: JPEG image


Reply to: