CaptainSpalding

Found the solution. I have had this problem before. The needed IO combination needs to be selected in BIOS, in default only one of the three sata ports will be in use. Advanced >> Chipset Configuration >> South Bridge Configuration >>Flexible I/O Selection default is [PCIe x 2/Mini SAS/SATA(1:0)]

Now after changing the order of sata cables a lot of times, the missing drive is now to be seen but another drive isn't . Not even in bios. Anybody has a suggestion where to look for the problem? tower-diagnostics-20230502-1949.zip

Yes, that was nice advice, thank you! I checked the bios and it does not see the disk. I do remember that I had the same problem before and it was something to do with the sata drivers or what they are called. South and North. I have SATA 0-4 and 5-7 with their own... power settings? I think previosly it was a problem with those. Why would anybody disable a sata port btw? tower-diagnostics-20230502-0319.zip

I was putting back one hdd to my unraid case and it was connected to a back pci slot. When I was putting it in place I hit the MB with the pci bracket and a blue light lit on my Supermicro MB. It has something to do with UID, but the light was blue so I just powered down, put the disk in place and powered on. It started somekind of reboot loop, when it stopped one of my drives was not shown on the device list. I did not believe it was broken, so I started to check first the connections and then changed sata cables and different sata slots. There are not that many variations but I managed one time to have this device shown, but the other drive I changed sata cable with was not shown. I have only three sata slots I can try this with, but for some reason always one drive is shown as "no device". Obviously the disk is not damaged as it was shown in the drive list after it first went down. I had similar situation before and I bought a more powerful PSU, but I think not enough power was not the problem, but Unraid somehow made decision that the drive is not working properly because of something completely different that happened with the server. Is there any way to give Unraid a green light with this drive?

I think I figured out how this tmux works! I can use it the same way as 'screen' and not need to keep my PC on for the transfers.

Ok, thanks! I am not any kind of screen fanboy, so what is this tmux I am reading about? Same functions as screen, but is favorable for this kind of use?

My situation is that I have no internet connection for my unRAID for couple of months, but I would need to move few terabytes of files to it from an externad hd. I tried to open 'screen', but I get 'screen: command not found'. I remember that I needed to allow it from somewhere to work, but where? And I hope I do not need internet for that... I remember there was guide for screen in Wiki, but it has been removed?? Thank you in advance!

I do not get a pop-up. I tried with Firefox and Chrome. This page is where I land if I press that partion link on the main page:

Then I only get this. 🤔

From where can I do that? I found only a place where to change the device name.

I just added a non-cache disk to my server and it will give the serial number for it as the default share name. How can I change this?

Sorry, I did not know that it is called unassigned disk. I will ask there, thanks! 👍

I just added a non-cache disk to my server and it will give the serial number for it as the default share name. How can I change this?

I had a problem with my Supermicro A2SDi-4C-HLN4F motherboards integrated NIC. After upgrading to rc4 and rebooting the server did not get to network. Needed to rollback to rc3 and after worked normally. Network Controllers: Quad LAN with Intel® C3000 SoC, 1GbE

Ok, thanks! I am running rebuilt now. So rc4 no good for me?

I did screw up... I thought it needed to be unassigned when this xfs_repair is done. I did put Maintainance mode after on as the guide suggested. So my only option is to rebuild it again?

Here you are. tower-diagnostics-20220322-2050.zip

Now it wants to rebuild parity. Is that what I should do?

