Add > 2,1 TB NTFS disks without partion or format.

[Zeeuus]

Hello everybody,

I had a win 7 desktop working as a fileserver and decided to make this a real fileserver. Hence the migration to Amahi.

As usual, there where a bit of confusion, but I read the docs and finally I got it installed.
Nice, but...

I had two 3TB disks with movies and series on it. Even tough I follwed (and successfully added my 2TB disk) https://wiki.amahi.org/index.php/Adding ... o_your_HDA I can't make these mountable?

Then I read https://wiki.amahi.org/index.php/Partitions_Over_2.1_TB but they where talking abot partitioning and formatting. I don't want to do that! Is there no other way than to blow all the info of the disk and start over... Seems a bit harch in my eyes. =-)

Please advice me.

[bigfoot65]

You should not need to partition and format the drives if they have existing data.

On the Adding a second hard drive to your HDA guidance, in the troubleshooting area it shows how to manually mount drives. Have you tried that?

[Zeeuus]

Thanks for the reply,

Yes I have tried to follow this, but I do think I get confused and mix things up.
If I list /dev/ I find these entries.

Code: Select all

brw-rw---- 1 root disk 8, 0 22 jun 00.55 sda brw-rw---- 1 root disk 8, 1 22 jun 00.55 sda1 brw-rw---- 1 root disk 8, 2 22 jun 00.55 sda2 brw-rw---- 1 root disk 8, 3 22 jun 00.55 sda3 brw-rw---- 1 root disk 8, 16 22 jun 00.55 sdb brw-rw---- 1 root disk 8, 17 22 jun 01.14 sdb1 brw-rw---- 1 root disk 8, 18 22 jun 00.55 sdb2 brw-rw---- 1 root disk 8, 32 22 jun 00.55 sdc brw-rw---- 1 root disk 8, 33 22 jun 00.55 sdc1 brw-rw---- 1 root disk 8, 34 22 jun 00.55 sdc2 brw-rw---- 1 root disk 8, 35 22 jun 00.55 sdc3 brw-rw---- 1 root disk 8, 36 22 jun 00.55 sdc4 brw-rw---- 1 root disk 8, 37 22 jun 00.55 sdc5 brw-rw---- 1 root disk 8, 38 22 jun 00.55 sdc6 brw-rw---- 1 root disk 8, 48 22 jun 00.55 sdd brw-rw---- 1 root disk 8, 49 22 jun 00.55 sdd1 brw-rw---- 1 root disk 8, 50 22 jun 00.55 sdd2 brw-rw---- 1 root disk 8, 51 22 jun 00.55 sdd3

As I understand sda is the disk and sda1 is a partition residing on previously stated disk, right?

My output from fstab:

Code: Select all

#cat /etc/fstab # # /etc/fstab # Created by anaconda on Sun Jun 21 23:25:21 2015 # # Accessible filesystems, by reference, are maintained under '/dev/disk' # See man pages fstab(5), findfs(8), mount(8) and/or blkid(8) for more info # UUID=018935a0-5d36-4d1a-aee1-033e4cda409f / ext4 defaults 1 1 UUID=3821d493-7120-4381-b67a-6efefcd09421 /boot ext4 defaults 1 2 UUID=6ed4b5e1-ea1a-459b-9ded-79cec0a391c8 /home ext4 defaults 1 2 UUID=b8a3a3b3-35b8-493d-9f90-15e89b156360 swap swap defaults 0 0 UUID=9C188A231889FD10 /var/hda/files/drives/drive1 ntfs-3g rw,user,fmask=0113,dmask=0002,uid=500,gid=100,noatime 1 2 UUID=01D0A1547681FEA0 /var/hda/files/drives/drive2 ntfs-3g rw,user,fmask=0113,dmask=0002,uid=500,gid=100,noatime 1 2

On the other hand my listing from /var/hda/files/drives/ shows this output.

Code: Select all

