M.2's storage pool for VMs... single or multi volume?

[iPyDB_6]

recently, yesterday, installed 923+, DSM 7.2.2-72806, 4 x 8TB ironwolf drives, 16gb ram, 2 x M.2 Sandisk wd_black sn850x 2tb.

using 007revad's script(s) v2.0.29, the M.2's were setup as SHR-1. i tried both these options just to see if both would be configured and they were.

1) Multi Volume (DSM 7 default)
2) Single Volume

both times this error(?) message was returned:

Starting creation of the storage pool.
255 synostgpool failed to create storage pool!

though in DSM storage manager shows both M.2's as healthy allocated to "storage pool 2". maybe that error msg was simply due to DSM using the drive?.

#-------------------------------------------------------------------------------
Question: regarding installing 1-2 linux VM's in this M.2 storage pool... is single volume or multi volume the preferred way with VM's installed?

 

[Telos]

Why would multi-volume be preferred, unless volume caps were in play?

 

[007revad]

@iPyDB_6

With a DS923+ you didn't need Synology_M2_volume. With just Synology_HDD_db you're able to create M.2 storage pools in Storage Manager.

I would setup the 2 x WD Black SN850X as RAID 1 (or SHR-1) with a single volume.

  Starting creation of the storage pool.
  255 synostgpool failed to create storage pool!

That seems to happen too often, even though the storage gets created okay.

It used to say 0 synostgpool failed to create storage pool! but "0" means success. I had made a change in v2.0.8 to show the correct synostgpool return code. Now that I know some people get 255 I've changed the script to not show an error. Instead it will just show "synostgpool return code: $code" if "$code" is not 0 or 255.

 

[iPyDB_6]

@iPyDB_6

With a DS923+ you didn't need Synology_M2_volume. With just Synology_HDD_db you're able to create M.2 storage pools in Storage Manager.

I would setup the 2 x WD Black SN850X as RAID 1 (or SHR-1) with a single volume.

  Starting creation of the storage pool.
  255 synostgpool failed to create storage pool!

That seems to happen too often, even though the storage gets created okay.

It used to say 0 synostgpool failed to create storage pool! but "0" means success. I had made a change in v2.0.8 to show the correct synostgpool return code. Now that I know some people get 255 I've changed the script to not show an error. Instead it will just show "synostgpool return code: $code" if "$code" is not 0 or 255.

>With a DS923+ you didn't need Synology_M2_volume. With just Synology_HDD_db you're able to create M.2 storage pools in Storage Manager.

oops. you probably explained that on your github site and it didn't sink in. lol

your "TODO" & " DONE" notes were informative whereby single volume made more sense to me too but wanted to ask and ensure that, before going further with setting this unit up. and too, i wasn't in the know about "overprovisioning" anyways.

not showing an error msg and testing not 0 or 255 won't be a confusing/concerning to some users. smart.

many thanks!

 

[iPyDB_6]

Why would multi-volume be preferred, unless volume caps were in play?

honestly, can't answer that. what little i know, the "overprovisioning" avail with going with multi-volume wasn't really on my radar, currently. and for my use case here at home, single volume seemed more appropriate and keeping things simple, for my usage. but had to ask before i got to far into the setup of this 923+.