Jump to content

smdl

Members
  • Content Count

    14
  • Joined

  • Last visited

Community Reputation

0 Neutral

About smdl

  • Rank
    Member
  1. 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
  2. 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
  3. 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
  4. 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
  5. 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
  6. 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
  7. 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
  8. 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
  9. 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
  10. 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|-]:
  11. Hi. folks. I've been evaluating unRAID for a few months (I like it!) on a very old machine, and am just in the process of setting up an all-new server. I completed the setup and pre-clear last night, and just brought the array online today. One of my first steps was to add the CA Fix Common Problems app, and that reported a single hardware error when I ran it. However, I saw some notes in the forum indicating that doing a simple re-scan to see if the problem persisted would be a normal approach. When I did that, the problem was no longer indicated, so I carried on configuring the system. At things sit currenetly, everything unRAID seems happy, with everything in the green. However, while checking status, I happened to notice hardware errors showing up in the log. All say that the errors where corrected, and no action is required, but they persist. I have attached the Diagnostics file to this post, and would really appreciate any help with figuring out what isn't right. I'm still a novice with unRAID, so apologies if I am missing something obvious. Just in case the Diagnostic file doesn't include the hardware errors, I have included a sample below: Thanks, Shaun Oct 14 14:39:33 GISL-CR1-uR1 kernel: [Hardware Error]: CPU:14 (17:8:2) MC1_STATUS[Over|CE|MiscV|-|AddrV|-|-|SyndV|-]: 0xdc20000000020151 Oct 14 14:39:33 GISL-CR1-uR1 kernel: [Hardware Error]: Error Addr: 0x000000000107a9c0 Oct 14 14:39:33 GISL-CR1-uR1 kernel: [Hardware Error]: IPID: 0x000100b000000000, Syndrome: 0x000000002a010002 Oct 14 14:39:33 GISL-CR1-uR1 kernel: [Hardware Error]: Instruction Fetch Unit Extended Error Code: 2 Oct 14 14:39:33 GISL-CR1-uR1 kernel: [Hardware Error]: Instruction Fetch Unit Error: IC full tag parity. Oct 14 14:39:33 GISL-CR1-uR1 kernel: [Hardware Error]: cache level: L1, tx: INSN, mem-tx: IRD Oct 14 14:45:01 GISL-CR1-uR1 kernel: mce: [Hardware Error]: Machine check events logged Oct 14 14:45:01 GISL-CR1-uR1 kernel: [Hardware Error]: Corrected error, no action required. Oct 14 14:45:01 GISL-CR1-uR1 kernel: [Hardware Error]: CPU:6 (17:8:2) MC1_STATUS[Over|CE|MiscV|-|AddrV|-|-|SyndV|-]: 0xdc20000000020151 Oct 14 14:45:01 GISL-CR1-uR1 kernel: [Hardware Error]: Error Addr: 0x000000000106ce40 Oct 14 14:45:01 GISL-CR1-uR1 kernel: [Hardware Error]: IPID: 0x000100b000000000, Syndrome: 0x000000002a010002 Oct 14 14:45:01 GISL-CR1-uR1 kernel: [Hardware Error]: Instruction Fetch Unit Extended Error Code: 2 Oct 14 14:45:01 GISL-CR1-uR1 kernel: [Hardware Error]: Instruction Fetch Unit Error: IC full tag parity. Oct 14 14:45:01 GISL-CR1-uR1 kernel: [Hardware Error]: cache level: L1, tx: INSN, mem-tx: IRD Oct 14 14:45:01 GISL-CR1-uR1 kernel: mce: [Hardware Error]: Machine check events logged Oct 14 14:45:01 GISL-CR1-uR1 kernel: [Hardware Error]: Corrected error, no action required. Oct 14 14:45:01 GISL-CR1-uR1 kernel: [Hardware Error]: CPU:14 (17:8:2) MC1_STATUS[Over|CE|MiscV|-|AddrV|-|-|SyndV|-]: 0xdc20000000020151 Oct 14 14:45:01 GISL-CR1-uR1 kernel: [Hardware Error]: Error Addr: 0x000000000109e1c0 Oct 14 14:45:01 GISL-CR1-uR1 kernel: [Hardware Error]: IPID: 0x000100b000000000, Syndrome: 0x000000002a010002 Oct 14 14:45:01 GISL-CR1-uR1 kernel: [Hardware Error]: Instruction Fetch Unit Extended Error Code: 2 Oct 14 14:45:01 GISL-CR1-uR1 kernel: [Hardware Error]: Instruction Fetch Unit Error: IC full tag parity. Oct 14 14:45:01 GISL-CR1-uR1 kernel: [Hardware Error]: cache level: L1, tx: INSN, mem-tx: IRD Oct 14 14:50:28 GISL-CR1-uR1 kernel: mce: [Hardware Error]: Machine check events logged Oct 14 14:50:28 GISL-CR1-uR1 kernel: [Hardware Error]: Corrected error, no action required. Oct 14 14:50:28 GISL-CR1-uR1 kernel: [Hardware Error]: CPU:6 (17:8:2) MC1_STATUS[Over|CE|MiscV|-|AddrV|-|-|SyndV|-]: gisl-cr1-ur1-diagnostics-20191014-2201.zip
  12. Sincere thanks for the additional information. At the very least, this really helps me to better understand how things work. Cheers, Shaun
  13. Thanks for the reply, CHBMB. Yes, indeed, others on the SageTV forums are experiencing the same issue, but no one really seems to know what's happening with FireWire under the hood. Stuckless, the gentleman that put together the docker image for SageTV, doesn't use FireWire at all, so has no insight. He only activated FireWire in the image at the request of Wayner, the user who first successfully implemented FireWire in Sage/Unraid. However, Wayner, who then wrote the How-To thread on SageTV Unraid FireWire, uses SA boxes, and these work just fine as built. No help there yet, but I will keep seeking answers in that community. It's probably worth mentioning again that this issue apparently isn't a SageTV thing, as Sage is just leveraging FireWire functionality in LibreELEC or DVB (not sure which). Whoever put those together likely knows how to configure FireWire more directly, and I was hoping to follow the trail of breadcrumbs back to find the right folks. It's probably not very difficult, but I'm new to this world, and still trying to find my way. I'll keep looking, and I'm sure I'll get there eventually. In my continuing research, I can see that MythTV can accommodate the Motorola STBs, and there is even a standalone program called 6200ch intended to test tuning on them. So, the Linux world has clearly dealt with this, and I just need to get to the right folks who can educate my uneducated brain on the subject. Anyway, thanks for being patient with my questions. I won't darken your doorstep any longer with this issue. 😉 Cheers, Shaun
  14. Greetings, and thanks for putting together this great plugin! I'm new to Unraid, and am in the process of implementing SageTV in Docker. I'm on 6.6.6, and have the plugin installed. Based upon searches, I can see that firewire support was added in 6.3.1, and everything is working great -- with one minor exception. Firewire tuning is fully configured and communicating nicely, but there seems to be a minor issue with the Motorola DCX3200 STBs I'm using. Those with SA STBs find no issue at all, but with the Motorolla/Arris units, the channel changing command sent is not quite right, and this always results in the guide being displayed after the channel is successfully changed. Naturally, this completely obscures the recording, rendering it useless. My question: Apologies for bringing this up here, as I realize that my question might not relate to the plugin itself, but I'm hoping that someone might be able to direct me to the best place to dig deeper. In the Windows world, there are variables that can be adjusted to accommodate different models of STB, and I have successfully done this in the past. What I'm hoping to find out is if there are similar capabilities in this environment, and I'm not sure where to start as I am new to Linux/Unraid/LibreELEC/DVB. Any info, advice or redirection would be very much appreciated, as extensive searching has not yet produced results. Thanks, Shaun