ls -l /var/hda/files/drives/ totalt 36 drwxrwxr-x 1 500 users 20480 22 jun 01.12 drive1 drwxrwxr-x 1 500 users 8192 20 jun 09.56 drive2 drwxr-xr-x 2 root root 4096 22 jun 00.34 drive3 drwxr-xr-x 3 root root 4096 21 jun 23.24 drive4

From SDA config I can see this:
WDC WD30EFRX-68EUZN0 /dev/sda 32
WDC WD20EARX-00PASB0 /dev/sdb 30
KINGSTON SV300S37A120G /dev/sdc 29
WDC WD30EFRX-68EUZN0 /dev/sdd 31

That would be correct from my perspective:
Western Digital 3TB /sda
Western Digital 2TB /sdb
Kingston SSD 120GB /sdc
Western Digital 3TB /sdd

Also this is the mappings:

Code: Select all

# ls -l /dev/disk/by-uuid/ totalt 0 lrwxrwxrwx 1 root root 10 22 jun 00.55 018935a0-5d36-4d1a-aee1-033e4cda409f -> ../../sdc6 lrwxrwxrwx 1 root root 10 22 jun 00.55 01D0A1547681FEA0 -> ../../sdb2 lrwxrwxrwx 1 root root 10 22 jun 00.55 2350b38f-a8b2-419b-b2e1-e395087e0c4f -> ../../sdc5 lrwxrwxrwx 1 root root 10 22 jun 00.55 3821d493-7120-4381-b67a-6efefcd09421 -> ../../sdc1 lrwxrwxrwx 1 root root 10 22 jun 00.55 6ed4b5e1-ea1a-459b-9ded-79cec0a391c8 -> ../../sdc2 lrwxrwxrwx 1 root root 10 22 jun 01.14 9C188A231889FD10 -> ../../sdb1 lrwxrwxrwx 1 root root 10 22 jun 00.55 b8a3a3b3-35b8-493d-9f90-15e89b156360 -> ../../sdc3

A nudge in the right direction would be much helpful.

[bigfoot65]

Ok so in the wiki guidance for disks with data, it states to skip the partition/format option and move to the Mount step. Did you do that and then run hda-diskmount?

If so, then it should have provided the necessary entries for /etc/fstab. By default each drive will be mounted as drive1, drive2, etc for the additional disks.

Looking at your current /etc/fstab, I see:
A. WDC WD20EARX-00PASB0 /dev/sdb 30 which is Western Digital 2TB /sdb1 partition mounted as drive 1
B. WDC WD20EARX-00PASB0 /dev/sdb 30 which is Western Digital 2TB /sdb2 partition mounted as drive 2

Do you have two partitions on the Western Digital 2TB drive?

Also the other drives (Kingston SSD 120GB /sdc and Western Digital 3TB /sdd) do not appear to be mounted. It also appears as if Western Digital 3TB /sda is the OS drive, correct?

It would probably be best if you started over. This can be done by removing the two entries from /etc/fstab and rebooting. Then run hda-diskmount and capture all that it finds.

If it does not catch the drives > 2.1 TB, then you will need to mount them manually. That is shown in the guidance under troubleshooting as I mentioned in the previous post.

Make sense?

This is something that takes time and must be carefully done to ensure you get the right mount points. I personally do it manually myself so I can name the mount points sdb, sdc, etc vs drive1, drive2.

I can try to assist if needed by giving you the entries you need to put in /etc/fstab.

[Zeeuus]

That makes sense.

I did skip to the mount section, as there is data I want to preserve and it makes no sense to wipe that.

But, I do not think that the disk that are mounted are the ones you mentioned.

I had ONLY the Kingston 120GB SSD plugged in when I installed Amahi (Just to be sure not to wipe the wrong disk.) So that is where my System is installed.

The second disk I attached was the WD 2TB and yes, it have at least two partitions as I can recall from my memory.

Then I attached the third and four physical disk (WD 3TB) and they had one large partition on each disk.

