On Thursday, 27 December 2018 20:49:14 UTC-3:30, John Goold wrote:
> On Thursday, 27 December 2018 16:24:23 UTC-3:30, Marek Marczykowski-Górecki
> wrote:
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA256
> >
> > On Wed, Dec 26, 2018 at 09:24:01AM -0800, John Goold wrote:
> > > On Thursday, 20 December 2018 22:02:00 UTC-3:30, John Goold wrote:
> > > > Attached is screenshot, taken under my current OS, showing OS and
> > > > hardware info.
> > > >
> > > > After spending much too much time trying to track the problem down
> > > > (using the 4.0, 4.0.1-RC1 and 4.0.1-RC2 ISOs) I discovered why getting
> > > > the installer to run was failing...
> > > >
> > > > I had to unplug my external monitor (connected via an HDMI port).
> > > >
> > > > I was then able to boot the install DVD and install to an external USB
> > > > (SSD) drive (Seagate 2 TB). The install completed (supposedly
> > > > successfully), but attempts to boot from the USB drive fail.
> > > >
> > > > The boot process starts, with text being displayed starting in the top
> > > > left corner of the screen. It progresses to a point, then the screen
> > > > goes black and my computer starts to reboot.
> > > >
> > > > I have searched the mailing list and have failed to find a solution
> > > > (hours spent doing this). A lot of people seem to end up in boot-loops,
> > > > using various hardware.
> > > >
> > > > The attached file shows the hardware. The following information about
> > > > the BIOS/Firmware may be relevant:
> > > >
> > > > * Legacy Boot is enabled
> > > > * Virtualization Technology is enabled
> > > >
> > > > During the install I setup a user account. I did not enable disk
> > > > encryption (I will leave that until after I can get Qubes to boot).
> > > >
> > > > Comment: This boot-loop problem (or similar boot-loop problems) seems
> > > > to be a major issue with installing Qubes 4.x. Each time I come across
> > > > a posting about it, there seem to be different suggestions (some of
> > > > which work on the particular hardware involved) and some of which do
> > > > not.
> > > >
> > > > I believe that I tried R3.1 about a year or so ago and that it booted
> > > > alright. I cannot remember why I did not follow through on adopting
> > > > Qubes (if I could not get my external monitor working, that would be a
> > > > deal-breaker).
> > > >
> > > > Suggestions would be appreciated. I will provide any additional
> > > > information I am capable of.
> > >
> > > This thread is getting verbose, so I have replied to the original post
> > > and will attempt a brief summary of the rest of the thread (for context):
> > >
> > > Determining what is happening would be facilitated by seeing any entries
> > > in log files (assuming the boot got far enough to log anything).
> > >
> > > That means checking files on the USB drive used as the target of the
> > > install and which causes the boot-loop when attempting to boot.
> > >
> > > Since the boot is failing, I cannot look at the log files under the
> > > booted Qubes OS, so instead I attempted to look for the log files when
> > > booted into another OS (Linux Mint 19.1).
> > >
> > > Qubes is using LVM to handle allocating disk space (presumably to
> > > facilitate being able to add additional physical disks to an existing
> > > Qubes install). There appeared, at first glance to be 3 Logical volumes:
> > >
> > > pool00
> > > root
> > > swap
> > >
> > > Linux Mint mounted the LV "swap" automatically, but not the other two.
> > > The other two appear not to be "activated" and mount attempts failed.
> > > Attempts to "activate" the LVs fail.
> > >
> > > After searching the Net for information on LVM, I came across an article
> > > that helped me understand the Qubes setup better…
> > >
> > > There is one Logical Volume Group called "qubes_dom0".
> > > Within that there is a Logical Volume, "swap", that is detected and
> > > mounted automatically by my Linux Mint installation.
> > > Additionally, there is a "Thin Pool" allocated that uses up the rest of
> > > the space in the Volume Group. It is distinguished by information
> > > displayed by the lvdisplay command ("LV Pool metadata" and "LV Pool
> > > data").
> > >
> > > Within that "thin pool", a logical volume, "root" has been created that
> > > uses all the disk space currently assigned.
> >
> > Yes, that's right.
> >
> > - From what I've seen in this thread, you did it right, but the system you
> > used didn't support thin volumes. You can try Qubes installation image,
> > there is recovery mode ("Rescue" in boot menu in legacy mode).
> >
> >
> > Other things you can try is to press ESC during boot to see more
> > messages than just progress bar. If that doesn't really help, try
> > editing boot entry in grub and remove "quiet" and "rhgb" options from
> > there. This should give you more details when exactly system reboots.
> >
> > - --
> > 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/THMrX1ywFAlwlLecACgkQ24/THMrX
> > 1yw98wf/e5BWkvOJQjrDpiB4DDpmRKAWvmZ3b/NssWOZgtBTMdYZxcRHaguoSQx2
> > hrMUKr5fLT3xy5fQYzt/OSjWjEsfbYoLfG8hx32+Zp0WDTpfSjon85/HerYlb8TW
> > pHS0lxT4y0sTDPx8HHy4O+0tFiYnHGeG9+JEpRx9JTxxJc6jX5hiw/DlaIldO9AD
> > /Qdi3aQjpU7qFMeQq0MebhHcaPME57lc87SkFlHhKnjEC8CsVpYSRiEKRx4ufREn
> > 7GKeiayK0bEqm9HZWsVJyn4XBTtEiL9kE5VK6RY6pv5Xx7cOEqzQiMchpSIa5/rQ
> > jcM+S2IXxzL+4t2epl8//xMziDFaGQ==
> > =s/Kn
> > -----END PGP SIGNATURE-----
>
> The messages scroll past much too quickly for me and disappear almost
> immediately the scrolling stops (i.e. as soon as the reboot starts).
>
> The last message (the only one I was able to read) said: "Starting switch
> boot" (it may have been "Start …" or "Started …".
>
> I do not know if that helps or if it is simply the message that says, "… OK,
> may as well reboot".
>
> I did wonder if the proble was because I was using a 2TB USB drive (SSD), so
> I also tried using a 500 GB external USB drive (HDD) — same result.
>
> My wife bought me a nice new computer for Christmas — it is an Intel NUC7i7.
> I'm just waiting for my local computer store to get in some more 16 GB DIMMs
> before trying it out (I am putting in the maximum of 32GB (I have the 500 GB
> SSD installed already) I'll see if I get any different results with a
> different computer.
The boot-loop problem appears to be a problem with the HP Spectre X360.
I have the NUC7i7BNH up and running. I was able to install R1.0.1 (stable) on
it. Since it will become my primary computer, I no longer care about the HP
Laptop (at least in terms of installing Qubes on it!). At present I am reliant
on the HP during the transition to Qubes — it is a bit of a bumpy road.
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/qubes-users/467941c1-6c54-4a59-824f-216ca2fa210c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
