Well usbmount works by invoking the mount command with the proper filesystem. I can mount ntfs on my own, so see no reason why it shouldn't work.
But thanks for your help.
Beiträge von Noneatme
-
-
I've tried as you suggested, but the same error message occurs. That doesn't surprised me, because I think I've tried that already some days ago. Yes, I'm trying to figure out this error since 2 DAYS ALREADY and I'm really upset.
I believe something is preventing the mounting of the device to that mountpoint. I don't know if omv is doing something in the background when plugging the device in, maybe ghost-mounting or something? I don't know.
I don't know where to start and I don't know where to look because I have absolutely no idea what might causes this issue. I've tried almost everything! Using custom udev rules, mounting with read-only, mounting with different options.It works when I mount the device by hand using $ mount /dev/sdc1 /media/usb1.
So I really don't know what the hell these packages and automount tools (e.g. usbmount) are doing is doing in order to screw the mountpoint up that much. -
Code
Alles anzeigen# Configuration file for the usbmount package, which mounts removable # storage devices when they are plugged in and unmounts them when they # are removed. # Change to zero to disable usbmount ENABLED=1 # Mountpoints: These directories are eligible as mointpoints for # removable storage devices. A newly plugged in device is mounted on # the first directory in this list that exists and on which nothing is # mounted yet. MOUNTPOINTS="/media/usb0 /media/usb1 /media/usb2 /media/usb3 /media/usb4 /media/usb5 /media/usb6 /media/usb7" # Filesystem types: removable storage devices are only mounted if they # contain a filesystem type which is in this list. FILESYSTEMS="vfat ntfs fuseblk ext2 ext3 ext4 hfsplus" ############################################################################# # WARNING! # # # # The "sync" option may not be a good choice to use with flash drives, as # # it forces a greater amount of writing operating on the drive. This makes # # the writing speed considerably lower and also leads to a faster wear out # # of the disk. # # # # If you omit it, don't forget to use the command "sync" to synchronize the # # data on your disk before removing the drive or you may experience data # # loss. # # # # It is highly recommended that you use the pumount command (as a regular # # user) before unplugging the device. It makes calling the "sync" command # # and mounting with the sync option unnecessary---this is similar to other # # operating system's "safely disconnect the device" option. # ############################################################################# # Mount options: Options passed to the mount command with the -o flag. # See the warning above regarding removing "sync" from the options. MOUNTOPTIONS="sync,noexec,nodev,noatime,nodiratime" # Filesystem type specific mount options: This variable contains a space # separated list of strings, each which the form "-fstype=TYPE,OPTIONS". # # If a filesystem with a type listed here is mounted, the corresponding # options are appended to those specificed in the MOUNTOPTIONS variable. # # For example, "-fstype=vfat,gid=floppy,dmask=0007,fmask=0117" would add # the options "gid=floppy,dmask=0007,fmask=0117" when a vfat filesystem # is mounted. FS_MOUNTOPTIONS="-fstype=ntfs-3g,nls=utf8,umask=007,gid=46 -fstype=fuseblk,nls=utf8,umask=007,gid=46 -fstype=vfat,gid=1000,uid=1000,umask=007" # If set to "yes", more information will be logged via the syslog # facility. VERBOSE=no/Edit:
The USB Drive I want to mount:CodeDisk /dev/sdd: 58.9 GiB, 63216549888 bytes, 123469824 sectors 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: 0x00c558b0 Device Boot Start End Sectors Size Id Type /dev/sdd1 * 2048 123469823 123467776 58.9G 7 HPFS/NTFS/exFATAlso a side note:
I can use fusermount -u usb0 to fix the broken mount point. But then, the mount point is gone. E.g. endless symlink referring usb0 => usb0 -
Hello everyone,
I'm writing here because I do not know what to do anymore.
I've read through various forums, blogs, tutorials and how-to's about how to configure various packages for auto-mounting and auto-unmounting USB devices (hot-plugging and hot-unplugging.)Methods I've tried so far:
1. AutoFS
2. usbmount
3. /etc/fstab systemd automount
4. udev rules, in fact, all of thisI've configured each method accordingly, and with every method I'm running into the same problem.
Now I un-did all the above methods and decided I will got with usbmount. I've edited the configuration file according to this thread.
When mounted, the mount point looks like this:
When I try to access the mounted partition on usb or usb0, I'm getting the following error message:
I've read here, here and here that it is / was a fuse issue - but I still got the issue with any NTFS drive. I have fuse 2.8.3 installed.
Do I have to update some packages? If yes, how?
Thanks for any help!
- Noneatme
-
Which distribution did you use? I see only Fedora, Ubuntu, CentOS? Most likely Ubuntu, because it´s Debian-based.
There are other posts here which recommend to use a Docker image as a further opportunity.
I used the Ubuntu package. In my case, most prerequisites were already installed, so I think it should work out of the box on your machine too.
But of course, you can also use a Docker image. -
I also had issues with Plex in the past. I recommend using the Plex image from their official website. I've read somewhere that the omv plugin has multiple issues and will be gone in some time.
Just download the .deb from here , dpkg -i it and you should be fine. -
It shows now a capacitiy of 2,7 TB and that's correct because I removed the jumper.
Sadly, there is no partition on the HDD anymore
I'm currently running testdisk to scan the partitions I can recover. There was a huge amount of sensible data on it
Edit: Are you sure I don't overwrite the existing (lost) filesystem when I use "create.."?
Edit2: SMART displays 3 TB now...
CodeLU WWN Device Id: 5 0014ee 20c759184 Firmware Version: 82.00A82 User Capacity: 3,000,591,900,160 bytes [3.00 TB]But seriously, why is this even a thing if you place a jumper on your motherboard that partitions just "dissapear"? Who is in charge of this?
-
Addendum to Issue 2: I had a jumper installed on the motherboard, that was the issue.
Any ideas how I should recover the filesystems? -
Hello everybody, I need some help with 2 problems.
I have currently 3 disks installed:
SSD 1: 32 GB SanDisk SSD (Boot device) SanDisk SDSSDRC032G
HDD 2: 232 GB SAMSUNG HDD (Very old drive) SAMSUNG SP2514N
HDD 3: 3000 GB WD RED (not even a month old) WDC WD30EFRX-68EUZN0During the installation process of OMV, disk 3 was missing because I put the disk into the NAS some days ago.
I would like to keep the NAS running 24/7 so I removed the 232 GB Samsung HDD because it's not very safe to run this disk 24/7.
After I did that, OVM found only the boot filesystem.So the first question, how can I mount the existing filesystem located on the 3TB WD Red?
And the second issue: OMV shows me the wrong capacity of the WD disk. It should be around 2,7 TB, not 1,82.
(Might be a partition issue?)
Code
Alles anzeigen================================================================================ = Partitions ================================================================================ major minor #blocks name 8 16 31266648 sdb 8 17 29946880 sdb1 8 18 1 sdb2 8 21 1316864 sdb5 8 32 244198584 sdc 8 33 244197543 sdc1 8 0 1953536567 sdaSMART output:
Code
Alles anzeigen=== START OF INFORMATION SECTION === Model Family: Western Digital Red Device Model: WDC WD30EFRX-68EUZN0 Serial Number: WD-WCC4N2CFNDDU LU WWN Device Id: 5 0014ee 20c759184 Firmware Version: 82.00A82 User Capacity: 2,000,421,444,608 bytes [2.00 TB] Sector Sizes: 512 bytes logical, 4096 bytes physical Device is: In smartctl database [for details use: -P show] ATA Version is: 9 ATA Standard is: Exact ATA specification draft version not indicated Local Time is: Tue Dec 15 11:46:32 2015 CET SMART support is: Available - device has SMART capability. SMART support is: Enabledoutput of mount:
Code
Alles anzeigenroot@mediavault:~# mount sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime) proc on /proc type proc (rw,nosuid,nodev,noexec,relatime) udev on /dev type devtmpfs (rw,relatime,size=10240k,nr_inodes=497349,mode=755) devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000) tmpfs on /run type tmpfs (rw,nosuid,noexec,relatime,size=406192k,mode=755) /dev/disk/by-uuid/04e58252-82dc-4abf-a23d-d09f55472693 on / type ext4 (rw,relatime,errors=remount-ro,user_xattr,barrier=1,data=ordered) tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k) tmpfs on /run/shm type tmpfs (rw,nosuid,nodev,noexec,relatime,size=1075740k) /dev/sdc1 on /media/89919e88-335b-4a39-904e-e1a86885d57f type ext4 (rw,noexec,relatime,user_xattr,barrier=1,data=ordered,jqfmt=vfsv0,usrjquota=aquota.user,grpjquota=aquota.group,_netdev) rpc_pipefs on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw,relatime)/etc/fstab:
Code
Alles anzeigen# /etc/fstab: static file system information. # # Use 'blkid' to print the universally unique identifier for a # device; this may be used with UUID= as a more robust way to name devices # that works even if disks are added and removed. See fstab(5). # # <file system> <mount point> <type> <options> <dump> <pass> # / was on /dev/sda1 during installation UUID=04e58252-82dc-4abf-a23d-d09f55472693 / ext4 errors=remount-ro 0 1 # swap was on /dev/sda5 during installation UUID=1c261aca-aa82-48e4-b399-4b342f6ffe1a none swap sw 0 0 /dev/sdb1 /media/usb0 auto rw,user,noauto 0 0 # >>> [openmediavault] UUID=89919e88-335b-4a39-904e-e1a86885d57f /media/89919e88-335b-4a39-904e-e1a86885d57f ext4 defaults,nofail,user_xattr,noexec,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl 0 2 UUID=0d29365c-a4eb-4ecb-bd04-da09189715a2 /media/0d29365c-a4eb-4ecb-bd04-da09189715a2 ext4 defaults,nofail,user_xattr,noexec,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl 0 2 # <<< [openmediavault]Thanks for help, I really don't know what to do at the moment.
