November 6, 200916 yr Had to replace the hostname and inet1 sections of rc.M with this from the unRAID rc.M when I noticed there was no mention of ifplugd in the Slack rc.M: # Set the hostname. # tmm - modified to get hostname from ident.cfg file and ensure hostname is # defined as localhost alias in /etc/hosts (this lets wins name resolution work) if [ -r /boot/config/ident.cfg ]; then /usr/bin/fromdos </boot/config/ident.cfg >/var/tmp/ident.cfg source /var/tmp/ident.cfg else # fall back on this default: NAME=Tower fi /bin/hostname $NAME echo "# Generated" >/etc/hosts echo "127.0.0.1 $NAME localhost" >>/etc/hosts # Initialize the networking hardware. # tmm - if ifplugd is present, let it bring up the network h/w if [ -x /etc/rc.d/rc.inet1 ]; then if [ -x /etc/rc.d/rc.ifplugd ]; then . /etc/rc.d/rc.inet1 . /etc/rc.d/rc.ifplugd start else . /etc/rc.d/rc.inet1 start fi fi I'll check rc.S next to make sure there's no missing critical sections. The attached file contains my unraid and original slack rc.d files.
November 6, 200916 yr Author Do you mean disable the amd74xx in menuconfig config prior to running make? Yup.
November 7, 200916 yr I'm running on Slackware-Current (13.0 with all patches) and I am NOT using ifplugd. In my case it's not needed since it's always plugged in. It also saved me time in modifying various rc.d startup scripts.
November 7, 200916 yr Ok, I thought since ifplugd was missing it might be part of the problem, but it sounds like it's not. What exactly does ifplugd do, and more importantly, any recomendations on how to get my box working with the full install? BubbaQ, I removed amd74xx from the .config and ran make, still getting the same segfault result. Just wondering, why do you think removing that might help and what driver do you want to be interfacing with the hard drive? Thanks, Phil/TW
November 7, 200916 yr Just noticed something that might be relevant. This is an ls of my /boot directory on the hard drive: total 24045 drwxr-xr-x 2 root root 920 Nov 6 08:41 ./ -rw------- 1 root root 97792 Nov 6 08:41 map -rw-r--r-- 1 root root 890272 Nov 6 08:41 System.map -rw-r--r-- 1 root root 1869936 Nov 6 08:41 vmlinuz drwxr-xr-x 23 root root 536 Nov 6 07:05 ../ -rw-r--r-- 1 root root 891468 Nov 6 06:41 System.old -rw-r--r-- 1 root root 1874096 Nov 6 06:41 vmlinuz.old -rw-r--r-- 1 root root 512 Nov 3 21:15 boot.0300 -rw-r--r-- 1 root root 168 Nov 3 21:15 boot_message.txt lrwxrwxrwx 1 root root 28 Nov 3 21:13 config -> config-huge-smp-2.6.27.7-smp lrwxrwxrwx 1 root root 37 Nov 3 20:55 README.initrd -> /usr/doc/mkinitrd-1.3.2/README.initrd -rw-r--r-- 1 root root 5040 Nov 29 2008 diag1.img -rw-r--r-- 1 root root 1393024 Nov 20 2008 System.map-huge-2.6.27.7 -rw-r--r-- 1 root root 89081 Nov 20 2008 config-huge-2.6.27.7 -rw-r--r-- 1 root root 4540208 Nov 20 2008 vmlinuz-huge-2.6.27.7 -rw-r--r-- 1 root root 927553 Nov 20 2008 System.map-generic-2.6.27.7 -rw-r--r-- 1 root root 89202 Nov 20 2008 config-generic-2.6.27.7 -rw-r--r-- 1 root root 2220880 Nov 20 2008 vmlinuz-generic-2.6.27.7 -rw-r--r-- 1 root root 1432921 Nov 20 2008 System.map-huge-smp-2.6.27.7-smp -rw-r--r-- 1 root root 89384 Nov 20 2008 config-huge-smp-2.6.27.7-smp -rw-r--r-- 1 root root 4727664 Nov 20 2008 vmlinuz-huge-smp-2.6.27.7-smp -rw-r--r-- 1 root root 965704 Nov 20 2008 System.map-generic-smp-2.6.27.7-smp -rw-r--r-- 1 root root 89505 Nov 20 2008 config-generic-smp-2.6.27.7-smp -rw-r--r-- 1 root root 2347888 Nov 20 2008 vmlinuz-generic-smp-2.6.27.7-smp -rw-r--r-- 1 root root 15754 Feb 21 2008 slack.bmp In my lilo.conf I'm pointing at vmlinux-huge-smp-2.6.27.7-smp but it still has the Nov 20, 2008 date which is the date it was minted, while vmlinuz has dates reflecting it's been messed with lately. Is it possible when I run the final make install it's updating vmlinuz when it should be updating vmlinux-huge-smp-2.6.27.7-smp, or perhaps I should be pointing lilo.conf to vmlinuz? Thanks, Phil/TW
November 7, 200916 yr This has got to be it, I was booting into my backup kernel the whole time so no wonder I kept seeing the same thing. I booted into the other vmlinuz kernel and was able to run emhttp WITH NO SEGFAULT ;D ;D ;D I'm doing a fresh install from scratch just to wipe the slate clean, I'll report on how it goes. Thanks again, Phil/TW
November 7, 200916 yr Author perhaps I should be pointing lilo.conf to vmlinuz Yup... that is part of the instructions I put in the wiki.
November 7, 200916 yr You sure did, I must have understod you the first time then got it in my head backwards this time. I'm so happy it's working! Also, user shares are working. My next project is getting moblock-control working, which I did on another slack machine, so it shouldn't be too hard . Famous last words. Thanks for your help, Phil/TW
February 3, 201016 yr Does anyone know what kernel to use with the newest version of unraid (4.5 Final)?
February 3, 201016 yr Does anyone know what kernel to use with the newest version of unraid (4.5 Final)? unRAID 4.5 - 2.6.31.6 According to: http://lime-technology.com/forum/index.php?topic=4844.msg44480;topicseen#msg44480 unRAID 4.5.1 - 2.6.31.12 According to: http://lime-technology.com/forum/index.php?topic=4844.msg48339;topicseen#msg48339
February 4, 201016 yr The base is still slackware 12.2 isn't it? I'm more concerned about fuse and samba support rather than kernel's (I've patched and compiled that enough times not to really worry about the kernel version).
February 4, 201016 yr I used 13.0 for my last build. I've got to rebuild my server so that gives me a good reason for upgrading.
July 27, 201015 yr For those running unRAID on a full Slackware distro: How do you backup your system drive so that you can restore in the event of a crash? If this were a Windows system I'd take a Ghost image or something similar periodically, but I don't know what the best approach is in Slackware/Linux? How have others solved this problem? Thanks, Phil/TW
November 1, 201015 yr Hate to resurrect an old thread, but has anybody managed to do this on a newer build of unRAID (5.0b2 by any chance)? I'm thinking of building a unRAID/SageTV linux combo box (either that, or a unRAID + SageTV VMs on ESXi).
November 1, 201015 yr Yes. I have 5.0beta2 running on a Slackware Current (13.2), 64bit none the less too.
November 1, 201015 yr Hate to resurrect an old thread, but has anybody managed to do this on a newer build of unRAID (5.0b2 by any chance)? I'm thinking of building a unRAID/SageTV linux combo box (either that, or a unRAID + SageTV VMs on ESXi). If you are able to get unRAID and SageTV linux combo working let me know. I want to go down this route myself. Don't think I'll make it but want to try. That's also why I ordered the $20 C2SEE last week so that I can use my current production board X7SBE with quad core as test system until I get it working and still have production unRAID untouched.
November 1, 201015 yr Yes. I have 5.0beta2 running on a Slackware Current (13.2), 64bit none the less too. Think you could post up your .config file, and maybe some tips on how you got it running? I've been wrestling with the unRAID part of the puzzle this past weekend, but I'm pretty sure my issue is I'm trying to do it in VMWare workstation (don't have all the hardware in yet that I'm going to use on the box, and my drives should be in this week).
November 1, 201015 yr There are some caveats to running under 64bit, like preclear_disk.sh does not work, it fails the post-clear tests because of byte endian being different under 64bit than 32bit. To run under 64bit, you need to use Alien Bob's multilib-enabled 32bit and 64bit tools. I posted the details in the thread "unRaid 64bit" The only item that's needed in the linux .config is to copy over the "unraid/usr/src/linux/drivers/md/*" into "/usr/src/linux/drivers/md" and then select "md unRAID" to load as a module. That's all that's special inside the Linux kernel configuration. The rest of the kernel is configured as I saw fit.
December 2, 201015 yr Will the instructions as per http://www.lime-technology.com/wiki/index.php?title=Installing_unRAID_on_a_full_Slackware_distro work with -current (or 13.1?) and the soon to be released unRAID 4.6 or current rc? Any obstacles or gotchas that I should be on the look out for? Also, addons (sabnzbd, sickbeard, etc) are run from usb or dependencies need to be installed for these apps to run on the hard drive?
December 13, 201015 yr I just installed unRAID 4.6 on a fresh installation of 32-bit Slackware 13.1, loosely following the directions at http://www.lime-technology.com/wiki/index.php?title=Installing_unRAID_on_a_full_Slackware_distro I didn't have any "legacy" info in my unRAID configuration, so I chose kernel options to conform to the Slackware defaults (for instance, using the 'experimental' PATA drivers in libsata instead of the older ATA/IDE/etc option for PATA drives; this causes PATA drives to show up as /dev/sd* instead of /dev/hd*). Notable changes from the wiki instructions: kernel version is linux-2.6.32.9 You additionally need to copy over the following files from the unRAID distribution into your full Slackware distribution: /lib/libvolume_id.so.1.1.0 (and create a symlink to it from /lib/libvolume_id.so.1), /etc/exports-, /var/spool/cron/crontabs/root- The names of a variety of kernel options have changed; hopefully you can figure it out. I chose to disable "Device Drivers > ATA/ATAPI/MFM/RLL support" entirely, and enable the PATA drivers in "Serial ATA (prod) and Parallel ATA (experimental) drivers" instead, as explained above. Here's my kernel config: http://pastebin.com/HTnU8nYLp. Note that this is specific to my hardware, and is unlikely to work for you without modifications. Various things (lilo comes to mind) kept complaining that module 'dm-mod' did not exist. The unRAID kernel config files in the devices/md directory disabled the option to create it. To work around this: 1) build your kernel as specified in the wiki and make sure your system boots successfully; 2) replace /usr/src/linux/drivers/md/Makefile with this and /usr/src/linux/drivers/md/Kconfig with this; 3) 'make oldconfig' and enable dm-mod as a module, then 'make modules && make modules_install'; 4) add '/sbin/modprobe dm-mod' to /etc/rc.d/rc.modules. edit: it's probably better to download these two files (using wget) from my personal host here: http://www.nickmerryman.com/unraid/dmmod_2.6.32.9/ or from the attachments to this post (you'll have to rename the files) Follow the instructions in this thread to work around an issue in the UI where emhttp tries to call modprobe with an unsupported flag. I think the instructions there are slightly incorrect, or at least a bit unclear; you should replace "modprobe -rw" with "rmmod -w " (that's "rmmod<space><space><space><space>-w<space>", such that there are now two spaces between "-w" and "md-mod" and four spaces between "rmmod" and "-w"). Editing the binary in 'vim' worked fine for me. Also, the preclear script needs updating for Slackware 13.1. See my post here for details. Joe said he'd update the main script, but in the meantime I've made my locally edited version of the preclear script available here. I make no promises whatsoever about the script, other than it seems to have worked for me I think that's everything different from the wiki that I had to do. My drives are currently 'preclearing', and the only annoyance I currently have is that the "flash" samba share that unRAID creates shares my /boot partition, rather than actually sharing the /flash directory as its name would imply. And I have something set up wrong such that I don't get a pretty framebuffer on boot, but that's a) my own problem and b) not really a big deal. edit 12/13/2010: added preclear script details Kconfig.txt Makefile.txt
December 14, 201015 yr I just installed unRAID 4.6 on a fresh installation of 32-bit Slackware 13.1, loosely following the directions at http://www.lime-technology.com/wiki/index.php?title=Installing_unRAID_on_a_full_Slackware_distro I didn't have any "legacy" info in my unRAID configuration, so I chose kernel options to conform to the Slackware defaults (for instance, using the 'experimental' PATA drivers in libsata instead of the older ATA/IDE/etc option for PATA drives; this causes PATA drives to show up as /dev/sd* instead of /dev/hd*). Notable changes from the wiki instructions: kernel version is linux-2.6.32.9 You additionally need to copy over the following files from the unRAID distribution into your full Slackware distribution: /lib/libvolume_id.so.1.1.0 (and create a symlink to it from /lib/libvolume_id.so.1), /etc/exports-, /var/spool/cron/crontabs/root- The names of a variety of kernel options have changed; hopefully you can figure it out. I chose to disable "Device Drivers > ATA/ATAPI/MFM/RLL support" entirely, and enable the PATA drivers in "Serial ATA (prod) and Parallel ATA (experimental) drivers" instead, as explained above. Here's my kernel config: http://pastebin.com/HTnU8nYLp. Note that this is specific to my hardware, and is unlikely to work for you without modifications. Various things (lilo comes to mind) kept complaining that module 'dm-mod' did not exist. The unRAID kernel config files in the devices/md directory disabled the option to create it. To work around this: 1) build your kernel as specified in the wiki and make sure your system boots successfully; 2) replace /usr/src/linux/drivers/md/Makefile with this and /usr/src/linux/drivers/md/Kconfig with this; 3) 'make oldconfig' and enable dm-mod as a module, then 'make modules && make modules_install'; 4) add '/sbin/modprobe' to /etc/rc.d/rc.modules. Follow the instructions in this thread to work around an issue in the UI where emhttp tries to call modprobe with an unsupported flag. I think the instructions there are slightly incorrect, or at least a bit unclear; you should replace "modprobe -rw" with "rmmod -w " (that's "rmmod<space><space><space><space>-w<space>", such that there are now two spaces between "-w" and "md-mod" and four spaces between "rmmod" and "-w"). Editing the binary in 'vim' worked fine for me. I think that's everything different from the wiki that I had to do. My drives are currently 'preclearing', and the only annoyance I currently have is that the "flash" samba share that unRAID creates shares my /boot partition, rather than actually sharing the /flash directory as its name would imply. And I have something set up wrong such that I don't get a pretty framebuffer on boot, but that's a) my own problem and b) not really a big deal. Thanks for your help nick. But moving Makefile and Kconfig into the md directory gives me errors while issuing make oldconfig: /usr/src/linux# make oldconfig scripts/kconfig/conf -o arch/x86/Kconfig drivers/md/Kconfig:29: unknown option "Higher" drivers/md/Kconfig:31: unknown option "To" drivers/md/Kconfig:32: unknown option "called" drivers/md/Kconfig:34: unknown option "If" drivers/md/Kconfig:42: unknown option "If" drivers/md/Kconfig:54: unknown option "Information" drivers/md/Kconfig:56: unknown option "http" drivers/md/Kconfig:58: unknown option "To" drivers/md/Kconfig:59: unknown option "be" drivers/md/Kconfig:61: unknown option "If" drivers/md/Kconfig:112: unknown option "If" drivers/md/Kconfig:122: unknown option "If" drivers/md/Kconfig:131: unknown option "If" drivers/md/Kconfig:144: 'endif' in different file than 'if' drivers/md/Kconfig:7: location of the 'if' drivers/Kconfig:116: 'endmenu' in different file than 'menu' drivers/md/Kconfig:7: location of the 'menu' make[1]: *** [oldconfig] Error 1 make: *** [oldconfig] Error 2
December 14, 201015 yr Thanks for your help nick. But moving Makefile and Kconfig into the md directory gives me errors while issuing make oldconfig: Strange. I just double-checked, and it still works fine for me. Have you successfully compiled and booted into the kernel without this tweak for dm-mod? You're using kernel 2.6.32.9, right? Take a look at the bottom of that Kconfig file. Make sure it includes the last two lines; it's easy to accidentally miss a line at the bottom of a large copy/paste: endmenu endif If that doesn't work, just replace them both with the originals that you copied over from the /unraid/ directory (from the wiki's instructions). dm-mod might not be absolutely critical...
Archived
This topic is now archived and is closed to further replies.