I took the "-n" off and looks same? Should the check be this fast (max 2 secs)? Phase 1 - find and verify superblock... - reporting progress in intervals of 15 minutes Phase 2 - using internal log - zero log... - 20:22:34: zeroing log - 476930 of 476930 blocks done - scan filesystem freespace and inode maps... - 20:22:34: scanning filesystem freespace - 96 of 96 allocation groups done - found root inode chunk Phase 3 - for each AG... - scan and clear agi unlinked lists... - 20:22:34: scanning agi unlinked lists - 96 of 96 allocation groups done - process known inodes and perform inode discovery... - agno = 30 - agno = 0 - agno = 15 - agno = 45 - agno = 75 - agno = 31 - agno = 90 - agno = 46 - agno = 76 - agno = 77 - agno = 78 - agno = 60 - agno = 91 - agno = 79 - agno = 32 - agno = 92 - agno = 80 - agno = 93 - agno = 33 - agno = 61 - agno = 47 - agno = 81 - agno = 34 - agno = 94 - agno = 62 - agno = 48 - agno = 35 - agno = 95 - agno = 63 - agno = 82 - agno = 36 - agno = 49 - agno = 83 - agno = 37 - agno = 64 - agno = 50 - agno = 38 - agno = 65 - agno = 84 - agno = 39 - agno = 66 - agno = 51 - agno = 40 - agno = 85 - agno = 52 - agno = 67 - agno = 53 - agno = 41 - agno = 86 - agno = 54 - agno = 68 - agno = 87 - agno = 42 - agno = 55 - agno = 88 - agno = 69 - agno = 43 - agno = 56 - agno = 70 - agno = 89 - agno = 57 - agno = 44 - agno = 71 - agno = 58 - agno = 72 - agno = 59 - agno = 73 - agno = 74 - agno = 1 - agno = 16 - agno = 2 - agno = 3 - agno = 17 - agno = 4 - agno = 18 - agno = 5 - agno = 19 - agno = 6 - agno = 20 - agno = 7 - agno = 21 - agno = 8 - agno = 22 - agno = 9 - agno = 23 - agno = 24 - agno = 10 - agno = 25 - agno = 11 - agno = 26 - agno = 12 - agno = 27 - agno = 13 - agno = 28 - agno = 29 - agno = 14 - 20:22:35: process known inodes and inode discovery - 2240 of 2240 inodes done - process newly discovered inodes... - 20:22:35: process newly discovered inodes - 96 of 96 allocation groups done Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - 20:22:35: setting up duplicate extent list - 96 of 96 allocation groups done - check for inodes claiming duplicate blocks... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - agno = 4 - agno = 5 - agno = 6 - agno = 7 - agno = 8 - agno = 9 - agno = 10 - agno = 11 - agno = 12 - agno = 13 - agno = 14 - agno = 15 - agno = 16 - agno = 17 - agno = 18 - agno = 19 - agno = 20 - agno = 21 - agno = 22 - agno = 23 - agno = 24 - agno = 25 - agno = 26 - agno = 27 - agno = 28 - agno = 29 - agno = 30 - agno = 31 - agno = 32 - agno = 33 - agno = 34 - agno = 35 - agno = 36 - agno = 38 - agno = 39 - agno = 37 - agno = 41 - agno = 40 - agno = 44 - agno = 45 - agno = 43 - agno = 46 - agno = 47 - agno = 42 - agno = 49 - agno = 51 - agno = 50 - agno = 48 - agno = 52 - agno = 53 - agno = 54 - agno = 56 - agno = 55 - agno = 58 - agno = 60 - agno = 61 - agno = 62 - agno = 63 - agno = 64 - agno = 65 - agno = 66 - agno = 67 - agno = 68 - agno = 69 - agno = 70 - agno = 71 - agno = 72 - agno = 73 - agno = 74 - agno = 75 - agno = 76 - agno = 77 - agno = 78 - agno = 79 - agno = 80 - agno = 81 - agno = 57 - agno = 59 - agno = 83 - agno = 85 - agno = 86 - agno = 87 - agno = 88 - agno = 89 - agno = 90 - agno = 91 - agno = 92 - agno = 93 - agno = 94 - agno = 95 - agno = 84 - agno = 82 - 20:22:35: check for inodes claiming duplicate blocks - 2240 of 2240 inodes done Phase 5 - rebuild AG headers and trees... - 20:22:35: rebuild AG headers and trees - 96 of 96 allocation groups done - reset superblock... Phase 6 - check inode connectivity... - resetting contents of realtime bitmap and summary inodes - traversing filesystem ... - traversal finished ... - moving disconnected inodes to lost+found ... Phase 7 - verify and correct link counts... - 20:22:35: verify and correct link counts - 96 of 96 allocation groups done done

