İ just upgraded my old omv 3.5 to 5 with clean wipe install hdd. now only 1 file system hac come. rest didnt. i didnt have any raid. just single disks with data.
Upgraded from omv 3 to omv 5.5.8-1 File systems missing
-
- OMV 5.x
- tranz
-
-
tranz
Hat das Label OMV 5.x hinzugefügt. -
-
i dd nothing before update. i just made clean install. what i expect is see samba shares visible at network auto i mean i only connect with map to storage network option with windows. and transmission gone silly so i couldnt remove or install new torrent. so i wanted to upgrade. but i cant see file systems under that web ui tab.
-
Then you need to share the folders in SBM/CFIS, and give permissions to Shamshare to your user.
If you want to share the root of the HDD, the relative Path must be "/", if you white a name, then the OMV will create a shared folder with this name.
Also, I recommend to activate the "Enable permission inheritance" for the folders ins Shared Tab (in SMB/CFIS).
-
Then you need to share the folders in SBM/CFIS, and give permissions to Shamshare to your user.
If you want to share the root of the HDD, the relative Path must be "/", if you white a name, then the OMV will create a shared folder with this name.
Also, I recommend to activate the "Enable permission inheritance" for the folders ins Shared Tab (in SMB/CFIS).
Thank for tips. My problem is file systems not showing at that tab. not shares
-
-
If we are talking about the same,..
In FILE SYSTEMS, you are not able to Share nothing.
1st. Go to Shared Folders, and create the Shared Folders.
2nd. Go to SMB/CIFS, where you will be able to Share the Shared Folders.
To share stuff you need to make file system on disks 1st. Then you create share stuff from in it. My problem is I see the disk parts I used to view at omv 3. Now they don't show up at file system tab at web ui. But I can see em on terminal with lsblk. I guess I need to mount them to /srv /..
-
Ok, new little clue.
When I put a WD PAssport 4tb last year, I had a similar situation, and the issue was that the NAME of this HDD was so long with blank spaces, and I should need to short it and remove the blank spaces..
With OMV 4, the issue was not there.
Then from "My Passport Blue", I canged to "4Tb", and then the system recognized it.
But I did the change in other OS.
Link to this topic: RE: Issues with Mount a WD 4tb My Passport HDD and with install PlugIns.
-
What's the output of wipefs -n dev/sdb whats doesn't make sense is why the boot drive is not showing
-
What's the output of wipefs -n dev/sdb whats doesn't make sense is why the boot drive is not showing
Why the hell i wanna delete sdb?
-
not to blindly run every command you are suggested to run, but with the -n option, wipefs will not do anything. It will just show the filesystem signatures on that drive.
-
not to blindly run every command you are suggested to run, but with the -n option, wipefs will not do anything. It will just show the filesystem signatures on that drive.
-
it shows zfs member. i didnt recall anything i did with zfs all my hdds are ext4 and no raid.
-
i didnt fresh install if it changes anything but it doesnt
-
-
-f shows these
-
-
Why the hell i wanna delete sdb
I would never suggest to someone to delete anything unless it was the norm and as was pointed out this displays the partition signatures on the disk.
it shows zfs member. i didnt recall anything i did with zfs
This has come up more than once on the forum when a user has moved from one version to another, why, no one really knows other than the base OS and the kernel have moved the goalposts.
Shall i try these. i searched the zfs signatures topics. and found
That is the norm, wash, rinse, repeat until all the zfs signatures have gone.
-
I would never suggest to someone to delete anything unless it was the norm and as was pointed out this displays the partition signatures on the disk.
This has come up more than once on the forum when a user has moved from one version to another, why, no one really knows other than the base OS and the kernel have moved the goalposts.
That is the norm, wash, rinse, repeat until all the zfs signatures have gone.
Thank you for answers. Sorry didn't have so much experience. So didn't know - n stands for no act. OK then I will erase till no zfs. The weird thing is omv 3 see drives as usual it should be.. I don't see the gimmick why new version out these signature upfront..
-
The weird thing is omv 3 see drives as usual it should be.. I don't see the gimmick why new version out these signature upfront..
The only two differences is the debian version and the kernel, the only other way might be to do this is with a spare drive, prepare the drive in OMV5 mount it in OMV3 copy data from one of the offending drives so you have a backup. Attach the drive from OMV3 wipe it, create a file system and copy the data back from the backup, depends on how many zfs signatures are detected and how long it would take.
Jetzt mitmachen!
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!