s34nDROID

How do I start with --auth or is it on by default?

I'm having some issues configuring this as well. I have the plugin installed. But it I can't figure out what ip I need to forward to on my router. Do I open the ports for my IP to the unRaid server? I did a port scan on my unRaid and 1194 didn't come back as being open. Is that normal?

Can anyone post a working package for 5b4? I tried to modify my self but I get: WARNING: Package has not been created with 'makepkg' Executing install script for hamachi-2.0.0.11-i686-unRAID.tgz. install/doinst.sh: line 2: modprob: command not found Package hamachi-2.0.0.11-i686-unRAID.tgz installed. scratch that missing an e

Don't know if anyone else experienced this but I couldn't figure out why my ssh wouldn't reinstall after reboot. It was because of it's dependencies being installed after openssh. Solved this by adding a -r to the sort of the auto install line

Thanks for the info guys. I had another go at installing and I got unraid to boot from the hard drive now. Got the web interface and everything. Only problem now is that when I add my array drives (SATA) lilo throws a VFS sync error saying it can't find the root file system (PATA). I'm lost on this one. I tried doing a boot:linux root=/dev/hd* and root=/dev/sd* but no dice. I think this is all that is missing now.

Well, since my classes have started back I will have to put this one on the back burner for now. I've gone back to my USB install of unraid and things are fine. However, I would like some info on using a PATA drive that isn't mounted in the array but is used to save changes and enable persistence when installing custom stuff. One example that I had trouble with before was installing twonky and then all my settings being gone after a reboot. Does anyone have any information on something like this? Is there a way to do like a ln -s to a cloned directory structure on my drive?

Thanks I will look into that. I hope it is something simple like that. I really don't want to compile yet another kernel. I'll keep an eye out for that guide. One more question though. So when I finally get this working and a new version of unraid is released what are my upgrade options? If the kernel unraid uses changes?

Hey bubbaQ glad to hear from you. Yeah that's the guide I used only differences are that I'm running 13.1 and the kernel for unraid 5-b4. Also, I copied over some more files and emhttp doesn't throw a segfualt now I get: root@slack:~# tail -f /var/log/syslog Feb 14 17:59:06 slack kernel: md: recovery thread woken up ... Feb 14 17:59:06 slack kernel: md: recovery thread syncing parity disk ... Feb 14 17:59:06 slack emhttp: _shcmd: shcmd (15): exit status: 1 Feb 14 17:59:06 slack emhttp: _shcmd: shcmd (14): exit status: 1 Feb 14 17:59:06 slack emhttp: _shcmd: shcmd (12): exit status: 1 Feb 14 17:59:06 slack emhttp: _shcmd: shcmd (13): exit status: 1 Feb 14 17:59:06 slack kernel: md: using 1152k window, over a total of 1953514552 blocks. Feb 14 17:59:07 slack kernel: can't shrink filesystem on-line Feb 14 17:59:07 slack last message repeated 3 times Feb 14 17:59:07 slack emhttp: main: can't bind listener socket: Address already in use Seems like emhttp is starting all on it own now which is great. But I also get some mkdir errors for the /mnt/diskx that claim the file exists.

