Re: [qubes-users] installation failure hen trying to instal from usb to samsung sad on lenovo 220

[Marek Marczykowski-Górecki]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On Thu, Mar 29, 2018 at 11:56:12AM -0700, kai....@gmail.com wrote:
> greetings,
>
> i copied the current iso (tried it.both with rc5 and with today final official iso) to a 32gb usb stick
> and made my lenovo x220 boot from it. all went well until i choosed to habe the newly installed
> samsung 512gb ssd as target (it was listed in the graphic menu of the available targets).
> the system kind of halted for a second or two and then throwed an
> anaconda 25.20.9-12 exception report
> Trace back (most recent file first):
>
> File "/usr/python3.5/site-packages/blivet/devicetree.py", line 184, in _remove_device raise ValeError("Device %s not in tree" % dev.name)e
> ...
>
> The exact same line raised alreeady an error when trying to install rc5 on two other lenovo laptops (t430 and
> l560) with several different usb drives as targets.
>
> So at this point, i am a bit without clue what else to try to get qubes installed and am wondering
> a bit what causes all the pther installations to work for all other users?

What partitioning layout have you chosen? All defaults?

Can you extract logs from that system? The error message should have a
button to switch you to text console, then you'll find full error
message in /tmp/anaconda-tb-(something) file. You might want to
review/edit this file before posting it - it contains a lot of details
about your hardware. If you want, you may send it just to my address
instead of mailing list.

- --
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEEhrpukzGPukRmQqkK24/THMrX1ywFAlqzdEUACgkQ24/THMrX
1yzHfQf/bq/7HDnNSZkV+Ros0gHFWRvWkw94BnFVGNWVZoS5QzmANdKzSUXBQau8
0wbnUn2YYVpV/R8IUkJFoNtCrx33yVjtxd/l0Kou1ltBFfpF+LQy5o+C5Lm+6jiB
X/G7XJdrjwTGelAS0+H1ytZS6/qPseOCXMhXe1moezZkRbZjf8EoYmbfg7+vnloj
TFzzj6LjvjNbkgwwm4E/Qu661RAQbc2REdwO/jmGjV34GBnuVvg0v2ISbcPgauDu
RtPPXD82Zn6Jlokt0w3/NO0twtv/wL5q8W8j4mu2sSkQIjXOEssyjkYX49oi1qQb
mDH8dn9ZZde1bCU4YcKQKx33GuSMfA==
=Q6Y/
-----END PGP SIGNATURE-----

[kai....@gmail.com]

[...]

> Can you extract logs from that system? The error message should have a
> button to switch you to text console, then you'll find full error
> message in /tmp/anaconda-tb-(something) file. You might want to
> review/edit this file before posting it - it contains a lot of details
> about your hardware. If you want, you may send it just to my address
> instead of mailing list.
>
> - --
> Best Regards,
> Marek Marczykowski-Górecki
> Invisible Things Lab

Thank you for your offer, Marek. Pls see your email. I send you two emails, one with some screen shots and another one with the complete logs.

Looking forward hearing from you.
All the best
Kai

[kai....@gmail.com]

And, btw, yes I am/was using default paritioning.

The same error occured both when trying to install from an empty samsung ssd, freshly arrived and unpacked from amazon, as well as when i tried to install q4 on the same samsung drive after i had susccessfully installed qubes 3.2 on it (which worked fine).

all the best
kai

[Marek Marczykowski-Górecki]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On Fri, Mar 30, 2018 at 01:50:07AM +0200, Marek Marczykowski-Górecki wrote:
> On Thu, Mar 29, 2018 at 11:56:12AM -0700, kai....@gmail.com wrote:
> > greetings,
> >
> > i copied the current iso (tried it.both with rc5 and with today final official iso) to a 32gb usb stick
> > and made my lenovo x220 boot from it. all went well until i choosed to habe the newly installed
> > samsung 512gb ssd as target (it was listed in the graphic menu of the available targets).
> > the system kind of halted for a second or two and then throwed an
> > anaconda 25.20.9-12 exception report
> > Trace back (most recent file first):
> >
> > File "/usr/python3.5/site-packages/blivet/devicetree.py", line 184, in _remove_device raise ValeError("Device %s not in tree" % dev.name)e
> > ...
> >
> > The exact same line raised alreeady an error when trying to install rc5 on two other lenovo laptops (t430 and
> > l560) with several different usb drives as targets.
> >
> > So at this point, i am a bit without clue what else to try to get qubes installed and am wondering
> > a bit what causes all the pther installations to work for all other users?
>
> What partitioning layout have you chosen? All defaults?
>
> Can you extract logs from that system? The error message should have a
> button to switch you to text console, then you'll find full error
> message in /tmp/anaconda-tb-(something) file. You might want to
> review/edit this file before posting it - it contains a lot of details
> about your hardware. If you want, you may send it just to my address
> instead of mailing list.

According to logs, "sdc4" is your installation source. Which is a bit
unusual - installer expect the image to be written to the device
directly, not one of partitions.
While the error message should definitely be improved, the problem is in
how installation USB stick is prepared.

- --
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEEhrpukzGPukRmQqkK24/THMrX1ywFAlq0mHEACgkQ24/THMrX
1yyyLQf9GlXm+3OcSKZ8xvcTOXSxvFloDqa1LqYUln9tDVrGVV+IaxazXIFXQtNm
VD/OjTrHSayNVd0v0LtHGuIO9ElbSXh8MQI24xmaz8HgzO1n2MKMfcHRuMiQteL7
SzPdts6RJVZbRXhH3bwW5GvegFZcmP01nsb8Q8aYTlMqXZujrE/00KGOqsEYIGzN
e+Xt17azk7uVq29rlxJ5BIbKP8TorkplcOViu+vKk6MKzpKrIfhGnFR/3RyaFjcM
Dtyh5dwj9DcKhtH9MfwaowaNnYuJJ96Hkxmwqtk/6lEjI0RSL0FTwUSstlgla+HN
mS6HNvRj1HbIQvoQI9FmntRL9DXx5g==
=Qjs0
-----END PGP SIGNATURE-----

[kai....@gmail.com]

Hi Marek,

I am using this tool http://www.easy2boot.com/
to create my bootable usb, it is very easy to use, you just copy one or more iso image on the usb in the correct directory (e.g. linux or windows) and then run a little windows cmd script and the usb is ready for use. it has an inbuilt automatic menu, where it offers all the isos for bootng at runtime. so easy to create, maintain and to use. and free.

However, if this realy is the case, it explains why I constantly fail to install qubes 4 iso images with it, while all other people, using different tools, aparently do not fail. So may be i need to use rufus or another tool like that..

The funny thing is that it works with Qubes 3.2 installer, but not with Qubes 4.0 installer. So something must have gone worse with Qubes 4 installer, compared to Qubes 3.2 instaler.

All the best
Kai