tevert Posted May 13, 2011 Share Posted May 13, 2011 I've tried this a number of times for both 4.7 and the latest 5.0 beta with no success. I've very meticulously followed the wiki, and emhttp always segfaults when I get to that step in either 4.7 or 5.0 b6a. I read a post here with the same errors, but didn't find anything that applied to my situation that I could tell. emhttp: unRAID System Management Utility version 5.0-beta6a emhttp: Copyright (C) 2005-2011, Lime Technology, LLC emhttp: Pro key detected, GUID: 0781-5406-4857-411DC342805E emhttp: shcmd (1): udevadm settle emhttp: Device inventory: emhttp: Maxtor_6L300R0_L60MMHPH (sda) 293057320 emhttp: shcmd (2): modprobe md-mod super=/boot/config/super.dat slots=21 2>&1 |logger logger: FATAL: Error inserting md_mod (/lib/modules/2.6.36.2-unRAID/kernel/drivers/md/md-mod.ko): Unknown symbol in module, or unknown parameter (see dmesg) emhttp: diskId.0 not found kernel: emhttp[32449]: segfault at 0 ip 08050579 sp bf863f60 error 4 in emhttp[8048000+15000] strace snippet: (entire strace.txt attached) stat64("/proc/mdcmd", 0xbf928970) = -1 ENOENT (No such file or directory) time(NULL) = 1305312299 send(4, "<14>May 13 11:44:59 emhttp: diskI"..., 46, MSG_NOSIGNAL) = 46 --- SIGSEGV (Segmentation fault) @ 0 (0) --- I've reviewed the make compile log and no errors there. FWIW dmesg says: md_mod: Unknown parameter `super' md_mod: Unknown parameter `super' What should I look at next? I must be close, but I'm stuck. Thanks! Tony strace.txt Quote Link to comment
tevert Posted May 18, 2011 Author Share Posted May 18, 2011 Is this the end of my dream? Anyone have anything to look at or try? Tony Quote Link to comment
bubbaQ Posted May 18, 2011 Share Posted May 18, 2011 Which Wiki article did you "follow?" Quote Link to comment
tevert Posted May 18, 2011 Author Share Posted May 18, 2011 http://lime-technology.com/wiki/index.php?title=Installing_unRAID_5.0_on_a_full_Slackware_Distro Thank you for the reply!!! :-) Quote Link to comment
bubbaQ Posted May 18, 2011 Share Posted May 18, 2011 Are you sure the kernel and all modules build w/o errors? Quote Link to comment
tevert Posted May 18, 2011 Author Share Posted May 18, 2011 As far as I can tell everything went well there. I've attached the compile log. On make modules_install the md module showed up as DEPMOD which was different from the rest, but I assumed that was OK--is it? Thanks again for your help! make.log.txt Quote Link to comment
bubbaQ Posted May 18, 2011 Share Posted May 18, 2011 Is the flash mounted properly? Does "/boot/config/super.dat" exist? Quote Link to comment
tevert Posted May 18, 2011 Author Share Posted May 18, 2011 Yes, /boot/config/super.dat exists and is the file from the flash drive. I appreciate you sticking with me on this so much! Tony Quote Link to comment
tevert Posted May 18, 2011 Author Share Posted May 18, 2011 dmesg outputs: md_mod: Unknown parameter `super' emhttp[1355]: segfault at 0 ip 08050579 sp bfe8f5c0 error 4 in emhttp[8048000+15000] Attaching the full dmesg output. dmesg.txt Quote Link to comment
bubbaQ Posted May 19, 2011 Share Posted May 19, 2011 Try "modprobe md-mod" w/o a command line and see what you get back.... check syslog and dmesg. Quote Link to comment
tevert Posted May 19, 2011 Author Share Posted May 19, 2011 nothing came back in either /var/log/syslog or /var/log/dmesg or /var/log/messages after running #modprobe md-mod At the moment all my drives and the flash are installed. /var/log/messages shows the following when I try to run emhttp -p 88 emhttp: unRAID System Management Utility version 5.0-beta6a emhttp: Copyright (C) 2005-2011, Lime Technology, LLC emhttp: Pro key detected, GUID: 0781-5406-4857-41<******> emhttp: shcmd (1): udevadm settle emhttp: Device inventory: emhttp: Maxtor_6L300R0_L60MMHPH (sda) 293057320 emhttp: WDC_WD2001FASS-00U0B0_WD-WMAUR0194407 (sdc) 1953514552 emhttp: WDC_WD6400AAKS-00A7B0_WD-WCASY0013739 (sdf) 625131832 emhttp: WDC_WD1001FALS-00K1B0_WD-WMATV0782348 (sdd) 976762552 emhttp: WDC_WD2001FASS-00W2B0_WD-WMAY00649474 (sde) 1953514552 emhttp: SAMSUNG_HD753LJ_S13UJ1CQ600821 (sdh) 732574552 emhttp: WDC_WD2001FASS-00U0B0_WD-WMAUR0193889 (sdg) 1953514552 emhttp: MD01200-BJDW_MW0WCANM1163371 (sdj) 120627328 emhttp: WDC_WD6400AAKS-00A7B0_WD-WCASY0015595 (sdi) 625131832 emhttp: shcmd (2): modprobe md-mod super=/boot/config/super.dat slots=21 2>&1 |logger emhttp: diskId.0 not found kernel: emhttp[1539]: segfault at 0 ip 08050579 sp bfb56890 error 4 in emhttp[8048000+15000] Booting off the flash works. Thanks again so much for your help on this!! Tony Quote Link to comment
TaterSalad Posted May 19, 2011 Share Posted May 19, 2011 Do you see a /proc/mdcmd ? If not, that means your kernel was not properly built and unRAID didnt get implemented into it. In the 5.06a guide, I had to add the following in my make menuconfig: Device Drivers -> Multiple Device Support -> (*) Multiple devices driver support (unRAID) and <M> RAID support Watch your build and make sure unRAID gets implemented. You should see something like this compile: drivers/md.c And something about unRAID later... Quote Link to comment
tevert Posted May 19, 2011 Author Share Posted May 19, 2011 Wow. That was the clue I was looking for! My menuconfig did not have: Device Drivers -> Multiple Device Support -> (*) Multiple devices driver support (unRAID) On further investigation I found that inexplicably, WinSCP put the drivers folder inside the drivers folder (/usr/src/linux/drivers/drivers/md) I'm really puzzling over that. I'm not sure what its reason for rewriting the paths like that was--how or why it did that. (It's generally well-behaved for me). Anyway, after making sure the md folder went where I actually told it to go, I now have the unRaid MD listed in menuconfig. Recompiled the kernel. Rebooted. And... emHTTP starts! Wow thanks again! I sooooo appreciate your help! Ran mkmbr on my drives to get my files back and we're in business! I am sooo happy. Thank you again so much for helping me out on this. Tony Quote Link to comment
TaterSalad Posted May 19, 2011 Share Posted May 19, 2011 Glad I was of help. I had the exact same problem and it took a few days (and a few forum posts) for me to get it right. I am not sure if this is something that affects everyone or not. If it does, adding Device Drivers -> Multiple Device Support -> (*) Multiple devices driver support (unRAID) and <M> RAID support should definitely be added to the Wiki. Can anyone more versed on the subject comment? Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.