CSwain

Members
  • Posts

    4
  • Joined

  • Last visited

Everything posted by CSwain

  1. FWIW, I removed one of the disks that I knew was NTFS and was able to use testdisk on my windows box to recover the two partitions. When I reinstalled it, UD recognized it to mount right away and it seems fine. Running the first of the other two disks now, the first of which doesn't have recognizable partitions, so it's running a cylinder scan. Then we find out if testdisk handles xfs. I still have no idea why the partition info is unreadable on all three drives in the first place, as the drives were spun down when the machine lost power.
  2. Looking at the unassigned devices.cfg log reminds me that I previously changed the label on all three of these. There is a reference to the previous label on the mountpoint of the 8TB disk, but I can't find any other references to the old labels, and I didn't take a screenshot or anything. Not sure if that helps, but I figure more info is better.
  3. Hello, My UPS shut down for no apparent reason, and when my Unraid server came back up, the three disks I had as unassigned devices all show "format" instead of "mount", with no file system noted. They were previously formatted, mounted, tested, and then spun down, as I hadn't yet decided how I was going to use them. I'm pretty sure one was xfs and the other two were NTFS. I can reformat as I'm not losing anything, but why would this happen? Is there any other way to get the system to recognize them without reformatting? One of them, which used to be an array disk, is also showing in its log info: Mar 26 11:10:11 Robert root: /usr/sbin/wsdd -i bro Mar 26 11:10:11 Robert wsdd[5646]: Invalid interface name bro I think I may have had a share set on that one to backup some data. The other two aren't showing this, but still otherwise only allow formatting. Unraid 6.9.2, latest UD (updated after restart today, just in case). I did try a restart, but it made no difference. Edit: Diagnostics attached. robert-diagnostics-20220326-1215.zip