Hello, i have installed omv 3.0.71 on a c2 odroid. I have 9 external harddisks formatted in ntfs, so far I have mounted NFS 7 hard drives without problems but the last two gives me the following mount error "Failed to execute command" export PATH = / bin: / sbin: / Usr / bin: / usr / usr / local / sbin; export LANG = C; mount -v --source '/ dev / sdb1' 2> & 1 'with exit code' : Mount: can not find mount source / dev / sdb1 in / etc / fstab "I do not understand what it is, you know what to suggest? Thank you.
error mount ntfs hard disk
-
- OMV 3.x
- marcavatar
-
-
The following is not a definitive answer, but something to think about.
The device limit for USB is 127 per controller. That's the theory anyway. However, from a practical standpoint, you have a LOT of devices connected to your odriod so you must be using some sort of hub. (Maybe more than one.)
Further, USB is a serial bus so you have a lot of high traffic, high bandwidth, devices contending for the bandwidth that's available. As a consequence, you may be bumping into some sort of "practical" (not theoretical) device / bandwidth limitation of the odriod and/or the hub(s). -
-
Thanks for the reply, then actually use two powered USB hubs that then
connect to the Android c2, I typed through SSH the commands you posted
to me and this is the result:
# Cat / etc / fstab
UUID = e139ce78-9841-40fe-8823-96a304a09859 / ext4 errors = remount-r o, noatime, discard 0 1
/ Dev / mmcblk0p1 / boot vfat noatime, discard0 2# >>> [openmediavault]
/
Dev / disk / by-label / Data / srv / dev-disk-by-label-Data ext4
defaults, nofail, user_x, ttr, noexec, usrjquota = aquota.user,
grpjquota = aquota.group, jqfmt = vfsv0, acl 0 2
/ Dev / disk / by-label / WDElementsG / srv / dev-disk-by-label-WDElementsG ntfs defaults, nofail
/ Dev / disk / by-label / ElementsM / srv / dev-disk-by-label-ElementsM ntfs defaults, nofa on 0 2
/ Dev / disk / by-label / ElementsK / srv / dev-disk-by-label-ElementsK ntfs defaults, nofa on 0 2
/ Dev / disk / by-label / ElementsO / srv / dev-disk-by-label-ElementsO ntfs defaults, nofa on 0 2
/ Dev / disk / by-label / ElementsQ / srv / dev-disk-by-label-ElementsQ ntfs defaults, nofa on 0 2
/ Dev / disk / by-label / ElementsP / srv / dev-disk-by-label-ElementsP ntfs defaults, nofa on 0 2
/ Dev / disk / by-label / STORAGEV / srv / dev-disk-by-label-STORAGE n nfs defaults, nofail 0 2
/ Dev / disk / by-label / WDElementsT / srv / dev-disk-by-label-WDElementsT ntfs defaults, nofail
/ Dev / disk / by-label / ElementsN / srv / dev-disk-by-label-ElementsN ntfs defaults, nofa on 0 2
/ Srv / dev-disk-by-label-Data // export / Data none bind, nofail 0 0
/ Srv / dev-disk-by-label-WDElementsG / / export / HardDiskG none bind, nofail
/ Srv / dev-disk-by-label-ElementsM // export / HardDiskM none bind, nofail 0 0
/ Srv / dev-disk-by-label-ElementsO // export / HardDiskO none bind, nofail 0 0
/ Srv / dev-disk-by-label-ElementsK // export / HardDiskK none bind, nofail 0 0
/ Srv / dev-disk-by-label-ElementsQ // export / HardDiskQ none bind, nofail 0 0
/ Srv / dev-disk-by-label-Elements / // export / HardDiskP none bind, nofail 0 0
/ Srv / dev-disk-by-label-STORAGEV // export / HardDiskV none bind, nofail
/ Srv / dev-disk-by-label-WDElementsT / / export / HardDiskT none bind, nofail
/ Srv / dev-disk-by-label-ElementsN / / export / HardDiskN none bind, nofail
# <<< [openmediavault] -
Thanks for the reply, then actually use two powered USB hubs that then
connect to the Android c2, I typed through SSH the commands you posted
to me and this is the result:
# Cat / etc / fstab
UUID = e139ce78-9841-40fe-8823-96a304a09859 / ext4 errors = remount-r o, noatime, discard 0 1
/ Dev / mmcblk0p1 / boot vfat noatime, discard0 2# >>> [openmediavault]
/
Dev / disk / by-label / Data / srv / dev-disk-by-label-Data ext4
defaults, nofail, user_x, ttr, noexec, usrjquota = aquota.user,
grpjquota = aquota.group, jqfmt = vfsv0, acl 0 2
/ Dev / disk / by-label / WDElementsG / srv / dev-disk-by-label-WDElementsG ntfs defaults, nofail
/ Dev / disk / by-label / ElementsM / srv / dev-disk-by-label-ElementsM ntfs defaults, nofa on 0 2
/ Dev / disk / by-label / ElementsK / srv / dev-disk-by-label-ElementsK ntfs defaults, nofa on 0 2
/ Dev / disk / by-label / ElementsO / srv / dev-disk-by-label-ElementsO ntfs defaults, nofa on 0 2
/ Dev / disk / by-label / ElementsQ / srv / dev-disk-by-label-ElementsQ ntfs defaults, nofa on 0 2
/ Dev / disk / by-label / ElementsP / srv / dev-disk-by-label-ElementsP ntfs defaults, nofa on 0 2
/ Dev / disk / by-label / STORAGEV / srv / dev-disk-by-label-STORAGE n nfs defaults, nofail 0 2
/ Dev / disk / by-label / WDElementsT / srv / dev-disk-by-label-WDElementsT ntfs defaults, nofail
/ Dev / disk / by-label / ElementsN / srv / dev-disk-by-label-ElementsN ntfs defaults, nofa on 0 2
/ Srv / dev-disk-by-label-Data // export / Data none bind, nofail 0 0
/ Srv / dev-disk-by-label-WDElementsG / / export / HardDiskG none bind, nofail
/ Srv / dev-disk-by-label-ElementsM // export / HardDiskM none bind, nofail 0 0
/ Srv / dev-disk-by-label-ElementsO // export / HardDiskO none bind, nofail 0 0
/ Srv / dev-disk-by-label-ElementsK // export / HardDiskK none bind, nofail 0 0
/ Srv / dev-disk-by-label-ElementsQ // export / HardDiskQ none bind, nofail 0 0
/ Srv / dev-disk-by-label-Elements / // export / HardDiskP none bind, nofail 0 0
/ Srv / dev-disk-by-label-STORAGEV // export / HardDiskV none bind, nofail
/ Srv / dev-disk-by-label-WDElementsT / / export / HardDiskT none bind, nofail
/ Srv / dev-disk-by-label-ElementsN / / export / HardDiskN none bind, nofail
# <<< [openmediavault] -
This is a guess, maybe you have a drive with a identical label?
Can you post
lsblk --fs
-
Hi, this is what it turns out to be:
Root @ openmediavault: ~ # lsblk --fs
NAME FSTYPE LABEL UUID MOUNTPOINT
Sda
└─sda1 ext4 Data bf9b1e83-5541-48f5-a4d5-7c73838c052f / export / Data
Mmcblk0
├─mmcblk0p1 vfat boot 0966-01D4 / boot
└─mmcblk0p2 ext4 rootfs e139ce78-9841-40fe-8823-96a304a09859 / -
This is what comes with connected hard drives:
Root @ openmediavault: ~ # lsblk --fs
NAME FSTYPE LABEL UUID MOUNTPOINT
Sda
└─sda1 ntfs ElementsQ 8A688C8A688C76AB / export / HardDisk
Sdb
└─sdb1 ntfs ElementsN B6900F79900F3EFD / export / HardDisk
Sdc
└─sdc1 ext4 Data bf9b1e83-5541-48f5-a4d5-7c73838c052f / export / Data
Sdd
└─sdd1 ntfs ElementsM 461CB5691CB55521 / export / HardDisk
Sde
└─sde1 ntfs ElementsK 8C24B25D24B24A4A / export / HardDisk
Sdf
└─sdf1 ntfs ElementsO E026632926630040 / export / HardDisk
Sdg
└─sdg1 ntfs ElementsP 643E5EAC3E5E76D0 / export / HardDisk
Sdh
└─sdh1 ntfs WDElementsG DCE8E615E8E5EE28 / export / HardDisk
Sdi
└─sdi1 ntfs STORAGEV 01D1CA051EE97A80 / export / HardDisk
Sdj
└─sdj1 ntfs WDElementsT 01D1F890F24A7500 / export / HardDisk
Mmcblk0
├─mmcblk0p1
Vfat boot 0966-01D4 / boot
└─mmcblk0p2
Ext4 rootfs e139ce78-9841-40fe-8823-96a304a09859 / -
Looks ok to me, no duplicates, but the disks must stay attached on boot. OMV will not automount on disk plug
-
It is not possible that Openmediavault automatically recognizes the same hard disk when the external hard disk is switched on or every time I have to restart Openmediavault, I wanted to avoid letting them even when I did not use them. There is a system that saves energy and does not spoil it over time or maybe through ssh restart the server. Thank you
-
Well in that case you would have to switch off the whole system. No point in running Omv with no drives.
-
Hi, can you make openmediavault keep the burned hard disks shut down in case of downtime and then turn on automatically when they are called in? I would like to avoid turning them without reason, working all day, so there are moments where there is no one.
-
There are some power saving option. You should see them per disk in the physical disk section. Reports from this forum i am under the impression is not very reliable. Never used that feature.
I also have my doubts if the power energy save option work with USB disks.
Jetzt mitmachen!
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!