Can my old hardware support unRAID?

[PopSmith]

I didn't try to telnet to the server but I ran the command you mentioned and it only shows one line:

 

root 1130 1080 0 12:28 tty1 00:00:00 grep emhttp

 

I guess this would help explain why I can't access it via http://tower or http://192.168.0.188. (Update: access via the IP address works fine, tower does not)

 

I tried typing:

emhttp &

 

But it just spat out an error saying "mkdir: cannot create directory '/boot/config/shares': Not a directory

 

Update (again): I got to the Welcome screen. I decided to try it after Googling the above error and seeing this:

 

http://lime-technology.com/wiki/index.php?title=Installing_unRAID_on_a_full_Slackware_distro#Test_new_kernel_and_drivers_with_unRAID

 

"4. Log in and run emhttp -p 88. You should get error message “mkdir: cannot create directory `/boot/config/shares': Not a directory” ignore it for now.

If you get a segmentation fault, boot into the other kernel"

 

I just ran:

emhttp &

 

Instead of emhttp -p 88.

[PeterB]

This is odd!  Are you running a standard unRAID image?  Is your usb stick write-protected in some way?  Is your usb stick full?  Have you altered permissions on the directory structure of your usb stick?

 

In a standard setup, there should be nothing to prevent the creation of /boot/config files.

 

/boot is the root of your usb stick and config is one of the directories that should appear there.

[PopSmith]

I am running unRAID Basic version 5.0-beta9. The drive isn't write protected, after shutting down the server I copied a small text file to the drive (then deleted it) without issue. The stick definitely isn't full, it's a 256MB drive and unRAID is only taking up 78MB.

 

I have never altered the permissions of the drive in any way. The only thing sticking out to me is that there are no folders on the drive. Here's a screenshot of it (click it for the full size picture):

[PeterB]

Ah, that makes it clear!

 

You have de-archived the AiO.zip file into a flat, single level directory, rather than preserving the directory structure.  Check the options on your archiver software, and try again!