Ambrotos

A 1Gig Memorex TravelDrive. Andrew

unRAID has been installed as per the instructions here http://lime-technology.com/support/unraid-server-installation. It is installed on a flash with a single FAT32 partition, detected as sdb. There is also a single SATA (sda) hard drive in the system. It happens to have previously been used as a windows 7 system drive, so it has 2 partitions: one 100MB boot partition labeled "system reserved" and one 300GB NTFS partition that's not shown (probably because UNRAID doesn't support NTFS out of the box). Is your recommendation then that all drives newly inserted into an UNRAID box must be completely blank of partitions, or it will cause UNRAID to fail to boot? If so I'll certainly give that a try, but it seems like a pretty glaring weakness. If UNRAID is mounting based on volume label, I don't see why a partition on a separate drive with no label conflict is causing it problems. Andrew

Joe, The HD in the system used to be a windows drive. Windows 7 creates a small 100MB partition called "System Reserved" during installation for boot files. You'll notice that System Reserved is on sda whereas my flash is sdb. Here are the contents on /boot. As you can see, it's not quite entirely empty. I also listed the contents of /boot after having mounted the flash. root@Tower:/# ls -al /boot total 0 drwxr-xr-x 3 root root 0 2011-10-27 22:32 ./ drwxr-xr-x 16 root root 0 2011-10-27 22:32 ../ drwxr-xr-x 2 root root 0 2011-10-27 22:32 config/ root@Tower:/# ls -al /boot/config total 0 drwxr-xr-x 2 root root 0 2011-10-27 22:32 ./ drwxr-xr-x 3 root root 0 2011-10-27 22:32 ../ root@Tower:/# mount -L UNRAID /boot root@Tower:/# ls -al /boot total 74792 drwxr-xr-x 3 root root 4096 1970-01-01 00:00 ./ drwxr-xr-x 16 root root 0 2011-10-27 22:32 ../ -rwxr-xr-x 1 root root 2567072 2011-11-25 09:40 bzimage* -rwxr-xr-x 1 root root 73726096 2011-11-25 09:41 bzroot* drwxr-xr-x 2 root root 4096 2011-12-27 13:09 config/ -r-xr-xr-x 1 root root 13639 2011-12-27 13:10 ldlinux.sys* -rwxr-xr-x 1 root root 5162 2011-11-25 09:41 license.txt* -rwxr-xr-x 1 root root 781 2011-11-25 09:41 make_bootable.bat* -rwxr-xr-x 1 root root 165080 2011-11-25 09:41 memtest* -rwxr-xr-x 1 root root 33404 2011-11-25 09:41 menu.c32* -rwxr-xr-x 1 root root 13579 2011-11-25 09:41 readme.txt* -rwxr-xr-x 1 root root 183 2011-11-25 09:41 syslinux.cfg* -rwxr-xr-x 1 root root 27136 2011-11-25 09:41 syslinux.exe* root@Tower:/#

Joe, Yes, the volume label of my flash is exactly 'UNRAID'. Here's the output of the commands you suggested. I think we can conclude that the flash is not being mounted properly, as I don't see any reference to /boot. I suppose the question now is why. This is a very basic machine -- 1 SATA HD, 1 SATA DVD, 1 USB flash, and KVM. I wouldn't have thought there'd be anything to conflict. Tower login: root Linux 3.1.1-unRAID. root@Tower:~# mount proc on /proc type proc (rw) sysfs on /sys type sysfs (rw) root@Tower:~# ls -l /dev/disk/by-label total 0 lrwxrwxrwx 1 root root 10 2011-12-28 18:01 System\\x20Reserved -> ../../sda1 lrwxrwxrwx 1 root root 10 2011-12-28 18:01 UNRAID -> ../../sdb1 root@Tower:~# So my flash is detected as sdb1, and we can see that it's labeled properly. Any suggestions how to figure out why it's not mounting? Andrew

I've tried resets and shutdowns. Either way it's always initiated via the shutdown/reset buttons on unRAID's web GUI. I don't think it's related to the way I'm restarting though, as the emhttp daemon never started properly, even on first power-up after immediately after having programmed the flash. Andrew

Didn't find any problems... C:\Windows\system32>chkdsk f: /R The type of the file system is FAT32. Volume UNRAID created 27/12/2011 1:08 PM Volume Serial Number is EA98-B4CA Windows is verifying files and folders... File and folder verification is complete. Windows is verifying free space... Free space verification is complete. Windows has checked the file system and found no problems. 1,004,789,760 bytes total disk space. 16,384 bytes in 1 hidden files. 4,096 bytes in 1 folders. 76,587,008 bytes in 15 files. 928,178,176 bytes available on disk. 4,096 bytes in each allocation unit. 245,310 total allocation units on disk. 226,606 allocation units available on disk. C:\Windows\system32>

A quick update. I've purchased a Plus license, and it's not activating properly. As per the instructions, I shutdown the server, plug the flash into my desktop, copy the Plus.key file into the /config directory, and then boot the server. The flash still shows as unregistered, and the /boot/config directory is empty. I imagine this is another symptom of the same problem described above, so now I'm even MORE anxious to resolve it Andrew

Brand new install here, running 5.0b14. The problem I'm having is that the web interface isn't starting when I reboot the unRAID machine. If I login via Telnet and start the process, it seems to run just fine though. For example: Tower login: root Linux 3.1.1-unRAID. root@Tower:~# ps -ef | grep emhttp root 1174 1160 0 18:01 pts/0 00:00:00 grep emhttp root@Tower:~# cd /usr/local/sbin root@Tower:/usr/local/sbin# nohup emhttp & [1] 1175 root@Tower:/usr/local/sbin# nohup: ignoring input and appending output to `nohup.out' ps -ef | grep emhttp root 1175 1160 0 18:02 pts/0 00:00:00 emhttp root 1212 1160 0 18:02 pts/0 00:00:00 grep emhttp root@Tower:/usr/local/sbin# Attached is my syslog. I notice many messages in there about "flash device not mounted" and "Error reading /boot/config/super.dat". Could this be a problem with by flash drive? Could it be an installation problem? Any suggestions would be greatly appreciated. Andrew syslog.txt