Fresh installation of OMV4, unable to mount old XFS drive, with data, that works on OMV2

  • Hello there,
    I do need a helping hand / guidance.
    I have a single 3TB drive with old data, XFS filesystem, and OMV4 on a USB stick (and another stick with OMV2).
    Under OMV4, I am able to see the 3TB disk under Disks, as sda, BUT this is not visible/available under Filesystems, so I am unable to mount it. I am able to create, but this will wipe out my disk/data. If I plug another disk/usb drive, I am able to mount it under Filesystems, but sda is still invisible.
    If I use OMV2, it's all ok, I am able to see/use the 3TB drive.
    I should be able to use putty so, perhaps a magical mount command will fix my issue on OMV4, if anyone will be able to assist me with this, please.
    I did a search in forum, with no luck. Additional data, I believe I formatted the drive with OMV1, xfs filesystem, 4 years ago.


    Thanks in advance!
    Daniel

  • Hi Tkaiser,


    Thanks for your quick reply.


    Here is the output:
    ==================================


    Linux Haspeu 4.13.0-0.bpo.1-amd64 #1 SMP Debian 4.13.13-1~bpo9+1 (2017-11-22) x86_64



    The programs included with the Debian GNU/Linux system are free software;
    the exact distribution terms for each program are described in the
    individual files in /usr/share/doc/*/copyright.



    Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
    permitted by applicable law.



    root@Haspeu:~# uname -a
    Linux Haspeu 4.13.0-0.bpo.1-amd64 #1 SMP Debian 4.13.13-1~bpo9+1 (2017-11-22) x86_64 GNU/Linux
    root@Haspeu:~# lsblk -a
    NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
    sda 8:0 0 2.7T 0 disk
    ââsda1 8:1 0 2.7T 0 part
    sdb 8:16 1 7.5G 0 disk
    ââsdb1 8:17 1 5.5G 0 part /
    ââsdb2 8:18 1 1K 0 part
    ââsdb5 8:21 1 2G 0 part [SWAP]
    root@Haspeu:~# blkid
    /dev/sdb1: UUID="8eacee61-ba53-415c-bba3-e3f5c2690793" TYPE="ext4" PARTUUID="d0e792a8-01"
    /dev/sdb5: UUID="2f1b59d1-6752-4ede-8912-b5d17d01c42a" TYPE="swap" PARTUUID="d0e792a8-05"
    root@Haspeu:~# smartctl -a /dev/sda
    smartctl 6.6 2016-05-31 r4324 [x86_64-linux-4.13.0-0.bpo.1-amd64] (local build)
    Copyright (C) 2002-16, Bruce Allen, Christian Franke, http://www.smartmontools.org



    === START OF INFORMATION SECTION ===
    Model Family: Western Digital Red
    Device Model: WDC WD30EFRX-68AX9N0
    Firmware Version: 80.00A80
    User Capacity: 3,000,592,982,016 bytes [3.00 TB]
    Sector Sizes: 512 bytes logical, 4096 bytes physical
    Device is: In smartctl database [for details use: -P show]
    ATA Version is: ACS-2 (minor revision not indicated)
    SATA Version is: SATA 3.0, 6.0 Gb/s (current: 3.0 Gb/s)
    SMART support is: Available - device has SMART capability.
    SMART support is: Enabled



    === START OF READ SMART DATA SECTION ===
    SMART overall-health self-assessment test result: PASSED



    General SMART Values:
    Offline data collection status: (0x00) Offline data collection activity
    was never started.
    Auto Offline Data Collection: Disabled.
    Self-test execution status: ( 0) The previous self-test routine completed
    without error or no self-test has ever
    been run.
    Total time to complete Offline
    data collection: (39240) seconds.
    Offline data collection
    capabilities: (0x7b) SMART execute Offline immediate.
    Auto Offline data collection on/off support.
    Suspend Offline collection upon new
    command.
    Offline surface scan supported.
    Self-test supported.
    Conveyance Self-test supported.
    Selective Self-test supported.
    SMART capabilities: (0x0003) Saves SMART data before entering
    power-saving mode.
    Supports SMART auto save timer.
    Error logging capability: (0x01) Error logging supported.
    General Purpose Logging supported.
    Short self-test routine
    recommended polling time: ( 2) minutes.
    Extended self-test routine
    recommended polling time: ( 394) minutes.
    Conveyance self-test routine
    recommended polling time: ( 5) minutes.
    SCT capabilities: (0x70bd) SCT Status supported.
    SCT Error Recovery Control supported.
    SCT Feature Control supported.
    SCT Data Table supported.



    SMART Attributes Data Structure revision number: 16
    Vendor Specific SMART Attributes with Thresholds:
    ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
    1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 0
    3 Spin_Up_Time 0x0027 181 178 021 Pre-fail Always - 5916
    4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 586
    5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0
    7 Seek_Error_Rate 0x002e 100 253 000 Old_age Always - 0
    9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 712
    10 Spin_Retry_Count 0x0032 100 100 000 Old_age Always - 0
    11 Calibration_Retry_Count 0x0032 100 100 000 Old_age Always - 0
    12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 470
    192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 43
    193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 542
    194 Temperature_Celsius 0x0022 125 114 000 Old_age Always - 25
    196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0
    197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 0
    198 Offline_Uncorrectable 0x0030 100 253 000 Old_age Offline - 0
    199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0
    200 Multi_Zone_Error_Rate 0x0008 100 253 000 Old_age Offline - 0



    SMART Error Log Version: 1
    ATA Error Count: 1
    CR = Command Register [HEX]
    FR = Features Register [HEX]
    SC = Sector Count Register [HEX]
    SN = Sector Number Register [HEX]
    CL = Cylinder Low Register [HEX]
    CH = Cylinder High Register [HEX]
    DH = Device/Head Register [HEX]
    DC = Device Command Register [HEX]
    ER = Error register [HEX]
    ST = Status register [HEX]
    Powered_Up_Time is measured from power on, and printed as
    DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
    SS=sec, and sss=millisec. It "wraps" after 49.710 days.



    Error 1 occurred at disk power-on lifetime: 202 hours (8 days + 10 hours)
    When the command that caused the error occurred, the device was active or idle.



    After command completion occurred, registers were:
    ER ST SC SN CL CH DH
    -- -- -- -- -- -- --
    04 51 01 00 00 00 00 Error: ABRT



    Commands leading to the command that caused the error were:
    CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
    -- -- -- -- -- -- -- -- ---------------- --------------------
    b0 d5 01 e1 4f c2 00 08 01:04:18.163 SMART READ LOG
    b0 d6 01 e0 4f c2 00 08 01:04:18.163 SMART WRITE LOG
    b0 d6 01 e0 4f c2 00 08 01:04:18.161 SMART WRITE LOG
    b0 d5 01 e0 4f c2 00 08 01:04:18.161 SMART READ LOG



    SMART Self-test log structure revision number 1
    Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
    # 1 Short offline Completed without error 00% 203 -
    # 2 Short offline Aborted by host 30% 203 -
    # 3 Short offline Aborted by host 90% 203 -
    # 4 Short offline Completed without error 00% 202 -
    # 5 Short offline Aborted by host 90% 202 -



    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.



    root@Haspeu:~#
    ============================================================


    I am attaching a screenshot from OMV4 File System Menu, so you may see that sda1 is not visible, although it exists, so I am unable to mount it, using the GUI.


    Thank you for your time!


    Regards,
    Daniel

  • Ok. Got it.
    I will check back if a new kernel (4.14?) will be implemented then I will try upgrading again, patch my OMV4 and see if My WD Red will be back.
    Till then, I'll stay on OMV2 as it does the job nicely.


    Have a good day!
    Daniel

  • i have some similar Problem i switched from OMV3 to OMV4 cause i switched from usb3.0 boot drive to sata ssd.
    And now one HDD (WD30EFRX) with ext4 is correctly mentioned in filesystem tab but another one with XFS is not (WD40EFRX).
    Kernel Problem too or other problem?

Jetzt mitmachen!

Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!