Mike Henderson

I do not have any other disks at the moment. !!RESOLVED!! I hope that this long reply doesn't violate any rules, but I'd like to document the problem I had in case other users come across it. I have been trying for a couple of days to search for a solution and attempted using parted/fdisk/wipefs to resolve the issue via ssh. Those tools would report that they had made changes and written them to the disk but it never actually seemed to take. The path that lead to the solution was that when I tried to use fdisk to create an empty gpt partition on the drive, I was met with a warning "The old atari signature will be removed by a write command". I would finish in fdisk and exit with the write command but when I immediately checked again the atari signature was still on the disk. I have been trying to get away from giving Google all my information so I was doing all of my research in Duck Duck Go. So when I quoted this warning and searched for the topic, DDG returned no results. On a whim, I decided to quote this warning and throw it at Google. I got a match for an old Reddit post titled "Unsupported Partition Layout" - Unable to format drive(s)". This was the same message UnRaid was giving me in the Main share window. The Reddit article described the same efforts I had been through and the post was marked resolved. The problem the entire time was with the BIOS setting on my motherboard. It had a default setting which set the last two SATA ports on my motherboard to IDE. After changing these settings to SATA, I rebooted and was still met with the Unmountable warning on entering the MAIN screen. Though this time I spun down the problem disk, launched the syslog and then selected the FORMAT option. I watched as the syslog reported that it was actually able to create the partition and mount the drive! It is now happily added to my array and all is well.

I do not have any other disks at the moment.

Version: 6.8.3 I recently purchased a new 3TB drive and attempted to add it to my array (1 -3TB drive and 2 500GB Drives). I shutdown my rig and physically added the drive and powered back up. This was a new drive and I thought adding it was a simple as stopping the array and adding this new drive. I saw tha there was an option to format this new drive on the Main screen, I clicked this "format" button and the botom of the screen reported that "servers had started". I was met with the Unmountable issue. I decided to research adding a new drive and found that I should have Pre-Cleared the drive first. I removed the drive from the array and ran the pre-clear tool. It completed successfully but then reported that signatures did not match? The system still seemed to recognize the drive and I attempted to add it back to the array. I was met again with the Unmountable issue. I again attempted to run the format process from the Main screen. It then ran like before and completed quickly but with no change. I ran the SMART test and it reported no issues. I then fell down the hole of installing plugins and tools to try and fix the issue. After adding the pre-clear tool, common issues, and unassigned devices, I saw no problems. I kept looking into these forums and kept trying different things. I then found the option to run the syslog while also attempting to run the Format option from the main screen. Then I saw that the partition was being created but was still unmountable. I copied the syslog entry from that action below. I read the "READ ME FIRST" post to make sure I included everything required. I hope I got it all! Thank you in advance for any help you can provide, I feel like it will be something simple I overlooked. Mar 23 09:55:23 Tower kernel: mdcmd (47): nocheck pause Mar 23 09:55:24 Tower emhttpd: writing GPT on disk (sdb), with partition 1 byte offset 32K, erased: 0 Mar 23 09:55:24 Tower emhttpd: shcmd (977): sgdisk -Z /dev/sdb Mar 23 09:55:25 Tower rc.diskinfo[6968]: SIGHUP received, forcing refresh of disks info. Mar 23 09:55:25 Tower root: Creating new GPT entries in memory. Mar 23 09:55:25 Tower root: GPT data structures destroyed! You may now partition the disk using fdisk or Mar 23 09:55:25 Tower root: other utilities. Mar 23 09:55:25 Tower emhttpd: shcmd (978): sgdisk -o -a 8 -n 1:32K:0 /dev/sdb Mar 23 09:55:27 Tower root: Creating new GPT entries in memory. Mar 23 09:55:27 Tower root: The operation has completed successfully. Mar 23 09:55:27 Tower emhttpd: shcmd (979): udevadm settle Mar 23 09:55:27 Tower emhttpd: shcmd (980): mkdir -p /mnt/disk4 Mar 23 09:55:27 Tower emhttpd: /mnt/disk4 mount error: Unsupported partition layout Mar 23 09:55:27 Tower emhttpd: shcmd (981): umount /mnt/disk4 Mar 23 09:55:27 Tower root: umount: /mnt/disk4: not mounted. Mar 23 09:55:27 Tower emhttpd: shcmd (981): exit status: 32 Mar 23 09:55:27 Tower emhttpd: shcmd (982): rmdir /mnt/disk4 Mar 23 09:55:27 Tower emhttpd: Starting services... Mar 23 09:55:27 Tower emhttpd: shcmd (984): /etc/rc.d/rc.samba restart Mar 23 09:55:29 Tower root: Starting Samba: /usr/sbin/smbd -D Mar 23 09:55:29 Tower root: /usr/sbin/nmbd -D Mar 23 09:55:29 Tower root: /usr/sbin/wsdd Mar 23 09:55:29 Tower root: /usr/sbin/winbindd -D tower-diagnostics-20210323-0940.zip tower-smart-20210323-1007.zip tower-syslog-20210323-1417.zip