Re: backb losing its mount point
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Darac Marjal <mailinglist@darac.org.uk> writes:
Thanks for replying Darac.
> On 31/03/2021 09:32, Sharon Kimble wrote:
>>
>> I'm hoping that you folks can help me with a problem that is now
>> happening reasonably regularly, actually twice.
>>
>> I have 2 data drives on my system /mnt/backa and /mnt/backb. Both are
>> 4tb drives, with backa being 2.74tb and backb 2.81tb.
>
> It might be helpful to see the relevant lines from your /etc/fstab.
>
- --8<--------------- current fstab ---------------start------------->8---
/dev/sda2 /mnt/backb ext4 defaults,nofail,x-gvfs-show 0 2
/dev/sdb2 /mnt/backa ext4 defaults,nofail,x-gvfs-show 0 2
- --8<---------------cut here---------------end--------------->8---
because the system originally showed this
- --8<--------------- original fstab ---------------start------------->8---
/dev/sda2 /mnt/backa ext4 defaults,nofail,x-gvfs-show 0 2
/dev/sdb2 /mnt/backb ext4 defaults,nofail,x-gvfs-show 0 2
- --8<---------------cut here---------------end--------------->8---
but for some reason it mounted backb on /dev/sda2 so to regain access I
changed it to what is currently showing in fstab.
>
>>
>> Backb is now regularly losing its mount point when I reboot, meaning
>> that only backa is mounted, and backb holds my restic backup.
>>
>> To regain access to backb I'm having to 'sudo e2fsck -y -b 32768
>> /dev/sdc2' which rebuilds the mount point such that I can mount it on
>> reboot, as backb.
>
> Firstly, it's usually better to run the "fsck" frontend, which will
> determine which filesystem you've got and run the appropriate backend,
> but I can see that you're passing advanced parameters here, so jumping
> straight to e2fsck isn't that unusual.
>
> Secondly, you're specifying "-b 32768" which is telling fsck to use a
> secondary superblock. Why is this? Generally, the primary superblock
> should be "good enough" to repair a filesystem. The man page does state
> that the primary superblock *should* be updated after the fixes are
> complete, so this shouldn't be necessary. So, why are you having to use
> a secondary superblock? Do you know what's wrong with the primary one?
>
When the problem originally occurred this is what i did
- --8<---------------cut here---------------start------------->8---
2184 2021-03-18 13:32:51 sudo mount /mnt/backb
2185 2021-03-18 13:39:33 mount
2186 2021-03-18 13:43:32 fdisk -l
2187 2021-03-18 13:43:46 sudo fdisk -l
2188 2021-03-18 13:48:05 sudo lshw
2189 2021-03-18 13:54:04 sudo fdisk /dev/sdc
2192 2021-03-18 14:10:04 sudo mount /mnt/backb
2193 2021-03-18 14:11:58 sudo fsck /mnt/backb
2194 2021-03-18 14:12:48 sudo e2fsck -b 32768 /mnt/backb
2195 2021-03-18 14:13:10 sudo e2fsck -b 32768 /dev/sdc
2196 2021-03-18 14:13:58 sudo e2fsck -b 8193 /dev/sdc
2197 2021-03-18 14:18:46 sudo mke2fs -n /dev/sdc2
2198 2021-03-18 14:19:16 sudo mke4fs -n /dev/sdc2
2199 2021-03-18 14:19:54 sudo mke2fs -n /dev/sdc2
2202 2021-03-18 14:02:17 glances
2203 2021-03-18 14:19:33 man mke2fs
2204 2021-03-18 13:54:51 sudo fdisk /dev/sdc2
2205 2021-03-18 13:31:11 sudo gparted
2210 2021-03-18 14:32:49 sudo mke2fs -n /dev/sdc2
2211 2021-03-18 14:34:32 sudo e2fsck
2212 2021-03-18 14:35:14 sudo e2fsck p
2213 2021-03-18 14:35:31 sudo e2fsck /dev/sdc -p
2214 2021-03-18 14:29:51 sudo gparted
2215 2021-03-18 14:36:28 sudo e2fsck -b 32768 /dev/sdc2
2216 2021-03-18 14:45:56 man e2fsck
2217 2021-03-18 14:46:38 sudo e2fsck -y -b 32768 /dev/sdc2
- --8<---------------cut here---------------end--------------->8---
>
>>
>> So how do I stop it happening again please? And what is the cause of it
>> all? Should I physically unmount the drives before rebooting?
>
> The answers you seek should already be logged somewhere. Try the following:
>
> $ journalctl -b -u mnt-backb.mount #
> This will show output from
> attempts to mount /mnt/backb since the current bootup
- --8<---------------cut here---------------start------------->8---
journalctl -b -u mnt-backb.mount
Hint: You are currently not seeing messages from other users and the system.
Users in groups 'adm', 'systemd-journal' can see all messages.
Pass -q to turn off this notice.
- -- Journal begins at Wed 2021-02-24 17:51:13 GMT, ends at Wed 2021-03-31 11:08:09 BST. --
- -- No entries --
- --8<---------------cut here---------------end--------------->8---
>
> $ journalctl -b -g sdc2 # This will grep
> the journal for all messages containing "sdc2" since the current bootup
>
- --8<---------------cut here---------------start------------->8---
journalctl -b -g sdc2
Hint: You are currently not seeing messages from other users and the system.
Users in groups 'adm', 'systemd-journal' can see all messages.
Pass -q to turn off this notice.
- -- Journal begins at Wed 2021-02-24 17:51:13 GMT, ends at Wed 2021-03-31 11:08:09 BST. --
- -- No entries --
- --8<---------------cut here---------------end--------------->8---
Thanks
Sharon.
- --
Debian 10.9, fluxbox 1.3.7, emacs 28.0.50, org 9.4.5
-----BEGIN PGP SIGNATURE-----
iQJPBAEBCgA5FiEELSc/6QwVBIYugJDbNoGAGQr4g1sFAmBkTz8bHGJvdWRpY2Nh
c0Bza2ltYmxlLnBsdXMuY29tAAoJEDaBgBkK+INb/y0P/1junuat+DjKqa0YMVXX
LVLGPj5KmQ2zzeWhKDHFz3jNF3jIAcwzyIMrbvYUly3GvJO7QGRtHWVqrcMi+Vzk
2xHw8o816vZzm6sQAxfhEABBJRSciDakRV0ATehjs/FtG6BQK4vbFytjtZ+xzkpN
e//YTu0ZLEe/sL3C94/hkA63FMAwuBrvB9PfCN8fgDNCfXefOdze8pfezghwkGhk
oPOGRicu3f1+g4BTh3/43DZHXGCUJ3p44wc8cJzf2UW+sBBDvPz6rZnOL6o1Veap
vZCGNkw6DeG3DEvBOS9YR+wE0NNhl0pHxlLYFB2GNabbEG2kKnAoPJLFtrZNhJTh
/jPiY2+io3LjaSw5Gv9lmCknH3AS/xn49u557KPIay0z8JjIq1qAf/gvHfesCJM2
UxNbSFbsJ6/A4sabIMaORsVQJ4xvGsm4+NTvgOJdMts6z00FxetpQLjNf6OW+QMb
NXeJjRKCmalWvSLR472e0NK4pGBVc+BbcR9xWFFIBoIp2hTsLebHbLa0d/q0Ps1X
YgaY19b2dFMLVBmsCklMvD6qcyJxxPOhSmdnaqBu7EE3XVeSyhqqUWhDC1LbagOx
RRGK8nSedkm+MNEu5T5cWYJJlbwLW5dBzUD/BkKh/eWg1Sn8QdWljQZDqNGYt4mm
z76dUwjI4uqJakEqjlq4h1A7
=2Qiz
-----END PGP SIGNATURE-----
Reply to: