applehead Posted June 23, 2011 Share Posted June 23, 2011 Hello all, I've been following the wiki article for installing Full Slackware and unRAID 5.0beta. I am using Slackware v13.1 and Kernel 2.6.37.6 to match the kernel version of unRAID 5.0beta7. I have successfully gotten through the article and it looks like my disks are now mounting (but not the user shares yet). However, when I try to launch "emhttp -p 88" to get the web management console up, I get a segmentation fault. I see that a lot of other users on here have had a similar problem, but none of the posts detailed any resolution steps. One post mentioned that I should run "modprobe md_mod", but that did not remedy the problem. I am new to building kernels from scratch. How do I troubleshoot this problem? Thanks! Link to comment
Joe L. Posted June 23, 2011 Share Posted June 23, 2011 Hello all, I've been following the wiki article for installing Full Slackware and unRAID 5.0beta. I have successfully gotten through the article and it looks like my disks are now mounting (but not the user shares yet). However, when I try to launch "emhttp -p 88" to get the web management console up, I get a segmentation fault. I see that a lot of other users on here have had a similar problem, but none of the posts detailed any resolution steps. One post mentioned that I should run "modprobe md_mod", but that did not remedy the problem. I am new to building kernels from scratch. How do I troubleshoot this problem? Thanks! Does /proc/mdcmd exist? If not, that is your first issue to attack. Can you "cat" it to get the disk status? If you cannot, neither can emhttp. Link to comment
applehead Posted June 23, 2011 Author Share Posted June 23, 2011 Does /proc/mdcmd exist? If not, that is your first issue to attack. Can you "cat" it to get the disk status? If you cannot, neither can emhttp. Yes, it exists, and I can 'cat mdcmd' and it returns a bunch of device data. I should also add that dmesg is giving me the following output relating to emhttp: emhttp[5735]: segfault at 0 ip b754896c sp bfe57040 error 4 in libc-2.11.1.so[b7518000+15c000] emhttp[5748]: segfault at 0 ip b745e96c sp bfb89a90 error 4 in libc-2.11.1.so[b742e000+15c000] Link to comment
applehead Posted June 24, 2011 Author Share Posted June 24, 2011 Does anyone know where I should look next? Or is this just a roadblock because it is beta software? Link to comment
BRiT Posted June 25, 2011 Share Posted June 25, 2011 No. It's a problem specific to the setup you're running, as I have unRAID 5.0b7 running on a full Slackware 13.37 64bit distro with no issues at all. I've never had the issues you're posting about with any of the releases of unRAID from 4.5.x through 5.0b7 and I think you can agree my setup is far outside of any 'supported' environment and it works flawlessly. Link to comment
bubbaQ Posted June 25, 2011 Share Posted June 25, 2011 Does anyone know where I should look next? Use strace. Link to comment
applehead Posted June 27, 2011 Author Share Posted June 27, 2011 Thanks guys. I did an strace and it didn't reveal anything particularly helpful. I wish I had saved a copy of the output for you. Since I followed the wiki instructions exactly, but it didn't work, I blew away this install and am in the process of attempting the approach with Slack 12.2 with Unraid 4.7. Even though I wasn't able to get 5.0b7 working with the limited amount of time I could dedicate to it, I did find a few minor glitches in the instructions and have made some updates to the wiki for the benefit of the community. Link to comment
BRiT Posted June 27, 2011 Share Posted June 27, 2011 How are you certain there were glitches and your corrections are needed if you weren't able to successfully get it installed? Link to comment
applehead Posted June 28, 2011 Author Share Posted June 28, 2011 How are you certain there were glitches and your corrections are needed if you weren't able to successfully get it installed? Spelling mistakes and syntax errors for a couple of commands. Just minor updates. Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.