jodia54d

Thank you @JorgeB! I now see the SSD in my Unassigned and is mountable. Will try to figure out how best to back up the data there. Thank you very much once again!

Welcome to sfdisk (util-linux 2.38.1). Changes will remain in memory only, until you decide to write them. Be careful before using the write command. Checking that no-one is using this disk right now ... OK Disk /dev/sdh: 931.51 GiB, 1000204886016 bytes, 1953525168 sectors Disk model: CT1000MX500SSD1 Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes sfdisk is going to create a new 'dos' disk label. Use 'label: <name>' before you define a first partition to override the default. Type 'help' to get more information. >>> 64 Created a new DOS disklabel with disk identifier 0xa346a5e6. Created a new partition 1 of type 'Linux' and of size 931.5 GiB. Partition #1 contains a btrfs signature. Do you want to remove the signature? [Y]es/[N]o: I saw you provided similar help/instructions in similar post ... I assume I should select [N]o?

Thanks @JorgeB Welcome to sfdisk (util-linux 2.38.1). Changes will remain in memory only, until you decide to write them. Be careful before using the write command. Checking that no-one is using this disk right now ... OK Disk /dev/sdh: 931.51 GiB, 1000204886016 bytes, 1953525168 sectors Disk model: CT1000MX500SSD1 Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes sfdisk is going to create a new 'dos' disk label. Use 'label: <name>' before you define a first partition to override the default. Type 'help' to get more information. >>> 2048 Created a new DOS disklabel with disk identifier 0xf6a551ca. Created a new partition 1 of type 'Linux' and of size 931.5 GiB. /dev/sdh1 : 2048 1953525167 (931.5G) Linux /dev/sdh2:

Need help please! - yet another cache drive unmountable issue. I'm trying to replace existing 1TB SSD cache drive with an NVMe drive, and did the following: Stopped all running Dockers/VMs Disabled VMs, disabled Docker Changed all shares that are using cache to cache-primary, array-secondary and invoked Mover Mover stuck/stalled - tried to manually delete files in cache drive but there were read-only (30) errors Installed new NVMe drive, stopped array and selected new NVMe drive as new cache drive At this point, the old SSD cache drive becomes unmountable: unsupported or no file system. I've read quite a few forum posts of similar problems, and tried btrfs zero-log /dev/sdh -- this returns "No valid Btrfs, could not open ctree" I suspect my SSD cache drive had some errors/file corruption to begin with. I don't have critical data on there, but most of my appdata, domain and system files were stored in cache. Is the SSD cache drive data still salvagable? Now that I have a new NVMe drive installed, should I just set that as the cache drive, format, and will all my dockers and VMs be able to run again? Thank you in advance to anyone who can help! unraid-54d-diagnostics-20241006-0037.zip