@AlexPDX said in Storage Group and Storage Node explained for dummies:
1.5.8 keep remembering the Windows Keys in the Host
Yes that info is stored in the database. With that said, the upgrade should not erase keys. If it does then there is a bug in the upgrade script. AFAIK nothing is ever deleted from the database during an upgrade. A schema change will add or remove fields but not data.
@Fog_Newb said in Unable to restore 4k cluster size NVME:
This image was captured from the 4k block NVME
Yeah right, I see. Converting this to 512 byte block size is as easy as multiplying every sector count number by 8 - result:
/dev/nvme0n1p1 : start= 2048, size= 1083392, type=DE94BBA4-06D1-4D40-A16A-BFD50179D6AC, uuid=7ED58F36-04DC-4D18-9CD2-C7D832B9F61E, name="Basic data partition", attrs="RequiredPartition GUID:63"
/dev/nvme0n1p2 : start= 1085440, size= 614400, type=C12A7328-F81F-11D2-BA4B-00A0C93EC93B, uuid=A6A8E7DC-0655-4E99-A1FB-5F42A76303A7, name="EFI system partition", attrs="GUID:63"
/dev/nvme0n1p3 : start= 1699840, size= 32768, type=E3C9E316-0B5C-4DB8-817D-F92DF00215AE, uuid=2BBCB147-BA4C-4545-806A-57770D209F01, name="Microsoft reserved partition", attrs="GUID:63"
/dev/nvme0n1p4 : start= 1732608, size= 498384896, type=EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, uuid=BECEA3AA-9442-42BF-B497-A3E0FF5D7D94, name="Basic data partition"
Should fit on a 512 byte sector size disk with 250 GB roughly (a little bit less would even do).