Re-enabling Automounting

[floydbloke]

This is causing me a bit of grief.

Prior to the update my external HDD would automount and I could happily access directories and files. It has two partitions: 1TB_part1 and 1TB_part2, (both partitioned as FAT, or possibly NTFS, not at home right now and I can’t remember which). Now when I connect the HDD these partitions (or at least their names) appear as directories under /media but I can’t see any contents.
It does let me create new directories and folders within them though and if named appropriately SAMBA will pick them up and I can see them from a Windows machine.
If I now disconnect the external HHD and reboot my plug the directory/partition (in this 1TB_part1) and its contents that I created are still accessible on the plug. It seems that this content wasn't written to the external HDD at all??
Plugging the external HDD back into a Windows machine all the original contents are still there but the newly created content can’t be seen.

What am I missing? Could it be a permissions thing perhaps?

[WarheadsSE]

The drives didn't mount to those directories, so you were writing to the local file system, simple as that. Ensure the automount rules are installed and active.

[floydbloke]

The drives didn't mount to those directories, so you were writing to the local file system, simple as that. Ensure the automount rules are installed and active.

Thanks for that. The rules exist (in default format, straight from the install and they match the ArchLinux wiki) and it certainly appears that these rules create the said directories. I did not create them manually.
Is there a way that I can confirm that the rules are indeed active and where the drive/partitions are being mounted, if at all? I guess they should show up if I do just execute a mount command.

(apologies for my ignorance, I'm very much a beginner at anything Linux)

[WarheadsSE]

List the mounted partitions:
mount

List the known partitions:
cat /proc/partitions

[roncova]

Is there any update on the issue of having a connected USB drive mount at startup? I am running a v3 and the USB drive will automount fine if I unplug it and plug it back into the Pogo, but if the Pogo is powered down it won't see the drive until it is removed and reconnected.

[kmihelich]

For devices connected at boot, you need to add an fstab entry.

https://wiki.archlinux.org/index.php/Fstab

[jabba78]

How do you DIS-able automounting? I'm a noob , sorry.

[kikin81]

Dear ALARM fellows,
My pogoplug used to mount my exfat partition on boot with the following command which I added to /etc/rc.local

Code: Select all

# Mount external hdd
mount.exfat-fuse /dev/sdb1 /mnt/exfat


Unfortunately, it does not mount. When I run the command, I get the following error:

Code: Select all

FUSE exfat 0.9.5
ERROR: failed to open `/dev/sdb1'.


Running the command previously posted to see the unmounted partitions does list sdb1.

Code: Select all

cat /proc/partitions
major minor  #blocks  name

   8        0  117220824 sda
   8        1  117218241 sda1
  31        0     131072 mtdblock0
  31        1      14336 mtdblock1
  31        2     116736 mtdblock2
   8       16 1953512448 sdb
   8       17 1953512447 sdb1


My question is, is this a FUSE exfat 0.9.5 error? I used the command on the OP about re-enabling Automounting, but no luck. Any help would be greatly appreciated. Thanks for your time.

[WarheadsSE]

Device, last update date, and kernel version.

[sambul13]

Can someone clarify what ACTION=="remove" stands for? Is it when a USB Enclosure cable or Thumb drive is physically detached from Dockstar USB port? Or when a USB enclosure power is switched Off, it also constitutes drive removal? Or something else?

The rules work fine when switching a USB enclosure On/Off or hooking up a USB Thumb to the Dockstar. But the Clean up code doesn't seem to work: after drive removal (USB enclosure switched Off) it doesn't delete the directories where partitions were mounted, resulting in empty Samba shares still accessible in Windows, which may result in writing data to these folders that will be substituted by a newly mounted drive next time. It also overcrowds the view and confuses a user.

Its desirable to fix this issue, and also add the rule to delete (or hide) corresponding Samba shares if present, when partitions are dismounted. Similar rule should be added to device halt & shutdown code. Otherwise Windows Explorer stalls each time Dockstar is shut down (Samba stopped), resulting in its eventual restart.