Jump to content

smdl

Members
  • Content Count

    19
  • Joined

  • Last visited

Community Reputation

1 Neutral

About smdl

  • Rank
    Member
  1. A bit more information: I am aware of the issue where if you connect first to a public share, that a persistent connection will be created, and that Windows will not allow the user to connect again with different credentials. However, that does not appear to be what is happening, in this case. I have confirmed through smbstatus that the only machine currently connected is the Win 10 machine that I am able to connect successfully from. To be doubly sure, I also tried the recommended command on the Win 7 machine (net use * /delete) to determine if it believes that any connections exist. This also confirms that there are no connections to the unRAID server from that machine. On the unsuccessful machine, I am able to reach the unRAID server via Network, by navigating to either the machine or the IP, and I can see a list of all the shares that are visible. However, when I try to connect, no matter how I try, I keep getting an indication that the credentials are invalid. In the past, I had no trouble at all connecting to the unRAID server from this machine. As an aside, I have had also had no issue setting this Win 7 machine up in unRAID as a remote SMB share, and can happily see everything going that direction. The reason that I am attempting to connect at this time is that I have been using Robocopy on Windows to sync data from the Win 7 machine to a share on unRAID, with the goal of then being able to update the Win 7 machine to Win 10 (want to get all the data off before I go through the upgrade). I have been able to connect several times recently and run the Robocopy sync, and today was to be the final update before taking down the machine for upgrade. So, I'm a bit miffed that I am now not able to connect! 😐 I'm sure that this is something silly that I'm doing wrong, and welcome any input that folks might have. Thanks, Shaun
  2. Hi, folks. I'm fairly new to unRAID, but have been using it without issue for some time, with connections from multiple machines and users without issue. However, when I am trying to connect from one particular Windows machine today, the response I get is that the credentials are invalid. However, when I connect using the same credentials from another Windows machine, I am able to connect just fine. Not sure why I am having this difficulty when it has worked fine from this machine in the past, but any suggestions of where to look would appreciated. I'm continuing to dig to see what I can find. Thanks, Shaun
  3. Remember when I warned about dumb questions? 😉 Yes, that's exactly what I did, and you described the issue/resolution perfectly. Thanks for that! All working perfectly again Cheers, Shaun
  4. Hi, folks. I have been running unRAID with this plugin for my SageTV docker application for some time, and it has been working well, most recently on 6.7.2. Last night, I decided to upgrade to unRAID 6.8.2, and then updated plugins, after which my two HD-PVRs are no longer visible in SageTV. I wonder if this is a similar problem to that described by Fas77 on January 26? Am I able to roll back the plugin version, leaving unRAID at 6.8.2, or should I downgrade that, too? Still fairly new to this, so apologies in advance for dumb questions! Any thoughts about what else to check would be very much appreciated. Cheers, Shaun
  5. Sorry, didn't see this message before. Yes, you are correct -- I had to copy the templates from the backup that I had on the array. Also, I was fortunate to not have much on the array, so went back through the settings, and all the shares are now working fine. Thanks again for your help! Shaun
  6. Yes, I did copy all contents, but that didn't seem to address the issue of stale config. Regardless, I seem to have gotten it back working now. Thanks for the taking the time to reply -- it's appreciated. Cheers, Shaun
  7. Okay, being that I had the disk assignments document, I started with a fresh 6.8.1 flash drive, brought the system up and did a minimal config on it (static IP, root password, community apps, etc.). Then I assigned the drives in the same manner they were before, indicated that parity was already valid, and started the array. I was pleased to see that I can access all my data, my shares are present, and that my docker containers are up and functioning (which is what is most important to me). What I seem to have lost are the users, and I notice that all the shares are now public, but those things are easy to fix. Is it really this easy? Can I just go back through the settings and get things exactly the way I want them, or are there issued lurking that I am not yet aware of? Is there something else that I need to do, like indicating that this is a new config? Cheers, Shaun
  8. Hi, folks. Hoping someone can help me through my first failed USB flash drive. I'm fairly new to unRAID, but knew to make sure I had a backup, and had hoped that recovery would be as simple as copying the config folder over to a new installation. Unfortunately, I'm struggling to get back up and working, and would really appreciate some shared wisdom. Here is how I got where I am: I decided to try upgrading from 6.7.2 to 6.8.1 today, and it initially seemed to work well. However, there were a some operations (working on setting up new shares) that didn't want to save, so I decided to reboot. When I did, the system would not restart, and when I tried to copy the files off of the flash drive to my PC, corruption was evident (would not copy, etc.). So, knowing that I had a backup of the flash drive on the array, I created a new, blank config on the flash drive using the the USB Creator. This allowed me to get the system up and working (without assigning drives or starting the array), after which I was able to copy the previous backup onto a separate folder on the flash drive, and then save it to my PC. I then copied the config folder from the backup onto the flash drive, overwriting where appropriate. Having done this, the system did boot up properly, but it still doesn't seem to have the correct configuration as no drives are assigned, and there is a message at the bottom of the screen indicating "Array Stopped - Stale Configuration". I have tried recreating the USB drive with 6.8.1 and 6.7.2, but the result is the same. Hopefully, I am making a simple mistake. Any help would be very much appreciated! Cheers, Shaun
  9. Hi, folks. Just to close the loop on this, after extensive testing and parts-swapping, I was able to confirm that the problem was with the processor. I have since replaced the processor with a new one (same model), and the errors have stopped. Sincere thanks to those who offered input. Cheers, Shaun
  10. As mentioned, this system seems to operate fine from an unRAID perspective, but I will add that the array seems to take much longer to start than my old machine, which seems odd. Old machine is AMD Phenom 9500 Quad Core 2200mhz with 4GB DDR2, and 5 SATA drives (largest 2TB). New one is Ryzen 7 2700X 3700Mhz with 32GB DDR4, and 4 SATA drives (largest 4TB). Seems odd to me that the new array would take about twice as long to start, and I wonder if this is an indication of a performance problem related to the errors. Are there other factors that might contribute to slower startup? Thanks, Shaun
  11. Greetings, all. Well, the system continues to operate without apparent issue, although it's not really in heavy use, yet. Until I have a sense of what might be causing this, I'm hesitant to depend upon it. I've looked up the errors online, but all I really see are posts relating to Linux kernel and AMD error reporting conventions, which really go over my head. I'll keep trying to understand it, but these seem to be more about how errors are reported, rather than what their potential meaning might be. Hoping someone out there might have additional ideas as to where to look. Any help would be sincerely appreciated. Cheers, Shaun
  12. Uh oh. Spoke too soon. Again, uR seems to be working great, but these errors continue to appear in the background. I saw an note in CA Fix Common Problems: You should install mcelog via the NerdPack plugin, post your diagnostics and ask for assistance on the unRaid forums. The output of mcelog (if installed) has been logged I'm not sure I should be playing in NerdPack too much yet, and am not sure I actually have it installed. I did find NerdPack GUI, and have that installed, but can't really figure out how to do much in there, yet. Will keep searching as it would be nice to have the errors decoded. Here is another sample of the errors. Oct 15 20:20:01 Tower kernel: mce: [Hardware Error]: Machine check events logged Oct 15 20:20:01 Tower kernel: [Hardware Error]: Corrected error, no action required. Oct 15 20:20:01 Tower kernel: [Hardware Error]: CPU:14 (17:8:2) MC1_STATUS[Over|CE|MiscV|-|AddrV|-|-|SyndV|-]: 0xdc20000000020151 Oct 15 20:20:01 Tower kernel: [Hardware Error]: Error Addr: 0x0000000001073ac0 Oct 15 20:20:01 Tower kernel: [Hardware Error]: IPID: 0x000100b000000000, Syndrome: 0x000000002a010002 Oct 15 20:20:01 Tower kernel: [Hardware Error]: Instruction Fetch Unit Extended Error Code: 2 Oct 15 20:20:01 Tower kernel: [Hardware Error]: Instruction Fetch Unit Error: IC full tag parity. Oct 15 20:20:01 Tower kernel: [Hardware Error]: cache level: L1, tx: INSN, mem-tx: IRD Oct 15 20:20:01 Tower kernel: mce: [Hardware Error]: Machine check events logged Oct 15 20:20:01 Tower kernel: [Hardware Error]: Corrected error, no action required. Oct 15 20:20:01 Tower kernel: [Hardware Error]: CPU:6 (17:8:2) MC1_STATUS[Over|CE|MiscV|-|AddrV|-|-|SyndV|-]: 0xdc20000000020151 Oct 15 20:20:01 Tower kernel: [Hardware Error]: Error Addr: 0x0000000001071bc0 Oct 15 20:20:01 Tower kernel: [Hardware Error]: IPID: 0x000100b000000000, Syndrome: 0x000000002a010002 Oct 15 20:20:01 Tower kernel: [Hardware Error]: Instruction Fetch Unit Extended Error Code: 2 Oct 15 20:20:01 Tower kernel: [Hardware Error]: Instruction Fetch Unit Error: IC full tag parity. Oct 15 20:20:01 Tower kernel: [Hardware Error]: cache level: L1, tx: INSN, mem-tx: IRD Cheers, Shaun
  13. Okay, I was finally able to get the system back up and working again, but I had to recreate the USB boot drive to do it. Also good news, the errors don't seem to be recurring... yet. Will need to keep watching this for a while to see if it comes back in time. Thanks again for the help with this! Cheers, Shaun
  14. Thanks, folks -- I really appreciate the help. I actually did update the BIOS, right after I posted my last message, as there was a newer version available. The update was successful, which is great, but now the system won't boot. It consistently gives the following message: SYSLINUX 6.03 EDD Load error - Boot error I was just starting to look at that when I had to take my son to an event, so I am just getting back to it now. Seems it might have something to do with the USB flash drive, but it seems suspicious that the problem started immediately after I updated the BIOS. I'll see what I can dig up. Any suggestions or advice would be gratefully accepted Cheers, Shaun
  15. Hmm, just checked, and this error still seems to be occurring about every 5-6 minutes. Hoping someone has some idea of how to look further into these. I'll keep searching, as well. Thanks, Shaun 0xdc20000000020151 Oct 15 14:19:30 GISL-CR1-uR1 kernel: [Hardware Error]: Error Addr: 0x00000000011541c0 Oct 15 14:19:30 GISL-CR1-uR1 kernel: [Hardware Error]: IPID: 0x000100b000000000, Syndrome: 0x000000002a010002 Oct 15 14:19:30 GISL-CR1-uR1 kernel: [Hardware Error]: Instruction Fetch Unit Extended Error Code: 2 Oct 15 14:19:30 GISL-CR1-uR1 kernel: [Hardware Error]: Instruction Fetch Unit Error: IC full tag parity. Oct 15 14:19:30 GISL-CR1-uR1 kernel: [Hardware Error]: cache level: L1, tx: INSN, mem-tx: IRD Oct 15 14:19:30 GISL-CR1-uR1 kernel: mce: [Hardware Error]: Machine check events logged Oct 15 14:19:30 GISL-CR1-uR1 kernel: [Hardware Error]: Corrected error, no action required. Oct 15 14:19:30 GISL-CR1-uR1 kernel: [Hardware Error]: CPU:6 (17:8:2) MC1_STATUS[Over|CE|MiscV|-|AddrV|-|-|SyndV|-]: