/dev/sdb2 cannot be mounted or /srv/diskXXX is busy error - Cannot mount one of my disks

    • /dev/sdb2 cannot be mounted or /srv/diskXXX is busy error - Cannot mount one of my disks

      Hello to the forum. I tried searching for the topic of "not being able to mount" but the topics I saw are either related to RAID (which I don't have) or not really relevant.
      Long story short: I have been running OMV 3.0.77 with 3 disks: /dev/sda1 the main drive where I run debian/OMV and /dev/sdb and /sdc my 2 drives with ext4 (not raid, I have setup an rsync backup overnight).

      Everything has been running smoothly until today, when I booted up the NAS I could not access my SMB shares. Looking into OM web interface I see that sdb2 is not mounted. When trying to mount (either from GUI or SSH) I get the following message:

      Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C; mount -v --source '/dev/sdb2' 2>&1' with exit code '32': mount: /dev/sdb2 is already mounted or /srv/dev-disk-by-id-ata-Hitachi_HDS721010DLE630_MSE5235V0KU94E-part2 busy

      The disk is not mounted (since mount command returns only /dev/sda1 and /dev/sdc2). Command blkid returns:

      /dev/sda1: UUID="ddaf4f07-c50f-41c8-b1da-d1599c5cbfda" TYPE="ext4" PARTUUID="6f668dc7-01"
      /dev/sda5: UUID="d3ba9191-b42c-4b0a-9b79-6172f1cf35f0" TYPE="swap" PARTUUID="6f668dc7-05"
      /dev/sdb2: UUID="c7bf35bc-0276-454a-b2cb-d5750ce3c91e" TYPE="ext4" PARTUUID="22d354ff-02"
      /dev/sdc2: UUID="9bdcb397-6854-4e3d-867a-8a9160c2e2d4" TYPE="ext4" PARTUUID="08ca6e72-02"

      Trying to use e2fsck I get:

      e2fsck 1.43.3 (04-Sep-2016)
      /dev/sdb2 is in use.

      I disabled the SMB shares (in case this had to do something with the mounth) but nothing really changed. Still cannot mount the drive. The PC boot menu HDD diagnostics return no error or indicate any fault. Running the SMART test on the device from OMV GUI returns no errors in the self-test logs. The extended information is below (trimmed down in order to be <10K chars for the forum). Any help is appreciated. I could wipe the disk and copy from the other (so no data loss) but I would try to find another solution if I can avoid wiping.

      smartctl 6.4 2014-10-07 r4002 [x86_64-linux-4.9.0-0.bpo.3-amd64] (local build)
      Copyright (C) 2002-14, Bruce Allen, Christian Franke, smartmontools.org

      === START OF INFORMATION SECTION ===
      Model Family: Hitachi Deskstar 7K1000.D
      Device Model: Hitachi HDS721010DLE630
      smartctl 6.4 2014-10-07 r4002 [x86_64-linux-4.9.0-0.bpo.3-amd64] (local build)
      Copyright (C) 2002-14, Bruce Allen, Christian Franke, smartmontools.org

      SMART Extended Comprehensive Error Log Version: 1 (1 sectors)
      No Errors Logged

      SMART Extended Self-test Log Version: 1 (1 sectors)
      Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
      # 1 Short offline Completed without error 00% 27808 -
      # 2 Short offline Completed without error 00% 27733 -
      # 3 Short offline Completed without error 00% 27660 -
      # 4 Short offline Completed without error 00% 27614 -
      # 5 Short offline Completed without error 00% 27585 -
      # 6 Short offline Completed without error 00% 27398 -
      # 7 Short offline Completed without error 00% 27342 -
      # 8 Short offline Completed without error 00% 27225 -

      SMART Selective self-test log data structure revision number 1
      SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS
      1 0 0 Not_testing
      2 0 0 Not_testing
      3 0 0 Not_testing
      4 0 0 Not_testing
      5 0 0 Not_testing
      Selective self-test flags (0x0):
      After scanning selected spans, do NOT read-scan remainder of disk.
      If Selective self-test is pending on power-up, resume after 0 minute delay.

      SCT Status Version: 3
      SCT Version (vendor specific): 256 (0x0100)
      SCT Support Level: 1
      Device State: DST executing in background (3)
      Current Temperature: 38 Celsius
      Power Cycle Min/Max Temperature: 36/39 Celsius
      Lifetime Min/Max Temperature: 16/51 Celsius
      Under/Over Temperature Limit Count: 0/0


      Device Statistics (GP Log 0x04)
      Page Offset Size Value Description
      1 ===== = = == General Statistics (rev 1) ==
      1 0x008 4 318 Lifetime Power-On Resets
      1 0x010 4 27876 Power-on Hours
      1 0x018 6 13525125093 Logical Sectors Written
      1 0x020 6 136134359 Number of Write Commands
      1 0x028 6 656041885601 Logical Sectors Read
      1 0x030 6 1937580201 Number of Read Commands
      3 ===== = = == Rotating Media Statistics (rev 1) ==
      3 0x008 4 13782 Spindle Motor Power-on Hours
      3 0x010 4 13782 Head Flying Hours
      3 0x018 4 2728 Head Load Events
      3 0x020 4 0 Number of Reallocated Logical Sectors
      3 0x028 4 163 Read Recovery Attempts
      3 0x030 4 18 Number of Mechanical Start Failures
      4 ===== = = == General Errors Statistics (rev 1) ==
      4 0x008 4 0 Number of Reported Uncorrectable Errors
      4 0x010 4 0 Resets Between Cmd Acceptance and Completion


      SATA Phy Event Counters (GP Log 0x11)
      ID Size Value Description
      0x0001 2 0 Command failed due to ICRC error
      0x0002 2 0 R_ERR response for data FIS
      0x0003 2 0 R_ERR response for device-to-host data FIS
      0x0004 2 0 R_ERR response for host-to-device data FIS
      0x0005 2 0 R_ERR response for non-data FIS
      0x0006 2 0 R_ERR response for device-to-host non-data FIS
      0x0007 2 0 R_ERR response for host-to-device non-data FIS
      0x0009 2 4 Transition from drive PhyRdy to drive PhyNRdy
      0x000a 2 3 Device-to-host register FISes sent due to a COMRESET
      0x000b 2 0 CRC errors within host-to-device FIS
      0x000d 2 0 Non-CRC errors within host-to-device FIS
    • Hi,

      Apparently the command suggested seems to work for NTFS volumes (but thanks for the suggestion anyway). I tried dmesg | tail and it said "ext4-fs couldn't mount as ext2 due to feature incompatibilities". Checking fstab had the volume as ext2 (and not ext4).

      No clue what happened and fstab changed, but at least now everything is back to normal!