Ok so in the wiki guidance for disks with data, it states to skip the partition/format option and move to the Mount step. Did you do that and then run hda-diskmount?
yes
If so, then it should have provided the necessary entries for /etc/fstab. By default each drive will be mounted as drive1, drive2, etc for the additional disks.
Thats what I think, but...
Looking at your current /etc/fstab, I see:
A. WDC WD20EARX-00PASB0 /dev/sdb 30 which is Western Digital 2TB /sdb1 partition mounted as drive 1
B. WDC WD20EARX-00PASB0 /dev/sdb 30 which is Western Digital 2TB /sdb2 partition mounted as drive 2

Do you have two partitions on the Western Digital 2TB drive?
Yes
Also the other drives (Kingston SSD 120GB /sdc and Western Digital 3TB /sdd) do not appear to be mounted. It also appears as if Western Digital 3TB /sda is the OS drive, correct?
No, yes and no, see above
It would probably be best if you started over. This can be done by removing the two entries from /etc/fstab and rebooting. Then run hda-diskmount and capture all that it finds.
Fair, I'll do that
If it does not catch the drives > 2.1 TB, then you will need to mount them manually. That is shown in the guidance under troubleshooting as I mentioned in the previous post.

Make sense?
Very much, thanks!
This is something that takes time and must be carefully done to ensure you get the right mount points. I personally do it manually myself so I can name the mount points sdb, sdc, etc vs drive1, drive2.
Makes even more sense as there is to many parameters involved here, why rename things one more time?
I can try to assist if needed by giving you the entries you need to put in /etc/fstab.
I'll try this again as you already suggested above, and if I still get stuck, I'll post the output from hda-diskmount before editing fstab.

[Zeeuus]

So, I edited fstab and made a reboot.

When I ran hda-diskmount this was the output:

Code: Select all

[root@localhost ~]# hda-diskmount **************************************************************** Mounted /dev/sdb1 as '/var/hda/files/drives/drive5' You may want your system to mount it every time you boot. To do so, add this line VERY CAREFULLY to /etc/fstab and reboot: UUID=9C188A231889FD10 /var/hda/files/drives/drive5 ntfs-3g rw,user,fmask=0113,dmask=0002,uid=500,gid=100,noatime 1 2 **************************************************************** Mounted /dev/sdb2 as '/var/hda/files/drives/drive6' You may want your system to mount it every time you boot. To do so, add this line VERY CAREFULLY to /etc/fstab and reboot: UUID=01D0A1547681FEA0 /var/hda/files/drives/drive6 ntfs-3g rw,user,fmask=0113,dmask=0002,uid=500,gid=100,noatime 1 2 **************************************************************** Ignoring /dev/sda1 - already in /etc/fstab as UUID= **************************************************************** Ignoring /dev/sdc1 - already mounted Ignoring /dev/sdc1 - already in /etc/fstab as UUID=3821d493-7120-4381-b67a-6efefcd09421 **************************************************************** Ignoring /dev/sdc2 - already mounted Ignoring /dev/sdc2 - already in /etc/fstab as UUID=6ed4b5e1-ea1a-459b-9ded-79cec0a391c8 **************************************************************** Mounted /dev/sdc5 as '/var/hda/files/drives/drive7' (read-write) You may want your system to mount it every time you boot. To do so, add this line VERY CAREFULLY to /etc/fstab and reboot: UUID=2350b38f-a8b2-419b-b2e1-e395087e0c4f /var/hda/files/drives/drive7 ext4 defaults 1 2 **************************************************************** Ignoring /dev/sdc6 - already mounted Ignoring /dev/sdc6 - already in /etc/fstab as UUID=018935a0-5d36-4d1a-aee1-033e4cda409f **************************************************************** Ignoring /dev/sdd1 - already in /etc/fstab as UUID= **************************************************************** All Linux, Windows and Mac partitions on your disks have been mounted.

I do have a problem with this entry:

Mounted /dev/sdc5 as '/var/hda/files/drives/drive7' (read-write)
You may want your system to mount it every time you boot.
To do so, add this line VERY CAREFULLY to /etc/fstab and reboot:
UUID=2350b38f-a8b2-419b-b2e1-e395087e0c4f /var/hda/files/drives/drive7 ext4 defaults 1 2

