OMV 5 doesn't let me create shared folders

Carlo85 · 22. Dezember 2019

hi
i'm running omv 5 on buster, and on an armel, so no plugins, i guess
omv is working fine enough but for the shared folders section: when i click on choose a device i am given none, so i cannot create any

this is my fdisk:

Code

Disk /dev/mtdblock0: 1 MiB, 1048576 bytes, 2048 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




Disk /dev/mtdblock1: 512 KiB, 524288 bytes, 1024 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




Disk /dev/mtdblock2: 512 KiB, 524288 bytes, 1024 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




Disk /dev/mtdblock3: 512 KiB, 524288 bytes, 1024 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




Disk /dev/mtdblock4: 10 MiB, 10485760 bytes, 20480 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








Disk /dev/mtdblock6: 47.8 MiB, 50069504 bytes, 97792 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




Disk /dev/mtdblock7: 10 MiB, 10485760 bytes, 20480 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




Disk /dev/mtdblock8: 47.8 MiB, 50069504 bytes, 97792 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




Disk /dev/sda: 298.1 GiB, 320072933376 bytes, 625142448 sectors
Disk model: WDC WD3200KS-00P
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: 0xd632e2ad


Device     Boot Start       End   Sectors   Size Id Type
/dev/sda1        2048 625141759 625139712 298.1G 83 Linux




Disk /dev/sdb: 2.7 TiB, 3000592982016 bytes, 5860533168 sectors
Disk model: WDC WD30EFRX-68E
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: D1070018-0D36-4566-AF9E-C1DC8C69E518


Device      Start        End    Sectors  Size Type
/dev/sdb1    2048     999423     997376  487M Linux swap
/dev/sdb2  999424 5860532223 5859532800  2.7T Microsoft basic data




Disk /dev/md0: 2.7 TiB, 3000079745024 bytes, 5859530752 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes

Alles anzeigen

macom · 23. Dezember 2019

Did you mount filesystems in the GUI of OMV?

geaves · 23. Dezember 2019

Zitat von macom

Did you mount filesystems in the GUI of OMV?

I was just looking at this this, what makes little sense is line 72, 73 and 76. Line 73 would suggest that the 3TB was not wiped correctly and why is there a swap partition on that drive. There is also a suggested Raid setup, line 76 with one drive??

Carlo85 · 23. Dezember 2019

Zitat von geaves

I was just looking at this this, what makes little sense is line 72, 73 and 76. Line 73 would suggest that the 3TB was not wiped correctly and why is there a swap partition on that drive. There is also a suggested Raid setup, line 76 with one drive??

i have no idea why it's like that: all i know is that the hd was first used by the nsa 325 v2 and worked fairly, it kept working after i turned the nsa into a debian kirkwood machine, but recently i had to format it cause of some broken update: i have saved the old fstab if you want to check it
the swap i do have no idea why is there, but... if i can avoid struggling a 3 TB hd it'll stay there

is there any way to polish the array?
besides it's an array which works with one partition only, so if i can get rid of it without messing and moving files i'd be most happy to do it

Carlo85 · 23. Dezember 2019

Zitat von macom

Did you mount filesystems in the GUI of OMV?

i'm not sure what you mean but in omv, under filesystemm there are
/dev/sdb1
/dev/md0
/dev/sda1
the all have yes under "montare" (mount)
but they all have no under "citato" (quoted?)

geaves · 23. Dezember 2019

Zitat von Carlo85

if i can avoid struggling a 3 TB hd it'll stay there

TBH the only way forward is to start again, the reason the swap partition is on that drive is because the drive was connected when the OMV was installed, that's a best guess.

That 3TB has a Microsoft partition on it!!

You need to re install without that drive connected, once OMV is working correctly plug the drive in wipe it and then format it.

Zitat von Carlo85

is there any way to polish the array?
besides it's an array which works with one partition only, so if i can get rid of it without messing and moving files i'd be most happy to do it

my Grandmother had a saying "You can't make a silk purse out of a pig's ear"

Carlo85 · 23. Dezember 2019

if only i could persuade that pig to be a bug............
just seems absurd that it isn't recognizing it while it did for years

i haven't enough free space in any of my pcs to place 2 or 3 TB of stuff: should i really really wipe everything from that HD?

geaves · 23. Dezember 2019

Zitat von Carlo85

if only i could persuade that pig to be a bug

unfortunately not, but whatever you do whether it be a re install or an 'attempted' repair you need to get the data off that drive if you want to ensure that you don't lose anything.

Jetzt mitmachen!