root@slack:~# tail -f /var/log/syslog Feb 14 17:35:50 slack kernel: mdcmd (10): set spinup_group 0 0 Feb 14 17:35:50 slack kernel: mdcmd (11): set spinup_group 1 0 Feb 14 17:35:50 slack kernel: mdcmd (12): set spinup_group 2 0 Feb 14 17:35:50 slack kernel: mdcmd (13): set spinup_group 3 0 Feb 14 17:35:50 slack kernel: mdcmd (14): set spinup_group 5 0 Feb 14 17:35:50 slack kernel: mdcmd (15): spinup 0 Feb 14 17:35:50 slack kernel: mdcmd (16): spinup 1 Feb 14 17:35:50 slack kernel: mdcmd (17): spinup 2 Feb 14 17:35:50 slack kernel: mdcmd (18): spinup 3 Feb 14 17:35:50 slack kernel: mdcmd (19): spinup 5 Feb 14 17:37:52 slack emhttp: read_tokens: fopen /etc/unraid-version: No such fi le or directory Feb 14 17:37:52 slack emhttp: get_config_idx: fopen /boot/config/flash.cfg: No s uch file or directory - assigning defaults Feb 14 17:37:52 slack kernel: md: unRAID driver removed Feb 14 17:37:52 slack kernel: md: unRAID driver 2.0.0 installed Feb 14 17:37:52 slack kernel: mdcmd (1): mkslot 0 8,16 1953514552 Hitachi_HDS722 020ALA330_JK11B1YBJG7KKF Feb 14 17:37:52 slack kernel: mdcmd (2): mkslot 1 8,96 1465137492 ST31500341AS_9 VS144W3 Feb 14 17:37:52 slack kernel: mdcmd (3): mkslot 2 8,48 1465138552 ST31500341AS_9 VS133HV Feb 14 17:37:52 slack kernel: mdcmd (4): mkslot 3 8,64 1953514552 Hitachi_HDS722 020ALA330_JK1130YAG4DS1T Feb 14 17:37:52 slack kernel: mdcmd (5): mkslot 5 8,80 732573492 WDC_WD7500AAKS- 00RBA0_WD-WCAPT0650998 Feb 14 17:37:52 slack kernel: mdcmd (6): mkarray Feb 14 17:37:52 slack kernel: md: import disk0: [8,16] (sdb) Hitachi_HDS722020AL A330_JK11B1YBJG7KKF size: 1953514552 Feb 14 17:37:52 slack kernel: md: import disk1: [8,96] (sdg) ST31500341AS_9VS144 W3 size: 1465137492 Feb 14 17:37:52 slack kernel: md: import disk2: [8,48] (sdd) ST31500341AS_9VS133 HV size: 1465138552 Feb 14 17:37:52 slack kernel: md: import disk3: [8,64] (sde) Hitachi_HDS722020AL A330_JK1130YAG4DS1T size: 1953514552 Feb 14 17:37:52 slack kernel: md: import disk5: [8,80] (sdf) WDC_WD7500AAKS-00RB A0_WD-WCAPT0650998 size: 732573492 Feb 14 17:37:53 slack kernel: mdcmd (7): set md_num_stripes 1280 Feb 14 17:37:53 slack kernel: mdcmd (: set md_write_limit 768 Feb 14 17:37:53 slack kernel: mdcmd (9): set md_sync_window 288 Feb 14 17:37:53 slack kernel: mdcmd (10): set spinup_group 0 0 Feb 14 17:37:53 slack kernel: mdcmd (11): set spinup_group 1 0 Feb 14 17:37:53 slack kernel: mdcmd (12): set spinup_group 2 0 Feb 14 17:37:53 slack kernel: mdcmd (13): set spinup_group 3 0 Feb 14 17:37:53 slack kernel: mdcmd (14): set spinup_group 5 0 Feb 14 17:37:53 slack kernel: mdcmd (15): spinup 0 Feb 14 17:37:53 slack kernel: mdcmd (16): spinup 1 Feb 14 17:37:53 slack kernel: mdcmd (17): spinup 2 Feb 14 17:37:53 slack kernel: mdcmd (18): spinup 3 Feb 14 17:37:53 slack kernel: mdcmd (19): spinup 5 So here's a tail of my syslog when I do the emhttp -p 88 command It seems to be looking for flash.cfg but it's not there that's the only error that I see.

So I pulled an all-nighter and I got to a bootable kernal. Using Slack 13.1 and 2.6.36.2 kernal compiled for unraid version 5-b4. Apache still shows It works! and I've got the files from my previous install copied over. When I run emhttp I get a segfault and this is where I'm stuck. I'm even thinking of installing Slack 12.1 since that's what the guide is based off of but I wanted to get my system to the most current distro and version of unraid so I could stick with it for awhile. Anyone got any idea what it might be?

So I tried to tackle this one today and I have to admit I'm pretty frustrated at this point. I really want to make this work though so I'm not giving up yet. I was looking for information (guide) on how to install unraid on full slackware system. I just want the added flexibility to run more servers and media centric services on one box. I've followed the guide but it's not very clear or up to date. I'm not bashing the guide because it got me pretty far in the process but it seems like things have changed quite a bit since it was written. Does anyone have any information or update guides I can take a gander at? Trying to install 4.7 on Slack 13.1. Thanks for any help and I've searched but just haven't found what I'm looking for.