You are not logged in.
Hello all, this is the scenario:
I have an HDD with BunsenLabs Hydrogen and Windows 7 running. When I wrote BL into the disk, I was short in my /root partition (10GB), so I extended it to 16GB in a live session.
Everything works OK, but! there is a message every time I boot, which starts like this:
[47.121457] ACPI Error: Evaluating _BCM failed (20160831/video-354)
Then it gives me a message which goes "A start job is running for dev-disk-by\...", and it lasts 1m30s. (It's a bit of an annoyance, since BL used to boot in ~10s.)
Here are my guesses:
1) ACPI Error doesn't have anything to do with the following error, but I still posted that line because it's displayed just before the actual problem, and might be helpful information.
2) The start job tries to find the former partition's UUID (which was 10GB) for a minute and a half, and then it gives up and boots normally.
I cannot find the correct log to post here, since dmesg doesn't show the information I see when I power on my lappy.
What info should I provide in order to let you help me? Needless to say I'm rather noobish.
Thanks in advance!
Last edited by dr1nkus (2018-03-31 18:14:36)
Offline
List the UUIDs of the new partition layout:
$ lsblk --fs
# Example output
NAME FSTYPE LABEL UUID MOUNTPOINT
sda
├─sda1 vfat 1671-4B03 /boot/efi
├─sda2 ext4 d065c185-5c4d-4ef9-b349-0748fda28088 /boot
├─sda3 crypto_LUKS 7bd8b0bc-46c7-4791-bf85-c96fb769f9d6
│ └─lvm LVM2_member jjGUzD-9OJt-TtfI-KiAm-fX1g-XSdO-FCaOMB
│ ├─wismut-root ext4 e23fcdb1-25e6-474b-91b5-19a61354ebb6 /
│ ├─wismut-home ext4 0fc0ed21-a225-47ce-a83b-ec708118dc79 /home
│ ├─wismut-library xfs 960d0a86-f71f-4149-9310-b22ae537ed89 /home/joj/lib
│ └─wismut-swap swap 92ab40b9-dd9b-435f-bbf1-189756441061 [SWAP]
├─sda4 ext4 7e3b8703-d3e5-4165-9e7a-80bc819ade2e
└─sda5
mmcblk0
└─mmcblk0p1 vfat 63E8-13ED
Keep the list open and open /etc/fstab in an editor as root. Ensure that any lines starting with UUID= have the correct UUIDs (especially for the partition you changed). Save and reboot (don't if there isn't any discrepancy).
Offline
Actually, the conflict occurred with the swap partition.
Also, is sda# relevant? Because that does not coincide either.
[EDIT] This is what I mean by 'no coincidence':
dr1nkus@BOX:~$ lsblk --fs
NAME FSTYPE LABEL UUID MOUNTPOINT
sda
├─sda1 ntfs Reservado para el sistema 12DEE6C5DEE69FE9
├─sda2 ntfs 821E5D5D1E5D4B75
├─sda3
├─sda5 ext4 ad0effa4-2363-42bf-ad34-b3a88bc85de1 /
├─sda6 ext4 da82d784-1d8a-4a99-8abf-2960a78dd4ad /home
└─sda7 swap 4a39feff-b65a-4bbd-b16d-e9b556bad26f
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
# / was on /dev/sda5 during installation
UUID=ad0effa4-2363-42bf-ad34-b3a88bc85de1 / ext4 errors=remount-ro 0 1
# /home was on /dev/sda7 during installation
UUID=da82d784-1d8a-4a99-8abf-2960a78dd4ad /home ext4 defaults 0 2
# swap was on /dev/sda6 during installation
UUID=2fdea8e7-2b99-4548-95d1-9c12b07f6fdf none swap sw 0 0
/dev/sr0 /media/cdrom0 udf,iso9660 user,noauto 0 0
Last edited by dr1nkus (2018-03-31 15:49:49)
Offline
Then just fixing the SWAP partition's UUID in fstab should be enough.
Offline
Thank you, @nobody, that did it. I'll add this trick to my experience log ^^
EDIT: grammar
Last edited by dr1nkus (2018-03-31 18:22:36)
Offline