I had an unassigned drive that had a filesystem error and unmounted itself. It is just being used for security camera footage so I rebooted and tried to format the drive. It is now claiming it is 2.15GB when its a 1TB nvme drive. The format is also failing, see below. Should I just replace this drive, or is it something I can salvage?

Oct  2 08:48:33 unraid emhttpd: online: MN-5236_SSD-5236 (nvme1n1) 4096 524288
Oct  2 08:48:34 unraid emhttpd: read SMART /dev/nvme1n1
Oct  2 08:52:03 unraid unassigned.devices: Formatting device '/dev/nvme1n1'.
Oct  2 08:52:03 unraid unassigned.devices: Device '/dev/nvme1n1' block size: 4194304.
Oct  2 08:52:03 unraid unassigned.devices: Clearing partition table of disk '/dev/nvme1n1'.
Oct  2 08:52:06 unraid unassigned.devices: Successfully reloaded partition table on device '/dev/nvme1n1' with partprobe.
Oct  2 08:52:07 unraid unassigned.devices: Creating Unraid compatible mbr partition on disk '/dev/nvme1n1'.
Oct  2 08:52:14 unraid unassigned.devices: Successfully reloaded partition table on device '/dev/nvme1n1' with partprobe.
Oct  2 08:52:15 unraid unassigned.devices: Format device '/dev/nvme1n1' with 'xfs' filesystem.
Oct  2 08:52:15 unraid unassigned.devices: Format command: /sbin/mkfs.xfs -f '/dev/nvme1n1p1' 2>&1
Oct  2 08:52:15 unraid unassigned.devices: Format failed: Error accessing specified device /dev/nvme1n1p1: No such file or directory Usage: mkfs.xfs /* blocksize */#011#011[-b size=num] /* config file */#011[-c options=xxx] /* metadata */#011#011[-m crc=0|1,finobt=0|1,uuid=xxx,rmapbt=0|1,reflink=0|1, #011#011#011    inobtcount=0|1,bigtime=0|1] /* data subvol */#011[-d agcount=n,agsize=n,file,name=xxx,size=num, #011#011#011    (sunit=value,swidth=value|su=num,sw=num|noalign), #011#011#011    sectsize=num,concurrency=num] /* force overwrite */#011[-f] /* inode size */#011[-i perblock=n|size=num,maxpct=n,attr=0|1|2, #011#011#011    projid32bit=0|1,sparse=0|1,nrext64=0|1] /* no discard */#011[-K] /* log subvol */#011[-l agnum=n,internal,size=num,logdev=xxx,version=n #011#011#011    sunit=value|su=num,sectsize=num,lazy-count=0|1, #011#011#011    concurrency=num] /* label */#011#011[-L label (maximum 12 characters)] /* naming */#011#011[-n size=num,version=2|ci,ftype=0|1] /* no-op info only */#011[-N] /* prototype file */#011[-p fname] /* quiet */#011#011[-q] /* realtime subvol */#011[-r extsize=num,size=num,rtdev=xxx] /* sectorsize */#011[-s size=num] /* version */#011#011[

unraid-diagnostics-20241002-0904.zip

Edited October 2, 20241 yr by bmrowe
added diags

Reboot and try again, if the same try formatting with an Unraid pool, instead of UD.

5 minutes ago, JorgeB said:

Reboot and try again, if the same try formatting with an Unraid pool, instead of UD.

I'm not following - what do you mean by formatting with an unraid pool?

Create a new pool, assign the device, format it after array start.

Ah, thanks for the tip. Unfortunately it didn't work. I noticed the nvme was showing up with a different name in unraid. I googled the new name and saw a slew of people having this same issue where the ADATA S70 Blade nvme turns into a mn-5236 with 2.1GB of capacity. Some type of hardware/chip issue.

37 minutes ago, bmrowe said:

where the ADATA S70 Blade nvme turns into a mn-5236 with 2.1GB of capacity

Yep, a name/capacity change usually indicates a device problem