November 27, 20223 yr I tried all I could but I cannot stop the array... Any idea? monstruo-diagnostics-20221113-1102.zip
November 27, 20223 yr Community Expert Looks like disk11, 7EZ9, sdg disconnected and reconnected as sdz so Unraid lost track of it. SMART for 7EZ9 looks OK but no SMART tests have been run. Probably connection issues. You will have to hard power down, check connections, power and SATA, both ends, including splitters. Then reboot and post new diagnostics.
November 28, 20223 yr Author Actually a couple of cables looks faulty and I ordered new ones. I think is better to keep everything on hold till I receive the new cables...
December 9, 20223 yr Author Here I am again.... I changed the cables and I addews a new PSU togather with the original one since I was told that, in order to have a more stable configuration I should opt for max 4 SATA connector per cable (originally they were 7). Apparently all is good now at least on the hardware side... Now I have a new problem going on! I started the array and the Parity 2 disk il rebuilding (keep happening since I installed few weeks back) and I have some errors on one of the disks (disk 15). I hope this is not relared Once again with the cables since I really do not know what to do more than that (changed all of them with high quality new ones). On top of that I see that my Plex and Krusader dockers are unrensponsive (they do not start at all) and I can see tons of error message on the screen saying: Metadata Corruption detected.... Unmount and run xfs_repair... I am kind of frustrared since this is getting to a point that I solve 1 problem and I get 2 new ones as soon as the first is solved.... So I am thinking of reinstalling Unraid from scratch and have a clean configuration... Any suggestion? monstruo-diagnostics-20221209-0939.zip
December 9, 20223 yr Community Expert Disk9 appears to be failing, run an extended SMART test to config, also check filesystem on disk12.
December 9, 20223 yr Author Ok... I tried to do the extended SMART test on Disk9 but seems it is not working... when I try to start it in less than a second it goes back to start)... Done the filesistem check and posting the new diagnostic monstruo-diagnostics-20221209-1523.zip
December 9, 20223 yr Author BTW Krusader is still not working and Plex docker completely disappeared from Docker Containers
December 9, 20223 yr Community Expert SMART test is failing, drive needs to be replaced, if the fs on disk12 is fixed reboot and post new diags after array start.
December 10, 20223 yr Community Expert 6 minutes ago, gideva said: Just realized that now disk12 has 5.94Tb free... (it was full before)... According to the diagnostics you just posted disk12 has 2TB free and is 65% full. Are you sure you mean disk12?
December 10, 20223 yr Author Ok this is the situation now... After running the check filesystem the disk wont mount anymore (says Wrong). Apparently disk12 (that was sdl) disconnected and reconnected as sdx. So.... what is next? monstruo-diagnostics-20221210-1141.zip
December 10, 20223 yr Community Expert Diags posted are still completely spammed with disk12 fs corruption, reboot and post new diags after array start.
December 10, 20223 yr Community Expert Everything looks fine so far but disk12 appears to have been formatted.
December 10, 20223 yr Author Sorry guys this is a mess!!! I just realized that the disks are all mixed up... Originally disk12 was WCC4E5PX4XZ7 (with 3.79TB used and 211GB free) - 4TB, then ZR12MGFR - 6 TB (3.88 TB with 2.12 TB free) and now ZR12MGFR is still in the same position but appears it has 5.94 TB of free space... I am afraid I messed up with the array and I cannot sort out things now!!!
December 10, 20223 yr Author If I try to mount WCC4E5PX4XZ7 now says that is a NEW DEVICE and if I start the array all the data will be overritten.... Already lost 6TB of data apparently (I do not know how I manage to format a full disk...) would like to avoid to loose also other 4TB... Any suggestion (a part DO NOT FORMAT FULL DISKS)?
December 10, 20223 yr Community Expert If you add a new disk to a parity protected array it will be cleared (wiped) first, you can mount the disk with UD first to see if there's any data there.
December 10, 20223 yr Author I tried to mount with UD but the mountpb is grayed and does not let me do it....
December 10, 20223 yr Community Expert That suggests there's no valid fs on that disk, post the output of fdisk -l /dev/sdX (replace X with correct letter) and blkid
December 10, 20223 yr Author Here you have (hope is what you are asking): The backup GPT table is not on the end of the device. Disk /dev/sdy: 3.64 TiB, 4000787030016 bytes, 7814037168 sectors Disk model: WDC WD40EZRZ-00W 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: 3B1388DB-2DE5-4EE0-9610-618966CC50A5 Device Start End Sectors Size Type /dev/sdy1 64 7814037134 7814037071 3.6T Linux filesystem /dev/sda1: LABEL_FATBOOT="UNRAID" LABEL="UNRAID" UUID="5E44-1B01" BLOCK_SIZE="512" TYPE="vfat" /dev/loop1: TYPE="squashfs" /dev/md11: UUID="e5e91b75-ab28-4e86-a2ec-a12831114fae" BLOCK_SIZE="512" TYPE="xfs" /dev/sdf1: UUID="61b9a789-f119-4854-8b43-6d647c82c95a" BLOCK_SIZE="512" TYPE="xfs" PARTUUID="28f95189-5225-4ea1-9b59-a7be5e65c07b" /dev/md8: UUID="689b68aa-63e2-4f0c-9a97-89a96249811e" BLOCK_SIZE="512" TYPE="xfs" /dev/sdo1: UUID="d58b6acc-80a4-42b2-8929-b8bd471d3650" BLOCK_SIZE="512" TYPE="xfs" PARTUUID="2ee78350-0b64-410b-947e-80559ab6a476" /dev/sdw1: UUID="9fad86a9-363f-4d45-9713-bf70164c2efb" BLOCK_SIZE="512" TYPE="xfs" PARTUUID="4d3db4d8-02e7-4375-bcaf-ae861a8e821a" /dev/sdd1: UUID="e5e91b75-ab28-4e86-a2ec-a12831114fae" BLOCK_SIZE="512" TYPE="xfs" PARTUUID="e6e6a390-e3c1-68a8-94b2-b9b546ec36b0" /dev/md6: UUID="9fad86a9-363f-4d45-9713-bf70164c2efb" BLOCK_SIZE="512" TYPE="xfs" /dev/md18: UUID="823dd1ca-be31-47ba-8d5c-e391916c25ad" BLOCK_SIZE="512" TYPE="xfs" /dev/sdm1: UUID="2334d706-96f5-472a-9a4e-a5e942893aa6" BLOCK_SIZE="512" TYPE="xfs" PARTUUID="21b90859-da06-430e-bd0c-ad95e1b89cd0" /dev/sdu1: UUID="3786651d-896f-4f89-9437-483fefd06d03" UUID_SUB="2187370a-efa0-42f2-92fd-b0cea9b516f9" BLOCK_SIZE="4096" TYPE="btrfs" /dev/sdb1: UUID="6f08c371-2a2f-4856-b3f6-2e1f3f8e5aaa" BLOCK_SIZE="512" TYPE="xfs" PARTUUID="6d3c580e-3a09-451e-906c-77bfe904ec15" /dev/md4: UUID="61b9a789-f119-4854-8b43-6d647c82c95a" BLOCK_SIZE="512" TYPE="xfs" /dev/md16: UUID="def0418b-e736-442c-8f0a-a67bbd2c4d67" BLOCK_SIZE="512" TYPE="xfs" /dev/sdk1: UUID="ad7c72f4-a08b-4bc0-b32b-737700c19bf1" BLOCK_SIZE="512" TYPE="xfs" PARTUUID="0833ac48-fa4a-4f71-b1ee-ba4c436e2342" /dev/sds1: UUID="a3c70469-fe5f-4ef8-84e6-38c1827ff9d0" BLOCK_SIZE="512" TYPE="xfs" PARTUUID="60695e28-dac8-4ea7-93d7-7f9f187aec4b" /dev/md2: UUID="6f08c371-2a2f-4856-b3f6-2e1f3f8e5aaa" BLOCK_SIZE="512" TYPE="xfs" /dev/md14: UUID="ad7c72f4-a08b-4bc0-b32b-737700c19bf1" BLOCK_SIZE="512" TYPE="xfs" /dev/sdi1: UUID="2eb756cd-0432-42ee-991e-b1c796e8c241" BLOCK_SIZE="512" TYPE="xfs" PARTUUID="7531d334-cb00-45ba-9ae0-f4ed1ca87715" /dev/sdq1: UUID="689b68aa-63e2-4f0c-9a97-89a96249811e" BLOCK_SIZE="512" TYPE="xfs" PARTUUID="b070e132-1a41-4b9f-94ed-fe069c7f4ef2" /dev/md12: UUID="2334d706-96f5-472a-9a4e-a5e942893aa6" BLOCK_SIZE="512" TYPE="xfs" /dev/sdz1: UUID="bf2d1d37-309b-4144-a0f3-d29bec8983d6" BLOCK_SIZE="512" TYPE="xfs" PARTUUID="ee10c7e0-1a72-4691-933a-409e4786831b" /dev/md9: UUID="00633fe3-1e50-41b1-9987-fa8c4d04d92a" BLOCK_SIZE="512" TYPE="xfs" /dev/loop0: TYPE="squashfs" /dev/md10: UUID="69d83396-a98c-4624-9633-1ea9ecbf3f9d" BLOCK_SIZE="512" TYPE="xfs" /dev/sdx1: UUID="823dd1ca-be31-47ba-8d5c-e391916c25ad" BLOCK_SIZE="512" TYPE="xfs" PARTUUID="fb326c0b-ab95-413a-b1c1-2766fb881247" /dev/sde1: UUID="2cad65d3-9481-4075-990e-8e518d0d4c88" BLOCK_SIZE="512" TYPE="xfs" PARTUUID="51297471-b9ac-4a5a-8128-f29177b13257" /dev/md7: UUID="858b5c7a-00af-433b-bfc0-23c62d9e1b82" BLOCK_SIZE="512" TYPE="xfs" /dev/md19: UUID="bf2d1d37-309b-4144-a0f3-d29bec8983d6" BLOCK_SIZE="512" TYPE="xfs" /dev/sdn1: UUID="2bb52a8e-818a-4b9e-ac78-fedff1a9716d" BLOCK_SIZE="512" TYPE="xfs" PARTUUID="5dfc7722-3581-4423-bdcd-44f736c923da" /dev/sdv1: UUID="3786651d-896f-4f89-9437-483fefd06d03" UUID_SUB="a4fea608-e78b-42d8-942e-69851e4e85cb" BLOCK_SIZE="4096" TYPE="btrfs" /dev/sdc1: UUID="69d83396-a98c-4624-9633-1ea9ecbf3f9d" BLOCK_SIZE="512" TYPE="xfs" PARTUUID="38737510-474b-42d5-817e-779574c7bfdd" /dev/md5: UUID="a3c70469-fe5f-4ef8-84e6-38c1827ff9d0" BLOCK_SIZE="512" TYPE="xfs" /dev/md17: UUID="2bb52a8e-818a-4b9e-ac78-fedff1a9716d" BLOCK_SIZE="512" TYPE="xfs" /dev/sdl1: UUID="593561e8-412c-4978-b02f-ef47867ef451" BLOCK_SIZE="512" TYPE="xfs" PARTUUID="15d31c81-2be0-4142-8d1a-25a14f166c3e" /dev/sdt1: UUID="858b5c7a-00af-433b-bfc0-23c62d9e1b82" BLOCK_SIZE="512" TYPE="xfs" PARTUUID="40da6839-f5d6-4f0c-a8c0-38f993a68833" /dev/md3: UUID="2eb756cd-0432-42ee-991e-b1c796e8c241" BLOCK_SIZE="512" TYPE="xfs" /dev/md15: UUID="d58b6acc-80a4-42b2-8929-b8bd471d3650" BLOCK_SIZE="512" TYPE="xfs" /dev/sdj1: UUID="def0418b-e736-442c-8f0a-a67bbd2c4d67" BLOCK_SIZE="512" TYPE="xfs" /dev/md1: UUID="2cad65d3-9481-4075-990e-8e518d0d4c88" BLOCK_SIZE="512" TYPE="xfs" /dev/md13: UUID="593561e8-412c-4978-b02f-ef47867ef451" BLOCK_SIZE="512" TYPE="xfs" /dev/sdh1: UUID="00633fe3-1e50-41b1-9987-fa8c4d04d92a" BLOCK_SIZE="512" TYPE="xfs" PARTUUID="570c3c0a-6737-405b-909a-5f937980b0e1" /dev/sdr1: PARTUUID="7a17a666-2af3-03fd-0003-a388a2245fd9" /dev/sdp1: PARTUUID="912aef58-75f0-48c4-a83d-fa181dab4992"
December 13, 20223 yr Author Got this message after mount -v -t xfs /dev/sdy1 /x root@Monstruo:~# mount -v -t xfs /dev/sdy1 /y mount: /y: wrong fs type, bad option, bad superblock on /dev/sdy1, missing codepage or helper program, or other error. dmesg(1) may have more information after failed mount system call.
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.