Devuan bug report logs - #81
shutdown does not unmount usb hard drive properly - drive will not remount at boot without fsck first

Reply or subscribe to this bug.

Toggle useless messages

Message #5 received at submit@bugs.devuan.org (full text, mbox, reply):

Package: sysvinit-core
Version: 2.88dsf-59.2+devuan2

After I execute a shutdown, the next boot does not mount the usb drive 
partition even though it is in the fstab.

The /var/log/messages file shows:

May 23 11:07:37 devuan kernel: [  414.245986] FAT-fs (sda1): Volume was 
not properly unmounted. Some data may be corrupt. Please run fsck.

When I fsck the partition I get the following output:

pi@devuan:~$ sudo fsck -V /dev/sda1
[sudo] password for pi:
fsck from util-linux 2.25.2
[/sbin/fsck.vfat (1) -- /media/pi/E915-F57C] fsck.vfat /dev/sda1
fsck.fat 3.0.27 (2014-11-12)
0x41: Dirty bit is set. Fs was not properly unmounted and some data may 
be corrupt.
1) Remove dirty bit
2) No action
? 1
Got 12726272 bytes instead of 122036412 at 122060800

It happens like this every single time I shutdown and reboot.


I am using the devuan version for raspberry pi 3.

Linux devuan 4.6.3-gb48d47a #1 SMP Thu Oct 13 00:34:22 CEST 2016 aarch64 
GNU/Linux

I downloaded the img file from 
https://files.devuan.org/devuan_jessie/embedded/ on 5/21/2017.

I ran sudo apt-get update and upgrade after installation on the 
raspberry pi 3.


If you need more information, or if I need to contact someone else about 
this, then please let me know.

Thanks you.

Message #10 received at 81@bugs.devuan.org (full text, mbox, reply):

It appears that the problem was with fsck.  It did not remove the dirty 
bit even though that option was selected.  I ran it with the -a option 
and now it is fixed.  I still cannot get the partition to mount at boot, 
but that is some other problem.

My apologies for the confusion.

Message #15 received at 81@bugs.devuan.org (full text, mbox, reply):

Hi,

no need to apologise. Better filing a bug report, even if you are
unsure whether the bug is there, than avoiding to file one, even if
you are sure the bug is there ;)

Thanks.

Message #20 received at 81-close@bugs.devuan.org (full text, mbox, reply):

closed

Message #21 received at 81-close@bugs.devuan.org (full text, mbox, reply):

[Message part 1 (text/html, inline)]

Message #27 received at 81-close@bugs.devuan.org (full text, mbox, reply):

[Message part 1 (text/html, inline)]

Message #32 received at 81@bugs.devuan.org (full text, mbox, reply):

[Message part 1 (text/html, inline)]

Send a report that this bug log contains spam.