Cant mount XFS

  • I went from OMV3 to 4 and i now i cant mount my old XFS drive from the Web Gui could it be done manually? and how?
    its the sdc1 disk, sdb1 is ext4 and works fine in the web gui.


    With blkid the sdc 4TB xfs is not metioned

    Code
    blkid
    /dev/sdb1: LABEL="WD3TB" UUID="185dfe11-4a83-48c6-95af-556300daabd6" TYPE="ext4" PARTUUID="423af684ae32-4495-a8fb-b0eb730c7a2d"
    /dev/sr0: UUID="2018-03-30-17-03-30-00" LABEL="OpenMediaVault" TYPE="iso9660" PTUUID="cc614a30" PTTYPE="dos"
    /dev/sda1: UUID="33ba4a6e-e231-4eaa-8b8b-ae31b89a3a7c" TYPE="ext4" PARTUUID="4e1e5fe7-01"
    /dev/sda5: UUID="35fdc9e7-a854-4e44-8338-24776b996360" TYPE="swap" PARTUUID="4e1e5fe7-05"

    I hope someone could help me.

    • Offizieller Beitrag

    With blkid the sdc 4TB xfs is not metioned

    This is why you can't mount it. What kind of system? What kernel?

    omv 7.0-32 sandworm | 64 bit | 6.5 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.9 | compose 7.0.9 | cputemp 7.0 | mergerfs 7.0.3


    omv-extras.org plugins source code and issue tracker - github


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • Code
    Linux OMV 4.17.0-0.bpo.3-amd64 #1 SMP Debian 4.17.17-1~bpo9+1 (2018-08-27) x86_64 GNU/Linux

    it is running on Proxmox VM with PCI sata Passthrough but tried it without Proxmox on a Standalone Omv4 install with the same results that the xfs isnt showing up

    • Offizieller Beitrag

    it is running on Proxmox VM with PCI sata Passthrough but tried it without Proxmox on a Standalone Omv4 install with the same results that the xfs isnt showing up

    Well, it isn't an OMV issue. I have a system with four xfs drives in it. I would run xfs_repair /dev/sdc1 You might need to add the -L argument as well.

    omv 7.0-32 sandworm | 64 bit | 6.5 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.9 | compose 7.0.9 | cputemp 7.0 | mergerfs 7.0.3


    omv-extras.org plugins source code and issue tracker - github


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

    • Offizieller Beitrag

    XFS_repair runs through without errors with the L argument

    Does it show up in blkid now? Any messages in dmesg? Does it show up if you reboot?

    omv 7.0-32 sandworm | 64 bit | 6.5 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.9 | compose 7.0.9 | cputemp 7.0 | mergerfs 7.0.3


    omv-extras.org plugins source code and issue tracker - github


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • I had a similar issue after upgrading from 3.x to 4.x.
    Issue was a ZFS signature on my 4 disks.
    Looks like the newer tools are a little bit more sensitive.
    Use "wipefs" (be very carefully) to remove the other signatures from the disk.


    I had to download and compile "util-linux-2.32" as the onboard wipefs told me
    it had removed the ZFS signatures, but it hadn't.


    Good luck,
    Thomas

  • no doestnt shows up ;/

    Code
    [   10.011005] sd 1:0:0:0: [sdc] 7814037168 512-byte logical blocks: (4.00 TB/3.64 TiB)
    [   10.011007] sd 1:0:0:0: [sdc] 4096-byte physical blocks
    [   10.011015] sd 1:0:0:0: [sdc] Write Protect is off
    [   10.011016] sd 1:0:0:0: [sdc] Mode Sense: 00 3a 00 00
    [   10.011028] sd 1:0:0:0: [sdc] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA

    cant find anything more sdc related in dmesg

    • Offizieller Beitrag

    I had to download and compile "util-linux-2.32" as the onboard wipefs told me
    it had removed the ZFS signatures, but it hadn't.

    Interesting. Hopefully that works. If someone doesn't want to compile a new version, I would boot systemrescuecd since it includes utl-linux-2.32

    omv 7.0-32 sandworm | 64 bit | 6.5 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.9 | compose 7.0.9 | cputemp 7.0 | mergerfs 7.0.3


    omv-extras.org plugins source code and issue tracker - github


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

    • Offizieller Beitrag

    no doestnt shows up ;/

    As mentioned by ananas, what is the output of:


    wipefs -n /dev/sdc
    wipefs -n /dev/sdc1

    omv 7.0-32 sandworm | 64 bit | 6.5 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.9 | compose 7.0.9 | cputemp 7.0 | mergerfs 7.0.3


    omv-extras.org plugins source code and issue tracker - github


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • Code
    wipefs -n /dev/sdc
    offset               type
    ----------------------------------------------------------------
    0x200                gpt   [partition table]
    
    
    0x3a38177f000        zfs_member   [filesystem]
    Code
    wipefs -n /dev/sdc1
    offset               type
    ----------------------------------------------------------------
    0x3a38167f000        zfs_member   [filesystem]
    
    
    0x0                  xfs   [filesystem]
                         LABEL: WD4TB
                         UUID:  d042e489-fa16-427c-ad4d-9a5ba374fbf8

    it realy shows zfs member the -n argument is without remove right? what would be the right arguments to remove that signature?

    • Offizieller Beitrag

    Then ananas was probably correct.


    wipefs -o 0x3a38177f000 /dev/sdc
    wipefs -o 0x3a38167f000 /dev/sdc1

    omv 7.0-32 sandworm | 64 bit | 6.5 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.9 | compose 7.0.9 | cputemp 7.0 | mergerfs 7.0.3


    omv-extras.org plugins source code and issue tracker - github


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

    • Offizieller Beitrag

    when i erease one the next is generated it changed the letter from 0x3a38177f000 to 0x3a38177e000

    What is the output of: zfs list

    omv 7.0-32 sandworm | 64 bit | 6.5 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.9 | compose 7.0.9 | cputemp 7.0 | mergerfs 7.0.3


    omv-extras.org plugins source code and issue tracker - github


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

    • Offizieller Beitrag

    command not found it says but i guess i never had that drive in zfs format

    Strange that there is a zfs signature on it then. Not sure why it keeps coming back either. I can't replicate any of this on my test VM.

    omv 7.0-32 sandworm | 64 bit | 6.5 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.9 | compose 7.0.9 | cputemp 7.0 | mergerfs 7.0.3


    omv-extras.org plugins source code and issue tracker - github


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

    • Offizieller Beitrag

    But i dont get why there were so many entrys the OMV wipefs only showed 1 entry thats why they "regenerated" after delete

    OMV is using util-linux 2.29 which is much older. I would guess deleting each one in OMV would have eventually fixed it.

    omv 7.0-32 sandworm | 64 bit | 6.5 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.9 | compose 7.0.9 | cputemp 7.0 | mergerfs 7.0.3


    omv-extras.org plugins source code and issue tracker - github


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

Jetzt mitmachen!

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