On 07/14/2016 05:43 PM, Facundo Curti wrote:
Hi list.
I'm having troubles to start qubes. When I start it says that a
partition is being used by a process.
As I was reading:
https://forums.opensuse.org/showthread.php/503587-Slow-boot-What-is-quot-A-start-job-is-running-for-dev-disk-by-quot
https://bbs.archlinux.org/viewtopic.php?id=161814
https://bbs.archlinux.org/viewtopic.php?id=196083
It is a problem in the swap partition, a bad configuration on /etc/fstab.
Recently I resized it... So the UUID should be changed
now I'm trying to edit /etc/fstab, but for some reason, I just can do
that chrooting the system (not just mount). When I mount the disk,
/etc/fstab is almost empty.
Anyway, I do that. But I still can not boot.
Here is my /etc/fstab:
----------------------------------------
# /etc/fstab
# Created by anaconda on Fri Jul 8 23:45:42 2016
#
# Accessible filesystems, by reference, are maintained under '/dev/disk'
# See man pages fstab(5), findfs(8), mount(8) and/or blkid(8) for more
info
#
/dev/mapper/luks-1d18c3c1-3456-420e-86d9-83c5aab56904
/ ext4 defaults,x-systemd.device-timeout=0 1 1
UUID=8ac79b31-fdfe-4c2d-b6da-8e91f12b0518 /boot
ext4 defaults 1 2
/dev/mapper/cryptedSwap swap swap
defaults,x-systemd.device-timeout=0 0 0
#/dev/mapper/luks-7a2436b4-6f22-46e6-b9d4-fc72b0913d17
swap swap defaults,x-systemd.device-timeout=0 0 0
---------------------------------------------
And here is my /etc/crypttab
---------------------------------------------
luks-1d18c3c1-3456-420e-86d9-83c5aab56904
UUID=1d18c3c1-3456-420e-86d9-83c5aab56904 none
cryptedSwap /dev/disk/by-partuuid/0319b6a9-5470-49b6-84ef-eac0f91546a0
/dev/urandom swap,cipher=aes-cbc-essiv:sha256,size=256
---------------------------------------------
I made the swap according this guide:
https://wiki.archlinux.org/index.php/Dm-crypt/Swap_encryption#Without_suspend-to-disk_support
But the error persist :/
The system starts in emergency mode
Some ideas plz?
--
Idea: You did not refresh your initramfs or grub.conf after making the
changes in fstab/crypttab. :)
If you can drop to a CLI when the boot process fails, maybe you can
decrypt the root partition, mount and chroot into it. Next, mount boot
partition at /boot, verify fstab and crypttab are correct and then run
the tools to refresh your boot partition. IIRC, they would be 'dracut
-H' and 'grub2-mkconfig -o /boot/grub2/grub.cfg'.
Chris
--
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/8d0a0013-37a4-85ba-c453-812f0ace9ca7%40openmailbox.org.
For more options, visit https://groups.google.com/d/optout.
