mbc0 Posted June 13, 2017 Share Posted June 13, 2017 Hi, I upgraded my motherboard & CPU and as far as the unRAID side of things everything is great, the array has started, VM's Dockers etc everything is fine except the server can no longer be seen by any of the 5 machines on the network any more? Current elected master: WORKGROUP is current local master browser (Is this normal? should it say the name of my server instead? I have rebooted (all machines) added the extra lines [global] domain master = yes preferred master = yes os level = 255 but still nothing? I have attached my diagnostics file if someone could lend a hand please? Many Thanks unraidserver-diagnostics-20170613-0825.zip Link to comment
Frank1940 Posted June 13, 2017 Share Posted June 13, 2017 You might want to run this program from a Windows computer and see what local master is being detected by that computer: https://scottiestech.info/2009/02/14/how-to-determine-the-master-browser-in-a-windows-workgroup/ (All of the usual cautions about programs downloaded from the Internet should be observed. However, I have downloaded this program in the past and used without any issues...) Link to comment
mbc0 Posted June 13, 2017 Author Share Posted June 13, 2017 Many Thanks for this, I get this error at the moment (although it worked earlier and told me WORKGROUP was master LANscanner v1.68 - ScottiesTech.Info Scanning LAN... System error 53 has occurred. The network path was not found. Press any key to exit... If I perform Windows diagnostics when manually typing \\UNRAIDSERVER I get the information below... Note I am able to connect to all other machines & network devices without any issues, just the unRAID server is unreachable.. Windows Network Diagnostics Publisher details Issues found The remote device or resource won't accept the connection The remote device or resource won't accept the connection The device or resource (unraidserver) is not set up to accept connections on port "The File and printer sharing (SMB)". Detected Contact your network administrator Completed Issues found Detection details 6 The remote device or resource won't accept the connection Detected The device or resource (unraidserver) is not set up to accept connections on port "The File and printer sharing (SMB)". Contact your network administrator Completed The computer or device you are trying to reach is available, but it doesn’t support what you’re trying to do. This might be a configuration issue or a limitation of the device. Detection details Network Diagnostics Log File Name: 8F9BAF5C-BC80-42CD-AE92-4EC9003ECE28.Diagnose.0.etl Other Networking Configuration and Logs File Name: NetworkConfiguration.cab Collection information Computer Name: I7QUAD Windows Version: 10.0 Architecture: x64 Time: 13 June 2017 22:19:55 Publisher details Windows Network Diagnostics Detects problems with network connectivity. Package Version: 4.0 Publisher: Microsoft Windows Link to comment
mbc0 Posted June 14, 2017 Author Share Posted June 14, 2017 I get the same windows network diagnostics details from all windows machines telling me like above that it can see the unraidserver but cannot access it? anyone else got any ideas? Many Thanks Link to comment
Frank1940 Posted June 14, 2017 Share Posted June 14, 2017 I am no expert on reading and understanding syslogs but you have several error messages in your syslog but indicate some problems: Jun 13 01:10:58 UNRAIDSERVER kernel: Buffer I/O error on dev md14, logical block 244190608, async page read and Jun 13 01:10:58 UNRAIDSERVER emhttp: shcmd (322): mkdir -p /mnt/disk13 Jun 13 01:10:58 UNRAIDSERVER emhttp: shcmd (323): set -o pipefail ; mount -t btrfs,xfs,reiserfs -o noatime,nodiratime /dev/md13 /mnt/disk13 |& logger Jun 13 01:10:58 UNRAIDSERVER root: mount: wrong fs type, bad option, bad superblock on /dev/md13, Jun 13 01:10:58 UNRAIDSERVER root: missing codepage or helper program, or other error Jun 13 01:10:58 UNRAIDSERVER root: Jun 13 01:10:58 UNRAIDSERVER root: In some cases useful info is found in syslog - try Jun 13 01:10:58 UNRAIDSERVER root: dmesg | tail or so. Jun 13 01:10:58 UNRAIDSERVER emhttp: err: shcmd: shcmd (323): exit status: 32 Jun 13 01:10:58 UNRAIDSERVER emhttp: mount error: No file system (32) Jun 13 01:10:58 UNRAIDSERVER emhttp: shcmd (324): umount /mnt/disk13 |& logger Jun 13 01:10:58 UNRAIDSERVER root: umount: /mnt/disk13: not mounted Jun 13 01:10:58 UNRAIDSERVER emhttp: shcmd (325): rmdir /mnt/disk13 Jun 13 01:10:58 UNRAIDSERVER emhttp: shcmd (326): mkdir -p /mnt/cache Jun 13 01:10:58 UNRAIDSERVER kernel: Buffer I/O error on dev md14, logical block 244190608, async page read Jun 13 01:10:58 UNRAIDSERVER emhttp: shcmd (327): set -o pipefail ; mount -t btrfs -o noatime,nodiratime /dev/sdb1 /mnt/cache |& logger I seem to recall that md14 would be disk 14 and md13 would be disk 13. Since you have recently replaced your MB, I would open up the server and check to see that all cards are firmly seated and that all of the SATA (Both data and power) connectors are securely seated. You also have an error that indicates that there is a problem with the time setting not being synchronized. (I don't think this is a major issue but I seem to recall that it can cause problems with licensing in certain cases...) For your information, you can find all of the errors in your syslog by searching for err in the log file. Link to comment
JorgeB Posted June 14, 2017 Share Posted June 14, 2017 Did you try using the IP? \\192.168.0.33 Link to comment
mbc0 Posted June 14, 2017 Author Share Posted June 14, 2017 Hi, I resolved the Disk 13&14 errors (two of the drives are attached to the front of the case (Fractal Design Node 804) and the power splitter was not seated correctly but the network error was there before and after the disk errors. http://192.168.0.33/media gives me a 404 not found but 192.168.0.33 obviously takes me to the dashboard. Thanks so much for your help so far! I hope someone can work this out, I am still going round in circles! Link to comment
JorgeB Posted June 14, 2017 Share Posted June 14, 2017 On your desktop type on the windows explorer (not the browser) address bar: \\192.168.0.33 not //192.168.0.33 You should see all your shares Link to comment
Frank1940 Posted June 14, 2017 Share Posted June 14, 2017 Forward slashes / are used in a browser like Firefox or Chrome. Do you have access to your GUI with http://192.168.0.33 using your browser? Link to comment
mbc0 Posted June 14, 2017 Author Share Posted June 14, 2017 Hi, yes http://192.168.0.33 takes me to my unraid desktop Link to comment
mbc0 Posted June 14, 2017 Author Share Posted June 14, 2017 chrome/edge automatically changes http://192.168.0.33\media to http://192.168.0.33/media as well, thought it was worth a try! Link to comment
JorgeB Posted June 14, 2017 Share Posted June 14, 2017 You can access the WebGUI but can't access SMB shares, so it's not a physical network problem, most likely a SMB issue, try from a different computer if you can. Link to comment
mbc0 Posted June 14, 2017 Author Share Posted June 14, 2017 Hi it's the same problem no matter which computer or device I use... Link to comment
Frank1940 Posted June 14, 2017 Share Posted June 14, 2017 You must be running Win10 if you are using Edge. There was a raft of SMB/Win10 issues as Win 10 went through its introduction but things seem to have settled down in the past few months. I suspect a Local Master issue. I would suggest shutting down EVERY computer/device on the network that can possibly use SMB for ten minutes. Make sure that your unRAID is the Local Master for your Workgroup. Then restart each computer/device slowly with a couple of minutes between each restart. Link to comment
mbc0 Posted June 14, 2017 Author Share Posted June 14, 2017 Thanks for the advice, I have already tried that several times and even left overnight. I have Android/Linux/windows 10/7 all cannot connect to my server. I can confirm that my server is the master since yesterday.. this is really annoying! Link to comment
Frank1940 Posted June 14, 2017 Share Posted June 14, 2017 There is one resource that you should be aware of: and one other post: Did you do any other upgrades besides MB and RAM when changed out the MB? Link to comment
mbc0 Posted June 14, 2017 Author Share Posted June 14, 2017 The motherboard upgrade resulted in going from Intel to AMD so a completely different chipset, NIC & controllers (now all SATA 6) the RAM is the only part that is the same! Link to comment
mbc0 Posted June 14, 2017 Author Share Posted June 14, 2017 here is a copy of my network.cfg file just in case anyone can see anything awry? root@UNRAIDSERVER:/boot/config# vi network.cfg reading network.cfg # Generated settings: IFNAME[0]="br0" BONDNAME[0]="bond0" BONDING_MIIMON[0]="100" BRNAME[0]="br0" BRSTP[0]="no" BRFD[0]="0" BONDING_MODE[0]="1" BONDNICS[0]="eth0" BRNICS[0]="bond0" DESCRIPTION[0]="" USE_DHCP[0]="yes" DHCP_KEEPRESOLV="no" MTU[0]="" SYSNICS="1" ~ ~ ~ ~ ~ ~ ~ ~ Read network.cfg, 15 lines, 260 chars Link to comment
mbc0 Posted June 14, 2017 Author Share Posted June 14, 2017 I have not changed anything here but does this all look ok? Link to comment
mbc0 Posted June 15, 2017 Author Share Posted June 15, 2017 bump! Wondering if I have to start everything again from scratch! :-( 21TB OF Data I cannot access Link to comment
Frank1940 Posted June 15, 2017 Share Posted June 15, 2017 Let's go back to the beginning. First, post up another diagnostics file. Second, Look at the SMB settings on both the server and the client computers. Make sure that the workgroup name is IDENTICAL everywhere including capitalization. I perter to use all Cap's in computer and Workgroup names as that is how Windows has traditionally seen them. (Linux/UNIX, however, honors capitalization. Thus, Sam and sam are two different names to Linux/UNIX and one name to Windows. I have never figured out how SMB/Samba resolves this issue.) (Think about this problem. You can create Sam.txt and sam.txt files in the Linux environment and everything is fine there but your Windows client can only see one of them!) Third, run that lanscan program again on one of your clients. I just download it again on my win7 client (I can't verify that it works with Win10) and I actually run it by double-clicking on the executable inside of the zip container. That will give you a picture of what the clients are seeing. I have attached a screen capture of the output that I see... Link to comment
mbc0 Posted June 15, 2017 Author Share Posted June 15, 2017 Hi, Thanks for your time... everything you have asked is below but please remember I have 6 Windows machines on the network plus 3 Linux machines 6 Android devices, FREENAS, Printers, TV's etc and nothing has changed except upgrading the motherboard/CPU on the unRAID server. All the problems I have being unable to connect to the unRAID server are the same for each device whereas I have always been able to connect to the unRAID server from all of these devices all day long before the replacement of the motherboard/CPU. 1, Diagnostics file attached 2, Image attached for WORKGROUP settings on one of my Windows machines and the unRAID SMB Settings are on the previous post. 3, Lanscan gives the error shown below (it did work a few days ago) it does this same error on all Windows machines but my network is working perfectly for all other devices/machines. I hope you can see something/anything to prevent a complete rebuild :-( unraidserver-diagnostics-20170615-1619.zip Link to comment
Frank1940 Posted June 15, 2017 Share Posted June 15, 2017 Can you see any other computers from the clients? (Open up Windows Explorer and click on the Network icon.) You should be able to see every Computer that is running SMB/samba when you do this. See screen capture below: Link to comment
mbc0 Posted June 15, 2017 Author Share Posted June 15, 2017 Hi Frank, My network is working perfectly, each machine can access each other, all my devices are accessible through WORKGROUP as was my unraid server until I changed the Motherboard/CPU you can even see the plex server on the unraidserver, The biggest clue I think is what I posted on post #3 but I cannot find a way to investigate it "The computer or device you are trying to reach is available, but it doesn’t support what you’re trying to do. This might be a configuration issue or a limitation of the device." Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.