CaptainSpalding Posted March 20, 2022 Share Posted March 20, 2022 Yes, "no file sysem". Maybe this misspelling should also be addressed. My problem: I replaced a drive to my unRAID. Did parity check, formatted the drive and even moved files to it. Everything was working. Then I did shut down, added a usb drive - from witch I would have moved files from - powered on and this new drive said "Unmountabe: Not mounted or no file system". At the same time there was bulleting for a new version of unRAID (-rc4). I updated, booted and all of a sudden the server does not find it's way to network (??). I did ping google.com, but was a no go. I changed the network cable, but did not work eighter. It does boot and shows the same ip as before for unRAID (in the console) , but it does not have network connection. What should I do? Quote Link to comment
CaptainSpalding Posted March 20, 2022 Author Share Posted March 20, 2022 It seems that when unRAID starts to boot my router still shows the ethernet light, but when the display resolution changes to hd it cuts of. So something is happening during the unRAID boot that prevents the connection to network. Quote Link to comment
CaptainSpalding Posted March 21, 2022 Author Share Posted March 21, 2022 Any idea why ethernet shuts down on unraid boot? Exactly when the boot is finished. Quote Link to comment
ChatNoir Posted March 21, 2022 Share Posted March 21, 2022 Do you have several NICs on the system ? If so, is it using the one you want ? Your Diagnostics might show something. Quote Link to comment
CaptainSpalding Posted March 21, 2022 Author Share Posted March 21, 2022 I am unable to connect to WebGUI. How can I get these diagnostics from console? Quote Link to comment
itimpi Posted March 21, 2022 Share Posted March 21, 2022 8 minutes ago, CaptainSpalding said: How can I get these diagnostics from console? Use the ‘diagnostics’ command which writes them to the logs folder on the flash drive. 1 Quote Link to comment
CaptainSpalding Posted March 21, 2022 Author Share Posted March 21, 2022 Here's the file. tower-diagnostics-20220321-1819.zip Quote Link to comment
CaptainSpalding Posted March 21, 2022 Author Share Posted March 21, 2022 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 Quote Link to comment
ChatNoir Posted March 21, 2022 Share Posted March 21, 2022 Regarding the Ethernet issue, I see this happening in the log over and over again : Mar 21 21:43:14 Tower kernel: ixgbe 0000:06:00.1 eth1: The link is down Mar 21 21:43:14 Tower kernel: ixgbe 0000:06:00.1 eth1: NIC Link is Up 1 Gbps, Flow Control: RX/TX Mar 21 21:43:14 Tower kernel: bond0: (slave eth1): link status definitely up, 1000 Mbps full duplex Mar 21 21:43:14 Tower kernel: bond0: (slave eth1): making interface the new active one Mar 21 21:43:14 Tower kernel: device eth1 entered promiscuous mode Mar 21 21:43:14 Tower kernel: bond0: active interface up! Mar 21 21:43:14 Tower kernel: br0: port 1(bond0) entered blocking state Mar 21 21:43:14 Tower kernel: br0: port 1(bond0) entered forwarding state Mar 21 21:43:14 Tower kernel: ixgbe 0000:06:00.1 eth1: NIC Link is Down Mar 21 21:43:14 Tower kernel: bond0: (slave eth1): link status definitely down, disabling slave Mar 21 21:43:14 Tower kernel: device eth1 left promiscuous mode Mar 21 21:43:14 Tower kernel: bond0: now running without any active interface! Mar 21 21:43:14 Tower kernel: br0: port 1(bond0) entered disabled state Mar 21 21:43:17 Tower kernel: ixgbe 0000:06:00.1 eth1: The link is down Can't make much from it myself, but this looks related, hopefully someone can ? 1 Quote Link to comment
SimonF Posted March 21, 2022 Share Posted March 21, 2022 3 hours ago, CaptainSpalding said: 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 99.68 kB · 2 downloads Suspect out of tree driver has an issue on your system. If you revert to rc3 does it work? rc4 added oot: added Intel ixgbe: version 5.14.6 1 Quote Link to comment
bonienl Posted March 21, 2022 Share Posted March 21, 2022 When you have a single interface, it should be eth0 and not eth1. Delete the file “network-rules.cfg” on your flash device and reboot. 1 Quote Link to comment
CaptainSpalding Posted March 22, 2022 Author Share Posted March 22, 2022 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 Quote Link to comment
SimonF Posted March 22, 2022 Share Posted March 22, 2022 Yes copy the bz files from RC3 zip. If you upgraded from RC3 you should have an option to revert to prev, but it will show 6.9.2 if you upgraded from that or nothing if a new install. Quote Link to comment
CaptainSpalding Posted March 22, 2022 Author Share Posted March 22, 2022 (edited) 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? Edited March 22, 2022 by CaptainSpalding Quote Link to comment
Solution SimonF Posted March 22, 2022 Solution Share Posted March 22, 2022 https://unraid-dl.sfo2.cdn.digitaloceanspaces.com/next/unRAIDServer-6.10.0-rc2-x86_64.zip You can go back to 6.9.2 and then copy bz files to flash and then reboot. or put flash in another machine and copy files. 1 Quote Link to comment
CaptainSpalding Posted March 22, 2022 Author Share Posted March 22, 2022 (edited) 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 Edited March 22, 2022 by CaptainSpalding Quote Link to comment
JorgeB Posted March 22, 2022 Share Posted March 22, 2022 Check filesystem on disk5. 1 Quote Link to comment
CaptainSpalding Posted March 22, 2022 Author Share Posted March 22, 2022 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 Quote Link to comment
JorgeB Posted March 22, 2022 Share Posted March 22, 2022 Run it again without -n or nothing will be done. Quote Link to comment
CaptainSpalding Posted March 22, 2022 Author Share Posted March 22, 2022 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 Quote Link to comment
JorgeB Posted March 22, 2022 Share Posted March 22, 2022 Should be fixed now, just start the array normally. Quote Link to comment
CaptainSpalding Posted March 22, 2022 Author Share Posted March 22, 2022 Now it wants to rebuild parity. Is that what I should do? Quote Link to comment
itimpi Posted March 22, 2022 Share Posted March 22, 2022 4 minutes ago, CaptainSpalding said: Now it wants to rebuild parity. Is that what I should do? Tht does not sound right, but maybe posting a screenshot and new diagnostics might allow us to see why. Quote Link to comment
CaptainSpalding Posted March 22, 2022 Author Share Posted March 22, 2022 Here you are. tower-diagnostics-20220322-2050.zip Quote Link to comment
JorgeB Posted March 22, 2022 Share Posted March 22, 2022 Disk5 as unassigned, array was started, then assigned again, so now Unraid wants to rebuild it, why did you do that? Quote Link to comment
Recommended Posts
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.