October 20, 200718 yr I have been trying to get the free version to work. System boots up fine but when I type mount I just get a command prompt, and when I type ifconfig -a no ip address is listed for the intel pro network adaptor. I have read in some posts that you have to format the key to make it bootable, but the system does boot into unraid and I am able to enter root to access the commands.
October 20, 200718 yr If it boots unRAID, then your flash drive is fine. I don't know if forum attachments are working yet, but if they are, then a copy of your syslog would be helpful.
October 20, 200718 yr To obtain a copy of your current syslog, at the unRAID console or in a Telnet session, type the command: cp /var/log/syslog /boot This will make a copy of the system log in the root directory of your flash drive, which you can either copy directly from the flash share of your server, or plug the flash drive into your PC and access the syslog there. Any file manager such as Windows Explorer can access the file across the network. For example, if your unRAID server name is Tower, then you can access your newly created syslog as \\Tower\flash\syslog. I recommend renaming it with the date and time and the .txt extension, for example syslog2007-08-28-1630.txt. A helpful Wiki link: http://lime-technology.com/wiki/index.php?title=Viewing_the_System_Log
October 20, 200718 yr Author More Info that might help from the bootup. Thank you again for any assistance. Mounting non-rot local filesystems: mount: special device /dev/disk/by-label/UNRAID does not exist Using /etc/random-seed to initialixe /dev/urandom. INIT: Entering runlevel: 3 Going multiuser... Starting sysklogd daemons: /usr/sbin/syslogd -m0 /usr/sbin/klogd -c 3 -x /etc/rc.d/rc.inet1.config: line 18: /boot/config/network.cfg: No such file or directory /etc/rc.d/rc.inet1.config: line 19: /var/tmp/network.cfg: No such file or directory Welcome to Linux 2.6.22.5 (tty1) Tower login:
October 20, 200718 yr Author Hello I tried that command, but nothing gets copied to the key looks like the key did not get mounted. Thanks agian
October 20, 200718 yr Make sure that you specify the volume label of the flash drive as: UNRAID. I believe that might explain all of the problems. These installation links may help: http://www.lime-technology.com/wordpress/?page_id=46 http://lime-technology.com/wiki/index.php?title=Building_an_unRAID_Server
October 20, 200718 yr Author I made sure to lable the key correctly, I have tried UNRAID, and unRAID, not sure if it is case sensitive. Not sure what else to try, thanks again Rob.
October 20, 200718 yr Author Hello, Tried it on another KigMax usb key and I did not get any errors. Not sure what is wrong with the SanDisk key. Now the fun stuff begins, thanks again for the help. DX
October 20, 200718 yr Hello, Tried it on another KigMax usb key and I did not get any errors. Not sure what is wrong with the SanDisk key. Now the fun stuff begins, thanks again for the help. DX Many of the flash drives have "other" software pre-installed on hidden partitions. Some can only be removed by a utility suppled by the manufacturer. "U3" is one that is difficult to remove. The volume label on the flash drive must be all upper case and be set to "UNRAID" (without the quote marks) If you want, now that you are booted up on unRaid, plug your non-working SanDisk key in a different USB socket and you can then use the fdisk -l /dev/sdX command to see the partitioning. (you would need to figure out the correct drive to use the fdisk command on) on my IDE based array /dev/sda is my flash drive and /dev/sdb is the second flash drive. In any case, now that you are up and running, have fun. Joe L.
October 20, 200718 yr U3 is not difficult to remove just put it in windows machine and then you get U3 icon in the tray open it's UI and there somewhere in the menus you can remove that software from the usbstick. Pretty simple.
October 21, 200718 yr Yeah, it's so easy that there is a webpage just to help people with the process: http://www.u3.com/uninstall/ The fact is that not all of them are easy to completely uninstall (i.e. remove the partition and everything, not just disable the US software itself). Bill
June 9, 200818 yr More Info that might help from the bootup. Thank you again for any assistance. Mounting non-rot local filesystems: mount: special device /dev/disk/by-label/UNRAID does not exist Using /etc/random-seed to initialixe /dev/urandom. INIT: Entering runlevel: 3 Going multiuser... Starting sysklogd daemons: /usr/sbin/syslogd -m0 /usr/sbin/klogd -c 3 -x /etc/rc.d/rc.inet1.config: line 18: /boot/config/network.cfg: No such file or directory /etc/rc.d/rc.inet1.config: line 19: /var/tmp/network.cfg: No such file or directory Welcome to Linux 2.6.22.5 (tty1) Tower login: I am now running into this same problem after having to re-make my USB key. It was working but then the USB key went corrupt and couldn't boot out of bios. So I re-formatted and re-setup the key again and I'm getting the exact same errors as if UNRAID is missing. (YES - the KEY is formated as fat32 with a volume name of UNRAID) My system boots to the login now (instead of saying it can't find a boot device) but seeing the same message of /dev/disk/by-label/UNRAID does not exist, and the line 18 and 19 error message. Plus it not on my network. This key doesn't have any special area or other partions on it which seemed to correct this issue for someone else. It was working fine for around 1 week. Any ideas?
June 9, 200818 yr When your system encounters a boot device that doesn't work, it will sometimes remove that boot device. Go back through the bios and reset it to put the USB first and make sure it is configured properly. Bill
June 10, 200818 yr More Info that might help from the bootup. Thank you again for any assistance. Mounting non-rot local filesystems: mount: special device /dev/disk/by-label/UNRAID does not exist Using /etc/random-seed to initialixe /dev/urandom. INIT: Entering runlevel: 3 Going multiuser... Starting sysklogd daemons: /usr/sbin/syslogd -m0 /usr/sbin/klogd -c 3 -x /etc/rc.d/rc.inet1.config: line 18: /boot/config/network.cfg: No such file or directory /etc/rc.d/rc.inet1.config: line 19: /var/tmp/network.cfg: No such file or directory Welcome to Linux 2.6.22.5 (tty1) Tower login: I am now running into this same problem after having to re-make my USB key. It was working but then the USB key went corrupt and couldn't boot out of bios. So I re-formatted and re-setup the key again and I'm getting the exact same errors as if UNRAID is missing. (YES - the KEY is formated as fat32 with a volume name of UNRAID) My system boots to the login now (instead of saying it can't find a boot device) but seeing the same message of /dev/disk/by-label/UNRAID does not exist, and the line 18 and 19 error message. Plus it not on my network. This key doesn't have any special area or other partions on it which seemed to correct this issue for someone else. It was working fine for around 1 week. Any ideas? It sounds as if you are still using the original flash drive. Is this true? Or is it a second flash drive that worked for a short time, and not is not working? Despite what some may say, re-formatting and configuring a drive again and again is unlikely to help. If still the same flash drive as "originally failed" then I suggest you purchase another. At this point, they are very inexpensive. If two different Flash drives have both successfully booted, but subsequently stopped booting, then I would look elsewhere for the actual problem. (USB port on motherboard is most suspect, or interrupt conflict on motherboard, leading to eventual disable of USB port.) The volume label must be in upper case. So please verify it is set to UNRAID. (you said you tried alternatives in mixed case) Since you can get to a Linux prompt, log in as root Once logged in, type ls -l /dev/disk/by-label Let us know what the output says. also, type ls -l /dev/disk/by-id Let us know what it says: If you suspect a conflict of interrupts from your hardware, you might try to add a few boot parameters to your syslinux.cfg file on your flash drive as described in this post: http://lime-technology.com/forum/index.php?topic=1676.msg11412#msg11412 Joe L.
June 10, 200818 yr It sounds as if you are still using the original flash drive. Is this true? YES Or is it a second flash drive that worked for a short time, and not is not working? No 2nd flash, but have ordered a new one. But would like to get this going again. The volume label must be in upper case. So please verify it is set to UNRAID. (you said you tried alternatives in mixed case) It is: UNRAID original poster tried mixed case. Since you can get to a Linux prompt, log in as root Once logged in, type ls -l /dev/disk/by-label Let us know what the output says. all flagsset 1 root root 10 Jun SWAP_002 -> ../../sdd1 Note: swap_002 was an old windows volume name on 1 of the drives also, type ls -l /dev/disk/by-id Let us know what it says: List 4 lines/drive all start with flagsset 1 root root 09 Jun (then) ata-drivemodel_serialnumber -> ../../sda ata-drivemodel_serialnumber-part1 -> ../../sda1 scsi-SATA-drivemodel_serialnumber -> ../../sda scsi-SATA-drivemodel_serialnumber-part1 -> ../../sda1 repeats sda to sdi (Except for sdb) usb-Kingston_DataTraveler_2.0_guid-0:0 -> ../../sdb Looks like the usb key is sdb but without a label?
Archived
This topic is now archived and is closed to further replies.