error mounting disk

  • I am trying to to add a brand new 6TB sata hard disk to my system to use for rsync to back up to. I create the file system in OMV GUI, runs for ever but does finish with no issue. When I try to mount the drive, I get and error message with i have no clue what it means. Was hoping someone does. Thanks


    Code
    Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; mount -v --source '/dev/disk/by-uuid/7a4bd6af-2ed6-4794-bc01-101d4fd0543e' 2>&1' with exit code '12': NTFS signature is missing. Failed to mount '/dev/sdc1': Invalid argument The device '/dev/sdc1' doesn't seem to have a valid NTFS. Maybe the wrong device is used? Or the whole disk instead of a partition (e.g. /dev/sda, not /dev/sda1)? Or the other way around?
  • Which file system do you intend to use? NTFS or some kind of Linux file system? For rsync usage I would prefer a Linux file system like EXT4.

    If you go that way too first you should quick wipe the disk and then format it with a Linux file system.

    OMV 3.0.100 (Gray style)

    ASRock Rack C2550D4I C0-stepping - 16GB ECC - 6x WD RED 3TB (ZFS 2x3 Striped RaidZ1) - Fractal Design Node 304 -

    3x WD80EMAZ Snapraid / MergerFS-pool via eSATA - 4-Bay ICYCube MB561U3S-4S with fan-mod

  • Sorry, to wipe the complete device use wipefs -a /dev/sdc


    sdc1 is the first partition on the device sdc


    Please note: if you change the sata port on your motherboard, the device name will change. For example sdc might become sdb


    Then create a new filesystem using the GUI of OMV.

  • fdisk -l?

  • Which drives are on your RAID array? (At least, it show's a /dev/md0 hence the assumption)

    I see 2x 3.7Tb (/dev/sdb && /dev/sdd) that probably are the one's (if you really DO have a RAID).


    If I'm seeing this correctly (and you DO have a RAID) maybe it's possible that, when you plugged the 6Tb Disk, the drives on the RAID become messed ???


    1. Install the new disk in your machine. Be aware that some SATA controllers carry over the idiotic notion of master and slave from IDE days. If your motherboard has such a controller, you might find that SAT0 = sda, SATA1 = sdc, SATA2 = sdb, and SATA3 = sdd or some other screwy ordering like that. Also, the SATA drives might just collide with IDE devices such as a DVD or CD drive.



    If you don't have a RAID, maybe it's just a case that the drive wasn't properly "initialized"

    Code
    Disk /dev/sdc: 5.5 TiB, 6001175126016 bytes, 11721045168 sectors
    Disk model: ST6000DM003-2CY1
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 4096 bytes
    I/O size (minimum/optimal): 4096 bytes / 4096 bytes

    Check that it's still in the same "/dev"

    fdisk -l /dev/sdc


    Check the partition table of the drive and see if there are any errors.

    fdisk /dev/sdc and then press "p"

  • Yes, I am runnning raid on the 2 x 3.7TB drives. Here is the info from the commands you wanted me to run.


    Code
    root@openmediavault:~# fdisk -l /dev/sdc
    Disk /dev/sdc: 5.5 TiB, 6001175126016 bytes, 11721045168 sectors
    Disk model: ST6000DM003-2CY1
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 4096 bytes
    I/O size (minimum/optimal): 4096 bytes / 4096 bytes

    Thanks for your reply.

  • According to lines #5 till #8, your disk didn't had a partition table created.

    Code
    Device does not contain a recognized partition table.
    The size of this disk is 5.5 TiB (6001175126016 bytes). DOS partition table format cannot be used on drives for volumes larger than 2199023255040 bytes for 512-byte sectors. Use GUID partition table format (GPT).
    Created a new DOS disklabel with disk identifier 0xaa3e053d.

    What is the output now of:

    fdisk -l /dev/sdc

    lsblk

    blkid


    And just for piece of mind:

    mdadm --detail /dev/md0

  • Soma, here is the output of the commands you wanted me to run. Hope it helps.


    Code
    root@openmediavault:~# fdisk -l /dev/sdc
    Disk /dev/sdc: 5.5 TiB, 6001175126016 bytes, 11721045168 sectors
    Disk model: ST6000DM003-2CY1
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 4096 bytes
    I/O size (minimum/optimal): 4096 bytes / 4096 bytes
    Code
    /dev/sda: UUID="1ac92da3-fccb-cadf-9c4a-9dc00083c1ca" UUID_SUB="1ba3b553-71cb-9121-72d4-7f7d9d4095d9" LABEL="openmediavault:0" TYPE="linux_raid_member"
    /dev/sdb1: UUID="67f8957f-4256-43ef-a546-498710a572b3" TYPE="ext4" PARTUUID="951c56cc-01"
    /dev/sdb5: UUID="e9fbcafa-57d3-4b1f-84fd-3817730f2d34" TYPE="swap" PARTUUID="951c56cc-05"
    /dev/sdd: UUID="1ac92da3-fccb-cadf-9c4a-9dc00083c1ca" UUID_SUB="5c462bbe-2613-4aa3-9102-cb1917d7df2d" LABEL="openmediavault:0" TYPE="linux_raid_member"
    /dev/md0: LABEL="RAID" UUID="012310dd-0a1d-4e68-bf83-079109e5f9ec" TYPE="ext4"
    /dev/sde1: UUID="8A58FCA958FC9563" TYPE="ntfs" PARTUUID="95cc0009-01"
    root@openmediavault:~#
  • Sorry for the delay, but life took over.


    Have you fixed it?

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!