Hdd won’t show in device list but USB will?? Why?

Hi,

So I set up an old 8GB USB (ext4) and a 2GB USB (NTFS) as shared folders and it worked perfectly. Granted, I had to “sudo apt-get install ntfs.3g” so that the 2GB USB would even show up in the device list.

But now the next problem...

My 8TB hdd (NTFS - 1.5TB used) will happily mount (I use the webUI), but it won’t show up in the device list so that I can create a shared folder from it.

I have files on there which are 2GB+. Is this the reason?

Otherwise, why would the USB work and the hdd won’t?

I’ve followed the instructions set out by “Trekmaster”. Again, worked for the USB, but won’t for the hdd.

I tried “omv-confdbadm read conf.system.filesystem.mountpoint”, then unmounted and remounted the hdd (8TB) but it won’t work.

~1.5TB is a lot of data to lose, I don’t fancy reformatting it to ext4.

PLEASE HELP!

Thank you very much!!

Zitat von Trekmaster

Okay i figured it out. I'll write exactly what i did (Maybe some of the things is not necessary but i will write it step by step what I DID)

1. I reformatted my SD card and reflashed OMV_3_0_88_RaspberryPi_2_3_4.9.41.img with Etcher
2. I inserted the card in my Raspberry pi 3 and let it finish installation
3. Wrote apt upgrade and wait for finish
4. wrote apt-get install ntfs.3g (just to be sure)
5. Then i go into Omv interface on the net, and now the error message was gone ""Failed to execute XPath query '//services/afp'.""
6. All this time my hard drive was not plugged in and i did now plug it in.
7. Go into File Systems and now press mount and i didn't get a error this time.

I couldn't pick my Hard drive in Shared folders though (Not Visible at all) so i Googled alittle and found this command..

omv-confdbadm read conf.system.filesystem.mountpoint

After i wrote this in CLI i Dismounted my drive and remounted it (In WEBUI) and now it's visible in my Shared folders!!!

I hope this can help others.

BTW if you can't mount your drive and it gives that long Error "Failed to execute command....." try use this command:

ntfsfix /dev/xxx

Where xxx is your device (You can find it with fdisk -l)

Then you should be enable you mount your drive.

Alles anzeigen

Zitat von tkaiser

That's why you should do backup. Once you have a backup in place it's easy to format your data disk with ext4 or any other POSIX compliant filesystem (do NOT use NTFS with OMV!)

Hey,

Thanks for responding! I had originally planned for the 8TB to be the backup... I have been working on transferring everything over from a 2TB, debating whether to just use the 8TB as cold storage (but that's no fun). I'd just then reformat the 2TB as ext4.

My concern then would be that (I use MacOS) I couldn't read/write ext4 on mac without paying for additional software?

Thanks!

Zitat von tkaiser

Please do not try to do this. It simply doesn't work with other OS than MacOS to access a filesystem both locally and shared over the network. Apple's own filesharing daemons (both AppleFileServer and their SMB implementation) can cope with this but no other system. See here for some issues: Not starting NFS kernel daemon: no support in current kernel on 3.0.94 RPI3 or https://redmine.ixsystems.com/issues/5904
If you want to access a disk both locally and over the network using macOS as server is your only option.

I think my best option would be to use the 8TB (NTFS) as cold storage and 2TB (EXT4) as shared over the network.

I have no need to use the 2TB (EXT4) locally other than to have a faster transfer of files onto it to initially set it up, when it is shared over the network.

I could then just regularly backup the shared folder to the 8TB cold over the network.

Do you think this sounds logical?

I really appreciate your assistance! Thank you!

Zitat von tkaiser

Again: bad idea unless you fully understand which file/folder metadata are stored in which way by OMV (Samba and/or Netatalk) and macOS on 'foreign filesystems' and how encoding conventions look like. Unless you use only plain ASCII for file and foldernames and none of your files has metadata attached (impossible) this won't work well.

Use a disk formatted with a POSIX compliant filesystem on your OMV box and access it only through the network (with either Samba or Netatalk -- see above for the reasons).

BTW: it seems you're using a Rasperry Pi since you fear low NAS performance? If that's the case... there's no reason to run OMV on such crappy hardware. You get faster and even less expensive ARM boards: Which energy efficient ARM platform to choose?

I might be wrong but I'm confident ext4 is POSIX compliant. This is how I would format the hdd to create a shared folder.

Interestingly enough, I just connected a 1TB HFS+ FS hdd up and it works perfectly fine... It showed up in the device list and I can just simply share the folder as I wished. I don't now think I will need to format to ext4 as it would seem that I have a hdd that can be local and shared, not that I need this at all...

No idea why this hdd works when the other didn't. I got given the Raspberry Pi, very kindly, by a friend so there was no cost; hence, I am using that.

Thank you for your assistance and advice!