Drive possibly not being dismounted cleanly on reboot?

Topic: Drive possibly not being dismounted cleanly on reboot? (Read 2928 times) previous topic - next topic

0 Members and 1 Guest are viewing this topic.

Drive possibly not being dismounted cleanly on reboot?

01 January 2018, 07:30:58

Have an odd issue that I've not run into yet on any other distro even after hard shutdowns. Approximately every 5-10 reboots Artix can't seem to find my luks FDE partition. After entering in the passphrase it just says that the partition can't be found. Not a big deal because it can be fixed by booting off the Artix live USB, cryptsetup and mount the partition then cleanly cryptsetup close and reboot and it will start working properly again but just a hassle at this point if I'm in a rush. Anyone have any thoughts on a permanent fix? Because the decryption happens so early on I don't think there will be any logs to indicate what's going on.

Re: Drive possibly not being dismounted cleanly on reboot?

Reply #1 – 02 January 2018, 08:57:54

Can you post your /etc/fstab and your boot cmdline (It will be in some conf file in /boot, and will include vmlinuz, initrd, etc.)

Re: Drive possibly not being dismounted cleanly on reboot?

Reply #2 – 08 January 2018, 15:11:33

Sorry. I didn't receive an email letting me know there was a reply. I will post the requested information tonight.

Re: Drive possibly not being dismounted cleanly on reboot?

Reply #3 – 08 January 2018, 18:58:04

You must mean /boot/grub/grub.cfg and the menuentry you use to boot the specific partition up. More specifically the linux line would be of interest but the whole menuentry is best.

Re: Drive possibly not being dismounted cleanly on reboot?

Reply #4 – 04 February 2018, 17:55:49

Sorry again, been busy putting Artix on 20 other machines and documenting the live CD issues and workarounds for my friends that are also replacing their current setups with Artix.

Here is the line:

Code: [Select]

linux   /boot/vmlinuz-linux-lts root=UUID=XXXXXXXXXXXXXXXXXXXXXXXXXX rw  quiet cryptdevice=UUID=XXXXXXXXXXXXXXXXXXXXXXX:luks-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXX root=/dev/mapper/luks-XXXXXXXXXXXXXXXXXXXXXXXXXXX resume=/dev/mapper/luks-XXXXXXXXXXXXXXXXXXXXXXXX

(UUID info intentionally sanatized)

As I stated, this happens after the machine has been cleanly powered off. Booting the machine back up from the Artix LiveCD and cryptsetup luksOpen then luksClose then reboot lets the machine boot up properly without making any other changes. Also, this only happens on my Sony Vaio. I have a Lenovo Yoga 2 Pro & a Dell Precision 7510 that doesn't have this issue. Grepping for the drive in all the logs doesn't return lines indicating that there was any error of any type or that it was dismounted improperly.

And this is the contents of fstab although this happens at the grub prompt:

Code: [Select]

# /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>
UUID=XXXX-XXXX                            /boot/efi      vfat    defaults,noatime 0 2
/dev/mapper/luks-XXXXXXXXXXXXXXXXXXXXXXXXXXXX /              ext4    defaults,noatime,discard 0 1
/dev/mapper/luks-XXXXXXXXXXXXXXXXXXXXXXXXXXXX swap           swap    defaults,noatime,discard 0 2
tmpfs                                     /tmp           tmpfs   defaults,noatime,mode=1777 0 0

Re: Drive possibly not being dismounted cleanly on reboot?

Reply #5 – 25 February 2018, 23:28:34

Any ideas on this one? I just did an update on my Lenovo 2 Pro and now it has the same issue as the Vaio. Booted up fine before the update now it's having the same symptoms. Boots up to Luks prompt and after entering in the key correctly eventually times out and states "error: disk `cryptouuid/98173482573856091234asdfawuih2232` not found"

Re: Drive possibly not being dismounted cleanly on reboot?

Reply #6 – 26 February 2018, 16:17:15

This needs further investigation. Could you paste here the packages that got updated?

Re: Drive possibly not being dismounted cleanly on reboot?

Reply #7 – 28 February 2018, 15:42:45

My experience is this happens either when hardware acks up or when there is a process access the drive that can't be killed for some reason. It won't unmount if there are processes still pointing to files on the FS.

Re: Drive possibly not being dismounted cleanly on reboot?

Reply #8 – 28 February 2018, 23:37:21

Lately I've found it hard to manually unmount a partition and I get "device is busy" even though it is not busy as far as I can tell. So I wonder whether a delayed or impossible shutting down is caused by difficulty to unmount a volume.

Re: Drive possibly not being dismounted cleanly on reboot?

Reply #9 – 28 February 2018, 23:54:56

I've had the exact same thing happen on my desktop and my laptop. The desktop is dual boot, so I boot the OS on the other hard drive and fix the Artix HD with fsck. On the laptop, I gave up and installed a different distro.

Re: Drive possibly not being dismounted cleanly on reboot?

Reply #10 – 01 March 2018, 07:16:23

why would you instlaa a different system based on this minor problem?

Re: Drive possibly not being dismounted cleanly on reboot?

Reply #11 – 01 March 2018, 07:22:18

Quote from: fungalnet – on 28 February 2018, 23:37:21

Lately I've found it hard to manually unmount a partition and I get "device is busy" even though it is not busy as far as I can tell. So I wonder whether a delayed or impossible shutting down is caused by difficulty to unmount a volume.

lsof is your friend

Re: Drive possibly not being dismounted cleanly on reboot?

Reply #12 – 01 March 2018, 13:32:54

Thanks, that needs alot of studying on its own.
I did not download the gui for it as it needs all that jre (7,8,9) to run, I am tempted to temporarily as it seems very complex for meaningful use.
Early on I couldn't locate how lsof would point me to files open from a specific mount point, other than grep the mount point. I tried that while on chroot to a mounted installation and it produced nothing.

Re: Drive possibly not being dismounted cleanly on reboot?

Reply #13 – 02 March 2018, 06:30:44

how can you do this it in chroot? In fact, chroot can be hanging you. Usually, when this happens, it is a case of a moved log file which still have open handle, or an opened socket that was removed from the file system but still ghosted. Could be a database semiphore as well, or a mounted network drive that disapeared which confused the file system. I'm not sure why you care, though. Who cares if the filesystem hangs when the system goes down, as long as it goes down. These files systems are fairly bullet proof these days.

Re: Drive possibly not being dismounted cleanly on reboot?

Reply #14 – 02 March 2018, 11:51:56

[

Quote from: mrbrklyn – on 01 March 2018, 07:16:23

why would you instlaa a different system based on this minor problem?

Because I need a laptop that will boot when I turn it on. At home, if my desktop computer won't boot, I have another computer available to use. When I'm away from home, however, I need my laptop to be reliable. As much as I want it to be, Artix just isn't there yet.