On Saturday, 22 December 2018 13:53:19 UTC-3:30, awokd  wrote:
> John Goold:
> > I should have been clearer in indicating how far the boot process got:
> > 
> > The text messages were displayed starting in the top left corner of the 
> > screen until the screen cleared and the Qubes Q-logo was displayed with a 
> > progress bar underneath.
> > 
> > The boot process continued until the progress indicator was about 1/4 to 
> > 1/3 of the way across, then the screen went black and my computer starts to 
> > reboot.
> > 
> Did the 4.0 installer reboot in the same spot? I've heard of this 
> happening with newer kernels sometimes, but the one in the original 
> release is older. Also, if you're getting that far there might be 
> something in the log files. Boot in rescue mode if you can (or another 
> distribution), mount the system disk and check.

@awokd Thank you very much for responding — I do appreciate the effort.

Here is my attempt to find the log file(s). I am booted in another distribution 
(Linux Mint 19.1 64-bit Cinnamon):

I used "sudo" to become root and then:

root@JRGsHPSpectre:/dev/qubes_dom0# lvmdiskscan
  /dev/qubes_dom0/swap [       7.48 GiB] 
  /dev/sda1            [     200.00 MiB] 
  /dev/sda2            [     <27.95 GiB] 
  /dev/sda3            [     428.30 GiB] 
  /dev/sda4            [       9.31 GiB] 
  /dev/sdb1            [     500.00 MiB] 
  /dev/sdb2            [      <1.82 TiB] LVM physical volume
  1 disk
  5 partitions
  0 LVM physical volume whole disks
  1 LVM physical volume
root@JRGsHPSpectre:/dev/qubes_dom0#

So there is the Qubes swap partition (7.48 GiB). /dev/sdb2 is the USB disk 
drive that was the target of the Qubes install.

lvdisplay >> ~john/temp/LVM-Info.txt  # result below

  --- Logical volume ---
  LV Name                pool00
  VG Name                qubes_dom0
  LV UUID                fWWjqo-5OdP-J5pO-obIu-Is0u-KekI-w5Dj26
  LV Write Access        read/write
  LV Creation host, time localhost.localdomain, 2018-12-20 13:49:26 -0330
  LV Pool metadata       pool00_tmeta
  LV Pool data           pool00_tdata
  LV Status              NOT available
  LV Size                <1.80 TiB
  Current LE             470795
  Segments               1
  Allocation             inherit
  Read ahead sectors     auto
   
  --- Logical volume ---
  LV Path                /dev/qubes_dom0/root
  LV Name                root
  VG Name                qubes_dom0
  LV UUID                EBmNyt-sCQi-5G4V-EpQQ-GLuJ-SCCY-MnWssJ
  LV Write Access        read/write
  LV Creation host, time localhost.localdomain, 2018-12-20 13:49:27 -0330
  LV Pool name           pool00
  LV Status              NOT available
  LV Size                <1.80 TiB
  Current LE             470795
  Segments               1
  Allocation             inherit
  Read ahead sectors     auto
   
  --- Logical volume ---
  LV Path                /dev/qubes_dom0/swap
  LV Name                swap
  VG Name                qubes_dom0
  LV UUID                aLPIfF-1EHL-5a1X-ejaj-DNdK-yHk2-TCLZXH
  LV Write Access        read/write
  LV Creation host, time localhost.localdomain, 2018-12-20 13:49:28 -0330
  LV Status              available
  # open                 0
  LV Size                7.48 GiB
  Current LE             1915
  Segments               1
  Allocation             inherit
  Read ahead sectors     auto
  - currently set to     256
  Block device           253:0
   
This appears to show 3 logical volumes: pool00, root and swap (which appears to 
be mounted). Note that pool00 and root both have an "LV Status" of "NOT 
available".

I created a mount point, /mnt/lvroot and then attempted to mount the root 
logical volume:

root@JRGsHPSpectre:/dev/qubes_dom0# ls -l /mnt
total 4
drwxr-xr-x 2 root root 4096 Dec 22 17:23 lvroot
root@JRGsHPSpectre:/dev/qubes_dom0#

root@JRGsHPSpectre:/dev/qubes_dom0# mount /dev/qubes_dom0/root /mnt/lvroot -o 
ro,user
mount: /mnt/lvroot: special device /dev/qubes_dom0/root does not exist.
root@JRGsHPSpectre:/dev/qubes_dom0#

Well, so much for that :(

Let us see if we can make the other logical volumes active:

root@JRGsHPSpectre:/dev/qubes_dom0# vgchange --activate y --force qubes_dom0
  /usr/sbin/thin_check: execvp failed: No such file or directory
  Check of pool qubes_dom0/pool00 failed (status:2). Manual repair required!
  /usr/sbin/thin_check: execvp failed: No such file or directory
  1 logical volume(s) in volume group "qubes_dom0" now active
root@JRGsHPSpectre:/dev/qubes_dom0#

Well, I guess I am out of my depth with LVM or the install did not create the 
LVM group/volumes/<whatever> correctly.  :(

-- 
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 [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/79b8fff1-5971-48c5-b1e4-2e4defab9cd1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to