Correct at the time! Since then, I decided to use /mnt/share instead - (not sure why!)
I’ve already tried what you suggested in various combinations:
- Used custom UUID of “7ACCE961CCE917E1” per the UUID from the blkid output above
- Used custom UUID of “ebf1f6b3-1043-4425-8ab1-698370fd1b57” (PARTID from above)
- Used custom Label of “Seagate Expansion Drive” (from above)
- Used custom label of “Basic data partition” (from PARTLABEL)
Note that I did NOT include the quotation marks in what I entered in the LUCI interface!
In ALL cases, I first unmounted (using the unmount button) what the automount system mounted:
before trying the various forms of ADD. In all cases the result is something like:
The critical part in the above picture is "
(not present)" - it appears on all of the configurations I’ve tried.
I’ve also tried specifying ntfs in the “advanced” tab over the 4 different identification options - same result except that the “Filesystem” field shows “ntfs” instead of “?”.
Here are (I think) all the related lines in the system log:
2017-12-18T17:33:10-08:00 crit mountd[2390]: new mount : Disc-A2 -> sda2 (NTFS)
2017-12-18T17:33:10-08:00 crit mountd[2390]: mounting /tmp/run/mountd/sda2
2017-12-18T17:33:10-08:00 crit mountd[2595]: ntfs-3g /dev/sda2 /tmp/run/mountd/sda2 -o force
2017-12-18T17:33:10-08:00 err ntpdate[2168]: name server cannot be used: Try again (-3)
...
2017-12-18T17:33:13-08:00 crit mountd[2390]: ----------> mount ret = 0
2017-12-18T17:33:13-08:00 notice ntfs-3g[2676]: Version 2015.3.14 integrated FUSE 27
2017-12-18T17:33:13-08:00 notice ntfs-3g[2676]: Mounted /dev/sda2 (Read-Write, label "Seagate Expansion Drive", NTFS 3.1)
2017-12-18T17:33:13-08:00 notice ntfs-3g[2676]: Cmdline options: force
2017-12-18T17:33:13-08:00 notice ntfs-3g[2676]: Mount options: force,allow_other,nonempty,relatime,fsname=/dev/sda2,blkdev,blksize=4096
2017-12-18T17:33:13-08:00 notice ntfs-3g[2676]: Ownership and permissions disabled, configuration type 1
...
2017-12-18T17:50:01-08:00 notice ntfs-3g[2676]: Unmounting /dev/sda2 (Seagate Expansion Drive)
All lines above except the last were the automount system (I think) after my most recent reboot.
The last line is me clicking the “Unmount” button
All attempts at mounting with the “Add” button - including finishing with “Save and Exit” resulted in no entries in the syslog (that I can find!)
Just for grins and giggles, I tried doing a simple mount command from the SSH interface:
root@turris:/#
root@turris:/#
root@turris:/# blkid
/dev/mmcblk0: PTUUID="8c1fe33f" PTTYPE="dos"
/dev/mmcblk0p1: UUID="0aa0df20-0f06-4cba-944d-50bd9db9262c" UUID_SUB="e8357d8b-5424-4f78-ae37-747d3ca3c088" TYPE="btrfs" PARTUUID="8c1fe33f-01"
/dev/sda1: PARTLABEL="Microsoft reserved partition" PARTUUID="ca7138a3-f84f-40cc-a17a-b2c961e719aa"
/dev/sda2: LABEL="Seagate Expansion Drive" UUID="7ACCE961CCE917E1" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="ebf1f6b3-1043-4425-8ab1-698370fd1b57"
root@turris:/#
root@turris:/#
root@turris:/#
root@turris:/# mount /dev/sda2 /mnt/share
mount: wrong fs type, bad option, bad superblock on /dev/sda2,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so.
root@turris:/#
root@turris:/# dmesg | tail
[ 28.500638] br-lan: port 2(eth2) entered forwarding state
[ 28.500668] br-lan: port 1(eth0) entered forwarding state
[ 28.781039] mvneta f1034000.ethernet eth1: Link is Up - 1Gbps/Full - flow control off
[ 28.781056] IPv6: ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
[ 28.850615] br-lan: port 4(wlan0) entered forwarding state
[ 1151.193662] nf_conntrack: automatic helper assignment is deprecated and it will be removed soon. Use the iptables CT target to attach helpers instead.
[ 2239.425818] ntfs: (device sda2): parse_ntfs_boot_sector(): Volume size (7TiB) is too large for this architecture. Maximum supported is 2TiB. Sorry.
[ 2239.439287] ntfs: (device sda2): ntfs_fill_super(): Unsupported NTFS filesystem.
[ 2290.361509] ntfs: (device sda2): parse_ntfs_boot_sector(): Volume size (7TiB) is too large for this architecture. Maximum supported is 2TiB. Sorry.
[ 2290.374970] ntfs: (device sda2): ntfs_fill_super(): Unsupported NTFS filesystem.
root@turris:/#
This last bit really puzzles me as the automount system successfully mounted it!
Next things to try? Anybody?