Re: Stretch/testing instllable, but not bootable upon installation
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Wed, 30 Mar 2016 11:08:47 -0400
"Lennart Sorensen" <lsorense@csclub.uwaterloo.ca> wrote:
> /dev/sdc2 sounds odd. I wonder if a USB key confused it about disk
> ordering. I also thought everything used UUID to find disks now, not
> device names (since they are inherently so unstable).
>
> What disks were present during the install and which were still there
> when you tried to boot?
>
> Of course use of BTRFS makes me have no idea, since I haven't dared to
> try that yet. Last I looked at it I found it unusable even for just
> storing data, but that was a long time ago.
/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??
Andreas
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iEYEARECAAYFAlb82IYACgkQ5+rBHyUt5wsdJQCeNrWaftECxPGPfTLmflHoBzrM
BIoAnR84zlnGEqv5AeT3RIsUN2PRgCG9
=YLN2
-----END PGP SIGNATURE-----
Reply to: