August 20, 20223 yr Hello, I have been trying to add a Toshiba drive I have to my array since I first got Unraid and I am having no luck. I have don the preclear and that went fine. The system says "The drive is precleared" but when I try to add it in as my last disk it tries and then I am face with a blank space between my first and second drive and the one that I am trying to add isn't added (I know weird right) and is still listed under unassigned. Does anyone have any thoughts on this and how to fix it or add it to the array? Thanks for any help. I am very new to Unraid.
August 20, 20223 yr Community Expert You are likely to get better informed feedback if you attach your system’s diagnostics zip file to your next post in this thread after you have attempted to add it and failed. just a thought - do you have an ad-blocker installed in your browser? This can cause problems with the Unraid GUI unless the Unraid server is where-listed, but I must admit I have not heard of it causing the symptoms you describe.
August 20, 20223 yr Author Thanks for the reply. I didn't know about the diagnostics file but will submit it. Thanks for the help. Right now it is going through a parity check after failing at what I listed with the hard drive so I hope it has the info you need. Thanks again. Oh and this happens with the GUI when I have a monitor attached to Unraid and from another computer through the web browser. I don't think there are any ad blockers on the computer that has my unraid. unraid-diagnostics-20220820-0726.zip Edited August 20, 20223 yr by chest069 Added more info
August 20, 20223 yr Community Expert Not clear what is happening, but there were a lot of OOMs in your syslog. Reboot, try again, post new diagnostics.
August 20, 20223 yr Community Expert I saw in the syslog the message Aug 19 22:33:48 Unraid emhttpd: Error: disk8: already assigned Since the disk is not a new one maybe there is something that is confusing Unraid? Not sure what is causing this but have you deleted any existing partitions, or running a preclear on it?
August 20, 20223 yr Author Ok, I will do that. Can I restart it even if it currently going through a parity check? Just want to make sure.
August 20, 20223 yr Community Expert 1 minute ago, chest069 said: Ok, I will do that. Can I restart it even if it currently going through a parity check? Just want to make sure. You do not want to attempt a preclear with a parity check running as they will BADLY affect each others performance.
August 20, 20223 yr Author Ok, but can I restart the array (stopping I assume the parity check) while it goes through the parity check by stopping the array then restarting? So I can give you the new diagnostics report?
August 20, 20223 yr Author Ok, so I took a chance and just restarted. I only ran the diagnostics and the array shows stopped. I haven't attempted to start the array or add the drive in question. Hope this helps. I just noticed the drive I was trying to add from before now says mount not preclear. newunraid-diagnostics-20220820-0934.zip Edited August 20, 20223 yr by chest069 Added more information
August 20, 20223 yr Community Expert Just to make sure there is no misunderstanding. When you say "add" you mean you are trying to put a disk in a data slot that didn't have a disk in it before? Or do you really mean you are trying to replace a disk? 49 minutes ago, chest069 said: drive I was trying to add from before now says mount not preclear If it is mountable it is not clear. Did you perhaps format it? A formatted disk (empty filesystem) isn't a clear disk.
August 20, 20223 yr Author Ok so I am just trying to add a physical drive that is already in my system to the list of drives that are part of my array. Currently I am at 7 disks the system shows and I am trying to put this one in slot 8 which is empty but then what I described at the beginning is what happens when I do that. Also once I rebooted my Unraid and it loaded the drive that I was having this whole issue with is now showing mount and no longer preclear like it did before so I wasn't sure why that happened exactly and it was something I just figured I should point out to try and help matters along. Let me know if you need anything else, the system restarted the parity check, which I know you said I can't add the new drive while that is going on. It says it will take 2 days for the parity check to finish so I can't attempt to add the drive again until then I assume based on what you told me. Thank you for the help.
August 20, 20223 yr Author root@Unraid:~# fdisk -l Disk /dev/loop0: 110.63 MiB, 115998720 bytes, 226560 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/loop1: 17.39 MiB, 18239488 bytes, 35624 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/loop2: 30 GiB, 32212254720 bytes, 62914560 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/loop3: 1 GiB, 1073741824 bytes, 2097152 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/sdc: 14.91 GiB, 16008609792 bytes, 31266816 sectors Disk model: Cruzer Glide Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x00000000 Device Boot Start End Sectors Size Id Type /dev/sdc1 * 2048 31266815 31264768 14.9G c W95 FAT32 (LBA) Disk /dev/sdd: 2.73 TiB, 3000592982016 bytes, 5860533168 sectors Disk model: DT01ABA300 Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: dos Disk identifier: 0x00000000 Device Boot Start End Sectors Size Id Type /dev/sdd1 1 4294967295 4294967295 2T 0 Empty Partition 1 does not start on physical sector boundary. Disk /dev/sdf: 3.64 TiB, 4000787030016 bytes, 7814037168 sectors Disk model: ASM105x Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: gpt Disk identifier: C41EB32B-E8A8-4031-B662-5A60794A3B2A Device Start End Sectors Size Type /dev/sdf1 64 7814037134 7814037071 3.6T Linux filesystem Disk /dev/sdg: 3.64 TiB, 4000787030016 bytes, 7814037168 sectors Disk model: EFRX-68N32N0 Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: gpt Disk identifier: F6087F31-B422-4984-8F09-0FC6F867CE58 Device Start End Sectors Size Type /dev/sdg1 64 7814037134 7814037071 3.6T Linux filesystem Disk /dev/sdh: 4.55 TiB, 5000947302400 bytes, 9767475200 sectors Disk model: Elements 2620 Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: gpt Disk identifier: 866C2FCC-A438-48E4-942C-2B39AADB3B9B Device Start End Sectors Size Type /dev/sdh1 64 9767475166 9767475103 4.5T Linux filesystem Disk /dev/sdj: 12.73 TiB, 14000519643136 bytes, 27344764928 sectors Disk model: easystore 264D Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: gpt Disk identifier: 6A6687FD-5F22-47CA-B1AA-6AEEFB3415D9 Device Start End Sectors Size Type /dev/sdj1 64 27344764894 27344764831 12.7T Linux filesystem Disk /dev/sda: 3.64 TiB, 4000786153472 bytes, 7814035456 sectors Disk model: easystore 25FB Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: gpt Disk identifier: DFF7B2D1-2A0C-44C9-919A-3BF0DEF1308A Device Start End Sectors Size Type /dev/sda1 64 7814035422 7814035359 3.6T Linux filesystem Disk /dev/sdb: 3.64 TiB, 4000786153472 bytes, 7814035456 sectors Disk model: easystore 25FB Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: gpt Disk identifier: 4762FC92-FE69-472C-BB02-C5BA377414F7 Device Start End Sectors Size Type /dev/sdb1 64 7814035422 7814035359 3.6T Linux filesystem Disk /dev/sdi: 7.28 TiB, 8001562869760 bytes, 15628052480 sectors Disk model: easystore 264D Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: gpt Disk identifier: 65A54EA3-18B9-4C45-BC45-639E1C418C38 Device Start End Sectors Size Type /dev/sdi1 64 15628052446 15628052383 7.3T Linux filesystem Disk /dev/sde: 7.28 TiB, 8001562869760 bytes, 15628052480 sectors Disk model: My Book 25EE Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: gpt Disk identifier: 61E8E2E9-404A-487B-9507-4932CF2E6E77 Device Start End Sectors Size Type /dev/sde1 64 15628052446 15628052383 7.3T Linux filesystem Disk /dev/sdk: 931.51 GiB, 1000204886016 bytes, 1953525168 sectors Disk model: ST1000DM003-1ER1 Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: gpt Disk identifier: B6C310C6-03EB-482E-9261-D44EC41E61D0 Device Start End Sectors Size Type /dev/sdk1 2048 206847 204800 100M EFI System /dev/sdk2 206848 239615 32768 16M Microsoft reserved /dev/sdk3 239616 1951326207 1951086592 930.4G Microsoft basic data /dev/sdk4 1951326208 1952497663 1171456 572M Windows recovery environment /dev/sdk5 1952499712 1953523711 1024000 500M Windows recovery environment Disk /dev/md1: 3.64 TiB, 4000786100224 bytes, 7814035352 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/md2: 3.64 TiB, 4000786100224 bytes, 7814035352 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/md3: 3.64 TiB, 4000786976768 bytes, 7814037064 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/md4: 7.28 TiB, 8001562816512 bytes, 15628052376 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/md5: 3.64 TiB, 4000786976768 bytes, 7814037064 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/md6: 4.55 TiB, 5000947249152 bytes, 9767475096 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/md7: 7.28 TiB, 8001562816512 bytes, 15628052376 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Hope this helps.
August 21, 20223 yr Author Thanks for the reply, it is this one that gives me trouble Disk /dev/sdd: 2.73 TiB, 3000592982016 bytes, 5860533168 sectors Disk model: DT01ABA300 Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: dos Disk identifier: 0x00000000 Device Boot Start End Sectors Size Id Type /dev/sdd1 1 4294967295 4294967295 2T 0 Empty
August 21, 20223 yr Community Expert 1 hour ago, JorgeB said: Which one is the drive you're trying to add? I believe it the /dev/sdd Toshiba drive. Looks like it is a 3TB drive but has an existing 2TB DOS partition allocated. I would guess that deleting that partition would solve the issue.
August 21, 20223 yr Author Thanks for the reply, how do I do that in Unraid because I am not sure. Thank you for figuring this out too.
August 21, 20223 yr If you have Unassigned Devices plugin and UD+ installed you can use Unassigned Devices to delete the partition and reformat the drive. Destructive Mode must be enabled in UD settings.
August 21, 20223 yr Author Hey, thanks for letting me know I will try that. Well I enabled the destructive mode because I have both Unassigned Devices and UD+ installed but I can't find a way to delete the partition. Is the only way to try and add it to the array? If so my array is still going through a parity check and I can't do it then. Thanks for the help again.
August 21, 20223 yr Locate the drive in the UD section of the webUI and you'll see a little + sign (assuming that "show partitions" is set to "No"). Click the + sign and you'll see the partitions with a red X next to them. Clicking the X will delete the partition. IIRC you don't need to re-format the drive if you intend to add it to the array. unRAID will clear and format it for you. There is a great video for working with UD- https://www.youtube.com/watch?v=Wz4-YlH1lTk&t=204s Hopefully this link will take you directly to the proper section of the video. If not, the whole video will probably be useful for you.
August 22, 20223 yr Author Thanks for the reply and the link to the video. I did see what you said and clicked the red X and now it says format instead of mount (greyed out). My array still hasn't completed it's parity check yet so once that finishes I will try to add it again. Thank you for all the help.
August 22, 20223 yr Author Hello, Ok, so my array finished with the parity check no problems. I try to add the drive to slot 8 of my array and nothing. So I am submitting new Diagnostics. Trying to add hd unraid-diagnostics-20220822-0721.zip
August 22, 20223 yr Community Expert can you give the output of fdisk -l again so we can check that the partition has been deleted
August 22, 20223 yr Author I apologize I thought you might want that but wasn't sure but here it is. root@Unraid:~# fdisk -l Disk /dev/loop0: 110.63 MiB, 115998720 bytes, 226560 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/loop1: 17.39 MiB, 18239488 bytes, 35624 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/loop2: 30 GiB, 32212254720 bytes, 62914560 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/loop3: 1 GiB, 1073741824 bytes, 2097152 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/sdc: 14.91 GiB, 16008609792 bytes, 31266816 sectors Disk model: Cruzer Glide Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x00000000 Device Boot Start End Sectors Size Id Type /dev/sdc1 * 2048 31266815 31264768 14.9G c W95 FAT32 (LBA) Disk /dev/sdd: 2.73 TiB, 3000592982016 bytes, 5860533168 sectors Disk model: DT01ABA300 Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: gpt Disk identifier: D990A4F7-1AFF-436B-AB6A-996099908E87 Disk /dev/sdf: 3.64 TiB, 4000787030016 bytes, 7814037168 sectors Disk model: ASM105x Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: gpt Disk identifier: C41EB32B-E8A8-4031-B662-5A60794A3B2A Device Start End Sectors Size Type /dev/sdf1 64 7814037134 7814037071 3.6T Linux filesystem Disk /dev/sdg: 3.64 TiB, 4000787030016 bytes, 7814037168 sectors Disk model: EFRX-68N32N0 Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: gpt Disk identifier: F6087F31-B422-4984-8F09-0FC6F867CE58 Device Start End Sectors Size Type /dev/sdg1 64 7814037134 7814037071 3.6T Linux filesystem Disk /dev/sdh: 4.55 TiB, 5000947302400 bytes, 9767475200 sectors Disk model: Elements 2620 Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: gpt Disk identifier: 866C2FCC-A438-48E4-942C-2B39AADB3B9B Device Start End Sectors Size Type /dev/sdh1 64 9767475166 9767475103 4.5T Linux filesystem Disk /dev/sdj: 12.73 TiB, 14000519643136 bytes, 27344764928 sectors Disk model: easystore 264D Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: gpt Disk identifier: 6A6687FD-5F22-47CA-B1AA-6AEEFB3415D9 Device Start End Sectors Size Type /dev/sdj1 64 27344764894 27344764831 12.7T Linux filesystem Disk /dev/sda: 3.64 TiB, 4000786153472 bytes, 7814035456 sectors Disk model: easystore 25FB Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: gpt Disk identifier: DFF7B2D1-2A0C-44C9-919A-3BF0DEF1308A Device Start End Sectors Size Type /dev/sda1 64 7814035422 7814035359 3.6T Linux filesystem Disk /dev/sdb: 3.64 TiB, 4000786153472 bytes, 7814035456 sectors Disk model: easystore 25FB Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: gpt Disk identifier: 4762FC92-FE69-472C-BB02-C5BA377414F7 Device Start End Sectors Size Type /dev/sdb1 64 7814035422 7814035359 3.6T Linux filesystem Disk /dev/sdi: 7.28 TiB, 8001562869760 bytes, 15628052480 sectors Disk model: easystore 264D Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: gpt Disk identifier: 65A54EA3-18B9-4C45-BC45-639E1C418C38 Device Start End Sectors Size Type /dev/sdi1 64 15628052446 15628052383 7.3T Linux filesystem Disk /dev/sde: 7.28 TiB, 8001562869760 bytes, 15628052480 sectors Disk model: My Book 25EE Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: gpt Disk identifier: 61E8E2E9-404A-487B-9507-4932CF2E6E77 Device Start End Sectors Size Type /dev/sde1 64 15628052446 15628052383 7.3T Linux filesystem Disk /dev/sdk: 931.51 GiB, 1000204886016 bytes, 1953525168 sectors Disk model: ST1000DM003-1ER1 Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: gpt Disk identifier: B6C310C6-03EB-482E-9261-D44EC41E61D0 Device Start End Sectors Size Type /dev/sdk1 2048 206847 204800 100M EFI System /dev/sdk2 206848 239615 32768 16M Microsoft reserved /dev/sdk3 239616 1951326207 1951086592 930.4G Microsoft basic data /dev/sdk4 1951326208 1952497663 1171456 572M Windows recovery environment /dev/sdk5 1952499712 1953523711 1024000 500M Windows recovery environment Disk /dev/md1: 3.64 TiB, 4000786100224 bytes, 7814035352 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/md2: 3.64 TiB, 4000786100224 bytes, 7814035352 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/md3: 3.64 TiB, 4000786976768 bytes, 7814037064 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/md4: 7.28 TiB, 8001562816512 bytes, 15628052376 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/md5: 3.64 TiB, 4000786976768 bytes, 7814037064 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/md6: 4.55 TiB, 5000947249152 bytes, 9767475096 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/md7: 7.28 TiB, 8001562816512 bytes, 15628052376 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Thanks again for the help.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.