error mounting disk

tazzz013 · 6. Oktober 2021

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?

cabrio_leo · 6. Oktober 2021

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.

tazzz013 · 6. Oktober 2021

Zitat von cabrio_leo

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.

i formatted the drive in EXT4

macom · 7. Oktober 2021

Wipe the drive from the GUI of OMV. Short will be enough. Then create a new ext4 file system and try to mount.

tazzz013 · 7. Oktober 2021

Zitat von macom

Wipe the drive from the GUI of OMV. Short will be enough. Then create a new ext4 file system and try to mount.

Macom, that's the exact way I have done it. Still get the error.

macom · 7. Oktober 2021

what is the output of

wipefs -n /dev/sdc

tazzz013 · 7. Oktober 2021

Zitat von macom

what is the output of

wipefs -n /dev/sdc

Code

root@openmediavault:~# wipefs -n /dev/sdc
DEVICE OFFSET        TYPE UUID LABEL
sdc    0x200         gpt
sdc    0x57541e95e00 gpt
sdc    0x1fe         PMBR

macom · 8. Oktober 2021

Try wipefs -a /dev/sdc make sure to use the correct device as this will erase all data on the device

https://linux.die.net/man/8/wipefs

tazzz013 · 8. Oktober 2021

Zitat von macom

what is the output of

wipefs -n /dev/sdc

ran the comand, device should as sdc1 in OMV

Code

root@openmediavault:~# wipefs -a /dev/sdc1
/dev/sdc1: 2 bytes were erased at offset 0x00000438 (ext4): 53 ef
root@openmediavault:~#

macom · 9. Oktober 2021

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.

tazzz013 · 9. Oktober 2021

Did as you said, same error

macom · 9. Oktober 2021

fdisk -l?

tazzz013 · 9. Oktober 2021

Zitat von macom

fdisk -l?

Code

root@openmediavault:~# fdisk -l
Disk /dev/sda: 3.7 TiB, 4000787030016 bytes, 7814037168 sectors
Disk model: HITACHI HUS72404
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/sdb: 74.5 GiB, 80000000000 bytes, 156250000 sectors
Disk model: ST3808110AS
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x951c56cc

Device     Boot     Start       End   Sectors  Size Id Type
/dev/sdb1  *         2048 139683839 139681792 66.6G 83 Linux
/dev/sdb2       139685886 156248063  16562178  7.9G  5 Extended
/dev/sdb5       139685888 156248063  16562176  7.9G 82 Linux swap / Solaris


Disk /dev/sdd: 3.7 TiB, 4000787030016 bytes, 7814037168 sectors
Disk model: HITACHI HUS72404
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


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


Disk /dev/md0: 3.7 TiB, 4000652787712 bytes, 7813774976 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/sde: 465.8 GiB, 500107862016 bytes, 976773168 sectors
Disk model: 418AS  External
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x95cc0009

Device     Boot Start       End   Sectors   Size Id Type
/dev/sde1        2048 976769023 976766976 465.8G  7 HPFS/NTFS/exFAT
root@openmediavault:~#

Alles anzeigen

macom · 9. Oktober 2021

Sorry, I am lost.

tazzz013 · 9. Oktober 2021

No worries, appropriate your help

Soma · 9. Oktober 2021

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 ???

Zitat von Install New disk

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"

tazzz013 · 10. Oktober 2021

Zitat von Soma
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 ???

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"
Alles anzeigen

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

Code

Welcome to fdisk (util-linux 2.33.1).
Changes will remain in memory only, until you decide to write them.
Be careful before using the write command.

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.

Command (m for help): p
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
Disklabel type: dos
Disk identifier: 0xaa3e053d

Alles anzeigen

Thanks for your reply.

Soma · 10. Oktober 2021

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

tazzz013 · 10. Oktober 2021

Zitat von Soma
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
Alles anzeigen

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

NAME   MAJ:MIN RM   SIZE RO TYPE  MOUNTPOINT
sda      8:0    0   3.7T  0 disk
└─md0    9:0    0   3.7T  0 raid1 /srv/dev-disk-by-label-RAID
sdb      8:16   0  74.5G  0 disk
├─sdb1   8:17   0  66.6G  0 part  /
├─sdb2   8:18   0     1K  0 part
└─sdb5   8:21   0   7.9G  0 part  [SWAP]
sdc      8:32   0   5.5T  0 disk
sdd      8:48   0   3.7T  0 disk
└─md0    9:0    0   3.7T  0 raid1 /srv/dev-disk-by-label-RAID
sde      8:64   0 465.8G  0 disk
└─sde1   8:65   0 465.8G  0 part

Alles anzeigen

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:~#

Code

root@openmediavault:~# mdadm --detail /dev/md0
/dev/md0:
           Version : 1.2
     Creation Time : Fri Mar 29 21:51:36 2019
        Raid Level : raid1
        Array Size : 3906887488 (3725.90 GiB 4000.65 GB)
     Used Dev Size : 3906887488 (3725.90 GiB 4000.65 GB)
      Raid Devices : 2
     Total Devices : 2
       Persistence : Superblock is persistent

     Intent Bitmap : Internal

       Update Time : Sun Oct 10 10:00:42 2021
             State : clean
    Active Devices : 2
   Working Devices : 2
    Failed Devices : 0
     Spare Devices : 0

Consistency Policy : bitmap

              Name : openmediavault:0  (local to host openmediavault)
              UUID : 1ac92da3:fccbcadf:9c4a9dc0:0083c1ca
            Events : 65726

    Number   Major   Minor   RaidDevice State
       0       8        0        0      active sync   /dev/sda
       1       8       48        1      active sync   /dev/sdd
root@openmediavault:~#

Alles anzeigen

Soma · 14. Oktober 2021

Sorry for the delay, but life took over.

Have you fixed it?

error mounting disk

Jetzt mitmachen!

Ähnliche Themen

Error after mounting and applying changes

[SOLVED] Help to mount a BTFRS Raid on OMV6

ZFS pool not mounting on boot

Error mounting disk " fstab or config.xml ? "

Problem with change mount point of /tmp