This should be a NTFS, not an ext4 fs.
Hmmm, the plot thickenings....

As I understand sdc is really my 120 SSD disk that I installed the system on.
sdb is my 2TB disk with two partitions on it.
This leaves the two 3TB disk, they are then sda and sdd.
But what does this mean:

Ignoring /dev/sda1 - already in /etc/fstab as UUID=
Ignoring /dev/sdd1 - already in /etc/fstab as UUID=

Is this fedoras way of telling you to "no way I mount these..."

[bigfoot65]

The best way to get this sorted out is to only add one disk at a time. Edit /etc/fstab to only include your OS disk. I would recommend you unplug them completely from the MB as it will recognize anything plugged in as a device.

Remove all but the OS disk and one additional disk. I would also recommend you remove drive1, drive2, drive3, etc folders in /var/hda/files/drives. This will ensure you start off at drive1 again.

Then reboot. Once things come back up, run hda-diskmount and the results should show the additional disk.

If the disk does not show up, then you will have to manually mount it using the troubleshooting guidance in the wiki article.

Sometimes doing them all at once causes issues. By doing them one at a time it takes longer and more reboots, but at least you will get them installed correctly. The guidance in the wiki is for adding a single drive at a time. It's not recommended to add 2 or 3 at once unless you really know what you are doing.

[Zeeuus]

Your help is much appreciated, thanks so far.

I started over (again).

The disk with problem have been assigned sda.

• 1. Started with ONLY the boot disk. This disk got assigned /dev/sda at boot
  2. Shutdown
  3. Added 2TB disk, this was assigned /dev/sdb
  4. Shutdown
  5. Added one of the 3TB disks, this was assigned /dev/sda at boot my boot disk was reassigned /dev/sdb and the 2TB disk reassigned /dev/sdc

The real problem here is that I can't find UUID to manually mount the 3 TB disk.

Seems like the disk don't get any uuid:

Code: Select all

[root@localhost ~]# ls -l /dev/disk/by-uuid/ totalt 0 lrwxrwxrwx 1 root root 10 23 jun 10.35 018935a0-5d36-4d1a-aee1-033e4cda409f -> ../../sdb6 lrwxrwxrwx 1 root root 10 23 jun 10.35 01D0A1547681FEA0 -> ../../sdc2 lrwxrwxrwx 1 root root 10 23 jun 10.35 2350b38f-a8b2-419b-b2e1-e395087e0c4f -> ../../sdb5 lrwxrwxrwx 1 root root 10 23 jun 10.35 3821d493-7120-4381-b67a-6efefcd09421 -> ../../sdb1 lrwxrwxrwx 1 root root 10 23 jun 10.35 6ed4b5e1-ea1a-459b-9ded-79cec0a391c8 -> ../../sdb2 lrwxrwxrwx 1 root root 10 23 jun 10.35 9C188A231889FD10 -> ../../sdc1 lrwxrwxrwx 1 root root 10 23 jun 10.35 b8a3a3b3-35b8-493d-9f90-15e89b156360 -> ../../sdb3

Of course the 3TB disk have some partitions on it that I really want to preserve:

Code: Select all

