May 13, 200917 yr Hi all, I've just finished an unRAID install on a Slackware 12.2 system basically following the steps in this http://lime-technology.com/forum/index.php?topic=2073.msg17574#msg17574 post. I've got my unRAID kernel in and all looks good, but when I try to run emhttp I get a Segmentation fault. gdb backtrace; #0 0xb7dbc8c1 in strcmp () from /lib/libc.so.6 #1 0x08051ad6 in get_color () #2 0x08051d10 in get_status () #3 0x0804d4f2 in restart_md_driver () #4 0x0805279f in content_init () #5 0x0804c984 in init_dyncntnt () #6 0x0804ab87 in main () Any suggestions as to what might be wrong? Thanks, MrRandom
May 13, 200917 yr Author Scratch that, I omitted to run make modules_install so my unRAID module wasn't where it should have been. All up and running now.
September 25, 200916 yr Ok, I did run "make modules_install" and I am also getting a segmentation fault when I try to run emhttp -p 88. I've done a clean install twice and followed the Wiki instructions to the letter. When I look at http://192.168.1.10/ I get the expected, "It works!". Am I missing a module? Can the OP or someone else please help me learn what the gdb backtrace is if that's what I need to do?
September 26, 200916 yr This is almost always due to a kernel mismatch. When you compiled unraid.c and md.c, did you get any errors?
September 27, 200916 yr How can I tell if I got any errors when compiling? I ran make, make modules, make modules_install, make install then rebooted and it came up without panic. Are errors stored somewhere where I can see them? Thanks, Phil
November 2, 200916 yr Reviving this because I'm still having this issue, this time on another computer. My goal is to run a full slackware distro, which I've done successfully once before. I get to running emhttpd and I get a segmentation fault. bubbaQ, you mentioed it might be a kernel mismatch. Running uname -a I see that both are 2.6.27.7 but the unRAID 4.4.2 kernel is 2.6.27.7 #3 Nov 25th 2008, while the 2.6.27.7 downloaded from kernel.org is #2 Nov 20th 2008. Could this be doing it? If so, how do I get a hold of the #3 kernel? BTW, I tried building the kernel from 2.6.27.8 and got the same segmentation fault, which makes me think it might be something other than the kernel. How can I figure out what is causing this? Thanks, Phil/TW
Archived
This topic is now archived and is closed to further replies.