Looks good, right? Check Filesystem Status xfs_repair status: Phase 1 - find and verify superblock... - reporting progress in intervals of 15 minutes - block cache size set to 674568 entries Phase 2 - using internal log - zero log... zero_log: head block 54944 tail block 54944 - 19:44:33: zeroing log - 476930 of 476930 blocks done - scan filesystem freespace and inode maps... - 19:44:34: scanning filesystem freespace - 96 of 96 allocation groups done - found root inode chunk Phase 3 - for each AG... - scan (but don't clear) agi unlinked lists... - 19:44:34: scanning agi unlinked lists - 96 of 96 allocation groups done - process known inodes and perform inode discovery... - agno = 45 - agno = 15 - agno = 46 - agno = 75 - agno = 90 - agno = 30 - agno = 60 - agno = 0 - agno = 91 - agno = 47 - agno = 76 - agno = 61 - agno = 31 - agno = 48 - agno = 92 - agno = 62 - agno = 77 - agno = 49 - agno = 32 - agno = 63 - agno = 93 - agno = 50 - agno = 78 - agno = 64 - agno = 33 - agno = 94 - agno = 51 - agno = 79 - agno = 34 - agno = 65 - agno = 95 - agno = 66 - agno = 52 - agno = 35 - agno = 80 - agno = 67 - agno = 53 - agno = 36 - agno = 81 - agno = 68 - agno = 54 - agno = 69 - agno = 37 - agno = 82 - agno = 55 - agno = 83 - agno = 70 - agno = 56 - agno = 38 - agno = 71 - agno = 57 - agno = 39 - agno = 84 - agno = 72 - agno = 58 - agno = 85 - agno = 40 - agno = 73 - agno = 59 - agno = 41 - agno = 74 - agno = 86 - agno = 42 - agno = 87 - agno = 43 - agno = 88 - agno = 44 - agno = 89 - agno = 16 - agno = 1 - agno = 2 - agno = 17 - agno = 3 - agno = 18 - agno = 4 - agno = 19 - agno = 5 - agno = 20 - agno = 21 - agno = 6 - agno = 7 - agno = 22 - agno = 8 - agno = 23 - agno = 9 - agno = 24 - agno = 25 - agno = 10 - agno = 26 - agno = 11 - agno = 12 - agno = 27 - agno = 13 - agno = 28 - agno = 14 - agno = 29 - 19:44:34: process known inodes and inode discovery - 2240 of 2240 inodes done - process newly discovered inodes... - 19:44:34: process newly discovered inodes - 96 of 96 allocation groups done Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - 19:44:34: setting up duplicate extent list - 96 of 96 allocation groups done - check for inodes claiming duplicate blocks... - agno = 0 - agno = 2 - agno = 1 - agno = 3 - agno = 4 - agno = 5 - agno = 6 - agno = 7 - agno = 8 - agno = 9 - agno = 10 - agno = 11 - agno = 12 - agno = 13 - agno = 14 - agno = 15 - agno = 16 - agno = 17 - agno = 18 - agno = 19 - agno = 20 - agno = 21 - agno = 22 - agno = 23 - agno = 24 - agno = 25 - agno = 26 - agno = 27 - agno = 28 - agno = 29 - agno = 30 - agno = 31 - agno = 32 - agno = 33 - agno = 34 - agno = 35 - agno = 36 - agno = 38 - agno = 39 - agno = 37 - agno = 41 - agno = 40 - agno = 43 - agno = 44 - agno = 45 - agno = 47 - agno = 48 - agno = 46 - agno = 49 - agno = 51 - agno = 52 - agno = 53 - agno = 42 - agno = 50 - agno = 56 - agno = 57 - agno = 58 - agno = 54 - agno = 55 - agno = 60 - agno = 62 - agno = 63 - agno = 61 - agno = 64 - agno = 65 - agno = 59 - agno = 68 - agno = 66 - agno = 70 - agno = 71 - agno = 72 - agno = 73 - agno = 74 - agno = 75 - agno = 76 - agno = 77 - agno = 78 - agno = 67 - agno = 69 - agno = 79 - agno = 82 - agno = 83 - agno = 84 - agno = 85 - agno = 86 - agno = 87 - agno = 88 - agno = 80 - agno = 81 - agno = 89 - agno = 92 - agno = 93 - agno = 94 - agno = 90 - agno = 91 - agno = 95 - 19:44:34: check for inodes claiming duplicate blocks - 2240 of 2240 inodes done No modify flag set, skipping phase 5 Phase 6 - check inode connectivity... - traversing filesystem ... - agno = 0 - agno = 60 - agno = 15 - agno = 45 - agno = 30 - agno = 61 - agno = 90 - agno = 75 - agno = 1 - agno = 62 - agno = 91 - agno = 16 - agno = 76 - agno = 31 - agno = 92 - agno = 77 - agno = 17 - agno = 46 - agno = 93 - agno = 32 - agno = 63 - agno = 18 - agno = 33 - agno = 78 - agno = 19 - agno = 20 - agno = 64 - agno = 94 - agno = 2 - agno = 95 - agno = 34 - agno = 79 - agno = 47 - agno = 65 - agno = 3 - agno = 21 - agno = 4 - agno = 80 - agno = 48 - agno = 66 - agno = 5 - agno = 22 - agno = 35 - agno = 36 - agno = 81 - agno = 49 - agno = 67 - agno = 6 - agno = 50 - agno = 68 - agno = 82 - agno = 51 - agno = 69 - agno = 37 - agno = 52 - agno = 70 - agno = 38 - agno = 23 - agno = 7 - agno = 24 - agno = 25 - agno = 53 - agno = 26 - agno = 83 - agno = 71 - agno = 39 - agno = 84 - agno = 54 - agno = 8 - agno = 27 - agno = 85 - agno = 9 - agno = 40 - agno = 86 - agno = 72 - agno = 87 - agno = 28 - agno = 88 - agno = 73 - agno = 29 - agno = 55 - agno = 41 - agno = 89 - agno = 10 - agno = 42 - agno = 56 - agno = 43 - agno = 74 - agno = 11 - agno = 57 - agno = 44 - agno = 12 - agno = 58 - agno = 13 - agno = 59 - agno = 14 - traversal finished ... - moving disconnected inodes to lost+found ... Phase 7 - verify link counts... - 19:44:34: verify and correct link counts - 96 of 96 allocation groups done No modify flag set, skipping filesystem flush and exiting. XFS_REPAIR Summary Tue Mar 22 19:44:34 2022 Phase Start End Duration Phase 1: 03/22 19:44:32 03/22 19:44:33 1 second Phase 2: 03/22 19:44:33 03/22 19:44:34 1 second Phase 3: 03/22 19:44:34 03/22 19:44:34 Phase 4: 03/22 19:44:34 03/22 19:44:34 Phase 5: Skipped Phase 6: 03/22 19:44:34 03/22 19:44:34 Phase 7: 03/22 19:44:34 03/22 19:44:34 Total run time: 2 seconds

Now it has network! But what does this disk 5 is doing? It shows green but is not mounted? I did format it and added it to array previously. And even moved files to it just couple of days ago. Now unRAID offers me to format it again... Diagnostics say: root: mount: /mnt/disk5: wrong fs type, bad option, bad superblock on /dev/md5, missing codepage or helper program, or other error. EDIT: After all that I updated to rc3 and now it says: tower-diagnostics-20220322-1627.zip

Thanks! But I cannot access WebGUI so I need to do this manually. Where can I download prerelease versions? EDIT: Or can I only download the version 6.9.2 and update to rc3 afterwards?

Thank you guys! I did delete the "network-rules.cfg" file from the flash, but did not help. Latest diagnostics attached. In the end of syslog it does say that it is using eth1 and not eth0. Is reverting to rc3 my only option? And if so, do I just overwrite all of the bz* files on the flash drive with the ones on rc3 file package? tower-diagnostics-20220322-1348.zip

Here's a newer diagnostics log. I connected the new drive again that showed xfs on the GUI but still the message "Not mounted or no file sysem". I only have one NIC on the motherboard so that should not be a problem? tower-diagnostics-20220321-2142.zip