[root@localhost ~]# ls -l /dev/disk/by-id/ totalt 0 lrwxrwxrwx 1 root root 9 23 jun 10.35 ata-HL-DT-ST_RW_DVD_GCC-4480B -> ../../sr1 lrwxrwxrwx 1 root root 9 23 jun 10.35 ata-KINGSTON_SV300S37A120G_50026B785400AB28 -> ../../sdb lrwxrwxrwx 1 root root 10 23 jun 10.35 ata-KINGSTON_SV300S37A120G_50026B785400AB28-part1 -> ../../sdb1 lrwxrwxrwx 1 root root 10 23 jun 10.35 ata-KINGSTON_SV300S37A120G_50026B785400AB28-part2 -> ../../sdb2 lrwxrwxrwx 1 root root 10 23 jun 10.35 ata-KINGSTON_SV300S37A120G_50026B785400AB28-part3 -> ../../sdb3 lrwxrwxrwx 1 root root 10 23 jun 10.35 ata-KINGSTON_SV300S37A120G_50026B785400AB28-part4 -> ../../sdb4 lrwxrwxrwx 1 root root 10 23 jun 10.35 ata-KINGSTON_SV300S37A120G_50026B785400AB28-part5 -> ../../sdb5 lrwxrwxrwx 1 root root 10 23 jun 10.35 ata-KINGSTON_SV300S37A120G_50026B785400AB28-part6 -> ../../sdb6 lrwxrwxrwx 1 root root 9 23 jun 10.35 ata-PHILIPS_DVDR16LS_DL100510024516 -> ../../sr0 lrwxrwxrwx 1 root root 9 23 jun 10.35 ata-WDC_WD20EARX-00PASB0_WD-WCAZA7733456 -> ../../sdc lrwxrwxrwx 1 root root 10 23 jun 10.35 ata-WDC_WD20EARX-00PASB0_WD-WCAZA7733456-part1 -> ../../sdc1 lrwxrwxrwx 1 root root 10 23 jun 10.35 ata-WDC_WD20EARX-00PASB0_WD-WCAZA7733456-part2 -> ../../sdc2 lrwxrwxrwx 1 root root 9 23 jun 10.35 ata-WDC_WD30EFRX-68EUZN0_WD-WCC4N4LC7FFP -> ../../sda lrwxrwxrwx 1 root root 10 23 jun 10.35 ata-WDC_WD30EFRX-68EUZN0_WD-WCC4N4LC7FFP-part1 -> ../../sda1 lrwxrwxrwx 1 root root 10 23 jun 10.35 ata-WDC_WD30EFRX-68EUZN0_WD-WCC4N4LC7FFP-part2 -> ../../sda2 lrwxrwxrwx 1 root root 10 23 jun 10.35 ata-WDC_WD30EFRX-68EUZN0_WD-WCC4N4LC7FFP-part3 -> ../../sda3 lrwxrwxrwx 1 root root 9 23 jun 10.35 wwn-0x50014ee2b091f6ca -> ../../sdc lrwxrwxrwx 1 root root 10 23 jun 10.35 wwn-0x50014ee2b091f6ca-part1 -> ../../sdc1 lrwxrwxrwx 1 root root 10 23 jun 10.35 wwn-0x50014ee2b091f6ca-part2 -> ../../sdc2 lrwxrwxrwx 1 root root 9 23 jun 10.35 wwn-0x50014ee2b65a74c9 -> ../../sda lrwxrwxrwx 1 root root 10 23 jun 10.35 wwn-0x50014ee2b65a74c9-part1 -> ../../sda1 lrwxrwxrwx 1 root root 10 23 jun 10.35 wwn-0x50014ee2b65a74c9-part2 -> ../../sda2 lrwxrwxrwx 1 root root 10 23 jun 10.35 wwn-0x50014ee2b65a74c9-part3 -> ../../sda3 lrwxrwxrwx 1 root root 9 23 jun 10.35 wwn-0x50026b785400ab28 -> ../../sdb lrwxrwxrwx 1 root root 10 23 jun 10.35 wwn-0x50026b785400ab28-part1 -> ../../sdb1 lrwxrwxrwx 1 root root 10 23 jun 10.35 wwn-0x50026b785400ab28-part2 -> ../../sdb2 lrwxrwxrwx 1 root root 10 23 jun 10.35 wwn-0x50026b785400ab28-part3 -> ../../sdb3 lrwxrwxrwx 1 root root 10 23 jun 10.35 wwn-0x50026b785400ab28-part4 -> ../../sdb4 lrwxrwxrwx 1 root root 10 23 jun 10.35 wwn-0x50026b785400ab28-part5 -> ../../sdb5 lrwxrwxrwx 1 root root 10 23 jun 10.35 wwn-0x50026b785400ab28-part6 -> ../../sdb6

But the device i there...

Code: Select all

