Posts by amstel

    Hi all,

    Long story short an electrician has tested my sockets (on and off), when I was out nad switched off my Raspberry Pi 3 with micro SD and WD RED 10TB EXT4 connected via USB (a dock with PSU), managed by Linux raspberrypi 4.19.118-v7+.

    Now the GUI shows filesystem /dev/disk/by-label/WD10 is missing.

    Now I know that i have to buy an UPS :]

    Please could you advise how to fix that?


    Filesystem '/srv/dev-disk-by-label-WD10' not mounted

    Jul 3 20:17:58 raspberrypi monit[983]: 'filesystem_srv_dev-disk-by-label-WD10' unable to read filesystem '/srv/dev-disk-by-label-WD10' state

    Jul 3 20:17:58 raspberrypi monit[983]: 'filesystem_srv_dev-disk-by-label-WD10' trying to restart

    Jul 3 20:17:58 raspberrypi monit[983]: 'mountpoint_srv_dev-disk-by-label-WD10' status failed (1) -- /srv/dev-disk-by-label-WD10 is not a mountpoint

    Jul 3 20:18:29 raspberrypi monit[983]: Filesystem '/srv/dev-disk-by-label-WD10' not mounted

    # lsblk


    sda 8:0 0 9.1T 0 disk

    mmcblk0 179:0 0 29.8G 0 disk

    ├─mmcblk0p1 179:1 0 2.4G 0 part

    ├─mmcblk0p2 179:2 0 1K 0 part

    ├─mmcblk0p5 179:5 0 32M 0 part

    ├─mmcblk0p6 179:6 0 256M 0 part /boot

    └─mmcblk0p7 179:7 0 27.1G 0 part /

    cat /etc/fstab

    proc /proc proc defaults 0 0

    /dev/mmcblk0p6 /boot vfat defaults 0 2

    /dev/mmcblk0p7 / ext4 noatime,nodiratime,defaults 0 1

    # a swapfile is not a swap partition, no line here

    # use dphys-swapfile swap[on|off] for that

    # >>> [openmediavault]

    /dev/disk/by-label/WD10 /srv/dev-disk-by-label-WD10 ext4 defaults,nofail,user_xattr,noexec,usrjquota=aquota.user,,jqfmt=vfsv0,acl 0 2

    # <<< [openmediavault]

    # fsck /dev/sda

    fsck from util-linux 2.33.1

    e2fsck 1.44.5 (15-Dec-2018)

    ext2fs_open2: Bad magic number in super-block

    fsck.ext2: Superblock invalid, trying backup blocks...

    fsck.ext2: Bad magic number in super-block while trying to open /dev/sda

    The superblock could not be read or does not describe a valid ext2/ext3/ext4

    filesystem. If the device is valid and it really contains an ext2/ext3/ext4

    filesystem (and not swap or ufs or something else), then the superblock

    is corrupt, and you might try running e2fsck with an alternate superblock:

    e2fsck -b 8193 <device>


    e2fsck -b 32768 <device>

    Not sure if I should proceed further with that command

    # e2fsck -b 8193