September 29, 20178 yr From the looks of the above you are running out of memory and unraid is being forced to terminate processes Normally it would terminate anything high usage, when I had the issue it would shut off vm's without warning to regain memory Perhaps monitor your system for a while using htop in command line and see what is checking up your memory? Failing that, the cAdviser docker does a good job of allowing you to look into this more Jamie
September 29, 20178 yr I think unRAID should rely on cgroups to avoid non essential process from affecting the core process.
September 29, 20178 yr On 26/09/2017 at 4:13 PM, jonp said: If running an RC release and you get a full system lockup where the logs are unavailable to be obtained afterwards, you'll need to hook up a monitor and keyboard to the system directly, login to the console, and type the following command: tail /var/log/syslog -f This will start printing out log messages to the screen locally which may reveal a kernel panic right before the hang up. Take a photo of those messages after the system reaches this hung state and post a new topic highlighting the system crash. Without this, we cannot research the issue further at all. I've manually redacted some information from this, so it's not just moving `/mnt/cache` and it sent an email, etc. etc. But the last line looks interesting to me... Not sure what it means But hopefully that helps! Rebooting now.
September 29, 20178 yr 3 hours ago, nexusmaniac said: I've manually redacted some information from this, so it's not just moving `/mnt/cache` and it sent an email, etc. etc. But the last line looks interesting to me... Not sure what it means But hopefully that helps! Rebooting now. Thanks for capturing this! I've forwarded it to Tom for review.
September 29, 20178 yr 15 minutes ago, jonp said: Thanks for capturing this! I've forwarded it to Tom for review. Cheers Jon! Fingers crossed it's useful for him haha
September 30, 20178 yr Not sure if it's 6.4.0 rc9f related or not. Went to login to the webgui today and I get a 401 Authorization required.. No password prompt. Whether I use the IP or Tower. http or https. Is there any way I can easily remove the password requirement (i can telnet in) or restart the webgui without needing to restart the serve ? Ignore that. Seems to be related to my browser. Edited September 30, 20178 yr by dalben
September 30, 20178 yr May well be nothing, but can someone assist with the below? Quote [113210.099933] swap_dup: Bad swap file entry 00010000 [113210.110899] swap_info_get: Bad swap file entry 00010000 [113210.110900] BUG: Bad page map in process python2 pte:40000000 pmd:38ec0c067 [113210.110969] addr:00002b3d63d01000 vm_flags:00100073 anon_vma:ffff8803a4f80190 mapping: (null) index:2b3d63d01 [113210.111065] file: (null) fault: (null) mmap: (null) readpage: (null) [113210.111168] CPU: 5 PID: 12310 Comm: python2 Tainted: G B 4.12.14-unRAID #1 [113210.111169] Hardware name: System manufacturer System Product Name/MAXIMUS IV GENE-Z/GEN3, BIOS 0402 10/19/2011 [113210.111170] Call Trace: [113210.111174] dump_stack+0x61/0x7e [113210.111177] print_bad_pte+0x207/0x225 [113210.111178] unmap_page_range+0x6d4/0x7f6 [113210.111180] unmap_single_vma+0x65/0x6f [113210.111181] unmap_vmas+0x51/0x7e [113210.111184] exit_mmap+0x6e/0x106 [113210.111186] mmput+0x49/0xe8 [113210.111189] flush_old_exec+0x5a9/0x61b [113210.111192] load_elf_binary+0x26d/0x132f [113210.111194] ? __vfs_read+0xbb/0xdf [113210.111197] search_binary_handler+0x70/0x1f3 [113210.111198] load_script+0x1bc/0x1cc [113210.111200] ? fuse_permission+0x21/0x112 [113210.111201] ? __inode_permission+0x48/0x9c [113210.111202] search_binary_handler+0x70/0x1f3 [113210.111204] do_execveat_common.isra.15+0x458/0x5bc [113210.111205] do_execve+0x1e/0x20 [113210.111206] SyS_execve+0x25/0x29 [113210.111208] do_syscall_64+0x5e/0xb4 [113210.111210] entry_SYSCALL64_slow_path+0x25/0x25 [113210.111211] RIP: 0033:0x2b3d55453897 [113210.111212] RSP: 002b:00002b3d6326d928 EFLAGS: 00000206 ORIG_RAX: 000000000000003b [113210.111213] RAX: ffffffffffffffda RBX: 0000000000000009 RCX: 00002b3d55453897 [113210.111214] RDX: 00002b3dbc005660 RSI: 00002b3dbc02d5b0 RDI: 00002b3dbc02e5c0 [113210.111215] RBP: 00002b3dbc005660 R08: 00002b3d54c15054 R09: 0000000000000015 [113210.111216] R10: 00000000000005a1 R11: 0000000000000206 R12: 00002b3d5c9836c8 [113210.111217] R13: 00002b3d5cd7d320 R14: 0000000000000035 R15: 00002b3dbc02ee70 Thanks in advance Please let me know if you want diags
October 3, 20178 yr The plugins page not allowing me to check for updates came back in this version as well after about 11 days. I cannot check for updates to unraid either. I figure I can no longer do a clean shutdown even if I dismount the array properly before doing a restart. Diagnostics attatched Edited October 5, 20178 yr by Jerky_san
October 3, 20178 yr I am unable to stop the array from the GUI as well. So.. that's not good I suppose. Whats weird is that it takes time to happen so some process is eventually dying or something.
October 3, 20178 yr Sorry if this is covered earlier but couldn't find it. Is the actual intention that we start using the longhexidecial.unraid.net as the primary URL for our NAS ? As I can't see anyway of setting an alternative additions. This is somewhat off putting for me and we can't even use CNAMEs as that will trigger a SSL warning. It is, I freely admit, quite a clever solution for a zero hassle setup for most people, but I'd really like to be able to add alternate names and the verification TXT DNS records. I'm also not 100% sure I want my internal IP addresses leaking, where is the longhexidecimal part coming from ? Would it be derivable ?
October 3, 20178 yr Can anyone suggest anything? Mover isnt functioning and i can't seem to bring the array down properly. It all just spins.
October 4, 20178 yr 15 hours ago, Jerky_san said: Can anyone suggest anything? Mover isnt functioning and i can't seem to bring the array down properly. It all just spins. I would try to break the problem into smaller pieces. Try turning off virtualisation. Try running in safe mode. Do the basic NAS functions work? If so you can run in normal mode with plugins but don't start any dockers. If that's ok, start your dockers. Finally, re-enable the virtualisation. At some point you're likely to enable something and the problems will start again. That should give you a clue.
October 4, 20178 yr 1 hour ago, John_M said: I would try to break the problem into smaller pieces. Try turning off virtualisation. Try running in safe mode. Do the basic NAS functions work? If so you can run in normal mode with plugins but don't start any dockers. If that's ok, start your dockers. Finally, re-enable the virtualisation. At some point you're likely to enable something and the problems will start again. That should give you a clue. Oct 1 20:40:12 Tower kernel: traps: emhttpd[8868] trap divide error ip:419a82 sp:2adb12a27e00 error:0 in emhttpd[400000+25000] <- this appeared in the log before everything went to hell.
October 4, 20178 yr Sep 30 20:59:15 Tower kernel: usb 2-1.4: reset full-speed USB device number 4 using ehci-pci Sep 30 20:59:15 Tower kernel: usb 2-1.4: reset full-speed USB device number 4 using ehci-pci Sep 30 20:59:18 Tower kernel: usb 2-1.4: reset full-speed USB device number 4 using ehci-pci Sep 30 20:59:18 Tower kernel: usb 2-1.4: reset full-speed USB device number 4 using ehci-pci Sep 30 20:59:18 Tower kernel: usb 2-1.4: reset full-speed USB device number 4 using ehci-pci Sep 30 20:59:18 Tower kernel: usb 2-1.4: reset full-speed USB device number 4 using ehci-pci Sep 30 20:59:24 Tower kernel: usb 2-1.4: reset full-speed USB device number 4 using ehci-pci Sep 30 20:59:24 Tower kernel: usb 2-1.4: reset full-speed USB device number 4 using ehci-pci Sep 30 20:59:24 Tower kernel: usb 2-1.4: reset full-speed USB device number 4 using ehci-pci Sep 30 20:59:25 Tower kernel: usb 2-1.4: reset full-speed USB device number 4 using ehci-pci Sep 30 20:59:26 Tower kernel: usb 2-1.4: reset full-speed USB device number 4 using ehci-pci Sep 30 20:59:26 Tower kernel: usb 2-1.4: reset full-speed USB device number 4 using ehci-pci There are stability issues with your unRAID USB stick (sandisk). Try moving it to a different USB port, preferably USB2.0. Edited October 4, 20178 yr by bonienl
October 4, 20178 yr 48 minutes ago, bonienl said: Sep 30 20:59:15 Tower kernel: usb 2-1.4: reset full-speed USB device number 4 using ehci-pci Sep 30 20:59:15 Tower kernel: usb 2-1.4: reset full-speed USB device number 4 using ehci-pci Sep 30 20:59:18 Tower kernel: usb 2-1.4: reset full-speed USB device number 4 using ehci-pci Sep 30 20:59:18 Tower kernel: usb 2-1.4: reset full-speed USB device number 4 using ehci-pci Sep 30 20:59:18 Tower kernel: usb 2-1.4: reset full-speed USB device number 4 using ehci-pci Sep 30 20:59:18 Tower kernel: usb 2-1.4: reset full-speed USB device number 4 using ehci-pci Sep 30 20:59:24 Tower kernel: usb 2-1.4: reset full-speed USB device number 4 using ehci-pci Sep 30 20:59:24 Tower kernel: usb 2-1.4: reset full-speed USB device number 4 using ehci-pci Sep 30 20:59:24 Tower kernel: usb 2-1.4: reset full-speed USB device number 4 using ehci-pci Sep 30 20:59:25 Tower kernel: usb 2-1.4: reset full-speed USB device number 4 using ehci-pci Sep 30 20:59:26 Tower kernel: usb 2-1.4: reset full-speed USB device number 4 using ehci-pci Sep 30 20:59:26 Tower kernel: usb 2-1.4: reset full-speed USB device number 4 using ehci-pci There are stability issues with your unRAID USB stick (sandisk). Try moving it to a different USB port, preferably USB2.0. I'll try.. the USB port its in currently is the onboard one that is sometimes present on supermicro motherboards. Was working well till the GUI webserver refresh that happened earlier in the RCs.
October 5, 20178 yr Guys, this has got to be the most ridiculous bug report ever. Bear with me here. So this is my first time trying out UEFI mode. I knew it was supported from rc5, but I put it off for a long time because it was painful for my back (old age makes them pop, ugh) to get the server out of the closet for once. So when the rc9f came out, I decided to switch to UEFI mode. Thought it'd be easy, just switch to the UEFI boot in the BIOS, reboot, stick it back in the closet, right? Bad timing. It was a movie night, and the server did not load. And by did not load, I mean nothing. No WebGUI. No SSH. No NetBIOS. The screen was black when I plugged it in. The fans whirred, the server was definitely on, but UnRAID wasn't loading at all. Unfortunately, we did not get to see a movie in time, so I had to scramble with my keyboard and switch it back to the standard legacy mode. This was weird, so today I dug the server out again. Time for some proper troubleshooting! So I knew sometimes the server failed to boot if a monitor wasn't plugged in (dunno why this happens, it happens once in a blue moon) *Note: After troubleshooting, I realized the monitor wasn't the problem. Read on. So I switched it back to UEFI mode. Huh, it boots normally. Rebooted it through the local console. Okay, rebooted, UEFI comes back up again, UnRAID loads properly, WebGUI comes up, yada yada. Put it back in the closet, power it up. Uhh... no UnRAID loading? Exactly the same symptoms. No SSH, no WebGUI, no NetBIOS. Black screen, but the server still ran. Pull it back out. Huh, screen is still black. Maybe I'll check the BIOS, so I decide to reboot with the key. Then I realized I didn't have a keyboard plugged in. Frantically plugging it in, I missed the F2 key boat, and the BIOS screen barrelled past - wait. UnRAID is loading. So it turns out, the UEFI mode for UnRAID doesn't work unless a keyboard is plugged in. This is ridiculously weird. I've tried various methods, like resetting the BIOS, moving the USB to another port, all the good stuff. None will do if the keyboard isn't plugged in. If the keyboard is plugged, the UEFI mode runs smoothly. No keyboard, nothing loads. This has got to be one of the stupidest bug reports ever. I know you guys think I'm kidding, but believe me, I do not shit around. Standard legacy mode boots always, but the UEFI mode refuses to load if it does not detect a keyboard. One thing to note, if I keep the monitor plugged in, I see UnRAID fails to load with the boot selection menu. You developers might know? That blue menu with the multiple UnRAID boot options and the "Automatic boot in 5 seconds" message. With a keyboard, it shows up with UEFI. Without keyboard, it won't even show up. It'll stay black (but keep outputting a signal to the monitor... I know this because the monitor doesn't go into eco mode) until I power it off with my power button. One more tip. If the server is locked up, frozen, whatever, you usually need to press the power button for a few seconds before it shuts down. With this keyboard-weirdness, one second click and the server instantly shuts down. So I'm guessing this is a bug in the EFI whatever? Can you guys look into this? Unfortunately, no diags, there's *literally* nothing on the local console, believe me. Staying on legacy until this is fixed.
October 5, 20178 yr 6 minutes ago, ideaman924 said: So I'm guessing this is a bug in the EFI whatever? You should mention the motherboards used, as I'm booting UEFI without a keyboard connected.
October 5, 20178 yr Just now, johnnie.black said: You should mention the motherboards used, as I'm booting UEFI without a keyboard connected. ASRock A55M-VS. It now occurred to me that it might be the UEFI implementation ASRock used. Thanks for reminding me johnnie.black. But does this mean I will be unable to utilize UEFI for the foreseeable future?
October 5, 20178 yr 1 minute ago, ideaman924 said: ASRock A55M-VS. It now occurred to me that it might be the UEFI implementation ASRock used. Check out the upgrades for BIOS. There might be one to address this issue.
October 5, 20178 yr Just now, Frank1940 said: Check out the upgrades for BIOS. There might be one to address this issue. No updates since 2013, and I remember updating it on 2014. I checked the website btw. I think this thing is EOL..
October 5, 20178 yr 22 minutes ago, ideaman924 said: ASRock A55M-VS. It now occurred to me that it might be the UEFI implementation ASRock used. Thanks for reminding me johnnie.black. But does this mean I will be unable to utilize UEFI for the foreseeable future? I have the exact same issue with an ASrock Z87 motherboard. Definitely a BIOS related bug. The only "solution" is to boot in legacy mode, cause ASrock doesn't do any BIOS updates anymore for ancient motherboards.
October 5, 20178 yr 1 hour ago, bonienl said: 2 hours ago, ideaman924 said: ASRock A55M-VS. It now occurred to me that it might be the UEFI implementation ASRock used. Thanks for reminding me johnnie.black. But does this mean I will be unable to utilize UEFI for the foreseeable future? I have the exact same issue with an ASrock Z87 motherboard. Definitely a BIOS related bug. The only "solution" is to boot in legacy mode, cause ASrock doesn't do any BIOS updates anymore for ancient motherboards. Or buy a cheap Keyboard (even looking at second hand shops) and leave it always plugged in... Edited October 5, 20178 yr by Frank1940
October 5, 20178 yr Have you tried it without the monitor too? I have an AMD box that won't boot without a monitor plugged in.
October 5, 20178 yr Author On 10/3/2017 at 2:43 PM, dsmith44 said: Sorry if this is covered earlier but couldn't find it. Is the actual intention that we start using the longhexidecial.unraid.net as the primary URL for our NAS ? As I can't see anyway of setting an alternative additions. This is somewhat off putting for me and we can't even use CNAMEs as that will trigger a SSL warning. It is, I freely admit, quite a clever solution for a zero hassle setup for most people, but I'd really like to be able to add alternate names and the verification TXT DNS records. I'm also not 100% sure I want my internal IP addresses leaking, where is the longhexidecimal part coming from ? Would it be derivable ? Please break this out into it's own topic since as you can see, it is getting lost here. The 'longhexidecimal' is not derived from any IP address.
October 6, 20178 yr 6 hours ago, jbartlett said: Have you tried it without the monitor too? I have an AMD box that won't boot without a monitor plugged in. Again, thought it was the monitor causing the issues (initial tests supported my suspicion) But after further testing I found out the monitor doesn't matter. The keyboard does...
Archived
This topic is now archived and is closed to further replies.