[root@localhost ~]# ls -l /dev/sd* brw-rw---- 1 root disk 8, 0 23 jun 10.35 /dev/sda brw-rw---- 1 root disk 8, 1 23 jun 10.35 /dev/sda1 brw-rw---- 1 root disk 8, 2 23 jun 10.35 /dev/sda2 brw-rw---- 1 root disk 8, 3 23 jun 10.35 /dev/sda3 brw-rw---- 1 root disk 8, 16 23 jun 10.35 /dev/sdb brw-rw---- 1 root disk 8, 17 23 jun 10.35 /dev/sdb1 brw-rw---- 1 root disk 8, 18 23 jun 10.35 /dev/sdb2 brw-rw---- 1 root disk 8, 19 23 jun 10.35 /dev/sdb3 brw-rw---- 1 root disk 8, 20 23 jun 10.35 /dev/sdb4 brw-rw---- 1 root disk 8, 21 23 jun 10.35 /dev/sdb5 brw-rw---- 1 root disk 8, 22 23 jun 10.35 /dev/sdb6 brw-rw---- 1 root disk 8, 32 23 jun 10.35 /dev/sdc brw-rw---- 1 root disk 8, 33 23 jun 10.35 /dev/sdc1 brw-rw---- 1 root disk 8, 34 23 jun 10.35 /dev/sdc2

As you can see above the /dev/sda disk have tree partitions that I want to preserve.
All I find when googling is to wipe the disk, creating new partition tables or formatting the disk.
I'm really stuck here.

[Zeeuus]

Made some google today, and found some info in different fedora communitys.

This is what I came up with if that makes any sense.

Code: Select all

[root@localhost ~]# parted /dev/sda print Modell: ATA WDC WD30EFRX-68E (scsi) Disk /dev/sda: 3001GB Sektorstorlek (logisk/fysisk): 512B/4096B Partitionstabell: gpt Disk Flags: Nummer Början Slut Storlek Filsystem Namn Flaggor 1 17,4kB 1066kB 1049kB LDM metadata partition 2 1066kB 134MB 133MB Microsoft reserved partition msftres 3 134MB 3001GB 3000GB LDM data partition

Code: Select all

[root@localhost ~]# parted -l Modell: ATA WDC WD30EFRX-68E (scsi) Disk /dev/sda: 3001GB Sektorstorlek (logisk/fysisk): 512B/4096B Partitionstabell: gpt Disk Flags: Nummer Början Slut Storlek Filsystem Namn Flaggor 1 17,4kB 1066kB 1049kB LDM metadata partition 2 1066kB 134MB 133MB Microsoft reserved partition msftres 3 134MB 3001GB 3000GB LDM data partition Modell: ATA KINGSTON SV300S3 (scsi) Disk /dev/sdb: 120GB Sektorstorlek (logisk/fysisk): 512B/512B Partitionstabell: msdos Disk Flags: Nummer Början Slut Storlek Typ Filsystem Flaggor 1 1049kB 211MB 210MB primary ext4 startbar 2 211MB 62,8GB 62,6GB primary ext4 3 62,8GB 66,0GB 3238MB primary linux-swap(v1) 4 66,0GB 120GB 54,0GB extended 5 66,0GB 69,3GB 3238MB logical ext4 6 69,3GB 120GB 50,8GB logical ext4 Modell: ATA WDC WD20EARX-00P (scsi) Disk /dev/sdc: 2000GB Sektorstorlek (logisk/fysisk): 512B/4096B Partitionstabell: msdos Disk Flags: Nummer Början Slut Storlek Typ Filsystem Flaggor 1 1049kB 1468GB 1468GB primary ntfs 2 1957GB 2000GB 42,9GB primary ntfs

Code: Select all

[root@localhost ~]# blkid /dev/sdb1: UUID="3821d493-7120-4381-b67a-6efefcd09421" TYPE="ext4" /dev/sdb2: UUID="6ed4b5e1-ea1a-459b-9ded-79cec0a391c8" TYPE="ext4" /dev/sdb3: UUID="b8a3a3b3-35b8-493d-9f90-15e89b156360" TYPE="swap" /dev/sdb5: UUID="2350b38f-a8b2-419b-b2e1-e395087e0c4f" TYPE="ext4" /dev/sdb6: UUID="018935a0-5d36-4d1a-aee1-033e4cda409f" TYPE="ext4" /dev/sdc1: LABEL="Downer" UUID="9C188A231889FD10" TYPE="ntfs" /dev/sdc2: LABEL="Data" UUID="01D0A1547681FEA0" TYPE="ntfs" /dev/sda1: PARTLABEL="LDM metadata partition" PARTUUID="d712f10f-bd1e-11e4-9e57-0011d8971eba" /dev/sda2: PARTLABEL="Microsoft reserved partition" PARTUUID="c543e1dc-82f2-4089-8369-e3b10a8b434a" /dev/sda3: PARTLABEL="LDM data partition" PARTUUID="d712f112-bd1e-11e4-9e57-0011d8971eba"

Code: Select all

[root@localhost ~]# mount proc on /proc type proc (rw,nosuid,nodev,noexec,relatime) sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime) devtmpfs on /dev type devtmpfs (rw,nosuid,size=1534640k,nr_inodes=383660,mode=755) securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime) tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev) devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000) tmpfs on /run type tmpfs (rw,nosuid,nodev,mode=755) tmpfs on /sys/fs/cgroup type tmpfs (rw,nosuid,nodev,noexec,mode=755) cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/usr/lib/systemd/systemd-cgroups-agent,name=systemd) pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime) cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset) cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpuacct,cpu) cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,memory) cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices) cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer) cgroup on /sys/fs/cgroup/net_cls type cgroup (rw,nosuid,nodev,noexec,relatime,net_cls) cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio) cgroup on /sys/fs/cgroup/perf_event type cgroup (rw,nosuid,nodev,noexec,relatime,perf_event) /dev/sdb6 on / type ext4 (rw,relatime,data=ordered) systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=34,pgrp=1,timeout=300,minproto=5,maxproto=5,direct) debugfs on /sys/kernel/debug type debugfs (rw,relatime) tmpfs on /tmp type tmpfs (rw) mqueue on /dev/mqueue type mqueue (rw,relatime) configfs on /sys/kernel/config type configfs (rw,relatime) hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime) /dev/sdb2 on /home type ext4 (rw,relatime,data=ordered) /dev/sdb1 on /boot type ext4 (rw,relatime,data=ordered) /dev/sdb5 on /var/hda/files/drives/drive4 type ext4 (rw,relatime,data=ordered) /dev/sdc2 on /var/hda/files/drives/drive3 type fuseblk (rw,nosuid,nodev,noexec,noatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096) /dev/sdc1 on /var/hda/files/drives/drive2 type fuseblk (rw,nosuid,nodev,noexec,noatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096) none on /var/spool/greyhole/mem type tmpfs (rw,relatime,size=4096k) binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,relatime)

Also I did check the hda-diskmount skript in /usr/sbin as described in this thread viewtopic.php?f=15&t=2326&p=11617

Made a new mount point and tried to mount /dev/sda1 to /var/hda/files/drives/drive6 using:

Code: Select all

[root@localhost ~]# mount -v -t ntfs /dev/sda1 /var/hda/files/drives/drive6 NTFS signature is missing. Failed to mount '/dev/sda1': Ogiltigt argument The device '/dev/sda1' 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?

Even tough it is a GPT disk , this should not be a problem to mount, any advice would be highly appreciated as this is driving me nuts... What am I missing?

[bigfoot65]

There is often quirks when converting NTFS disks from a Windows to a Linux system. This may be the case.

I have not seen too many problems with mount drives. This one is odd. The key here is to determine the UUID for the drives. If you cannot do so given the steps in the wiki, maybe there is another option for identification.

I would recommend you try adding the drive to /etc/fstab using the UUID. Then when you execute mount -a, it should work. Just ensure you have the correct info on the line for ntfs and the mount point. Best to stay away from /dev/sda.

Would also be wise to ensure your OS drive is sda. This is controlled by the cabling. Could be the cause of some of your issues as well since you installed initially without additional disks and it was sda then.