December 20, 201213 yr Author In process of checking now. It should be v5.0 rc8a which I downloaded from the link twice. Both times I have noticed in the syslog emhttp: unRAID System Management Utility version 4.7.
December 20, 201213 yr In process of checking now. It should be v5.0 rc8a which I downloaded from the link twice. Both times I have noticed in the syslog emhttp: unRAID System Management Utility version 4.7. Well, you did not upgrade then. You best describe exactly what you did with the file you downloaded. It has nothing directly with how your system is misbehaving, but a corrupted download or incorrect install can result in all kinds of things I've not thought of. Joe L.
December 20, 201213 yr Author Here are the last few lines of code for the 5.0 rc8a download from the following link: http://lime-technology.com/download/cat_view/49-unraid-server. Before I extrect 5.0 files I format my USB. Then I select file unRAID Server version 5.0-rc8a AiO Then copy bzimage and bzroot to the USB fob. Double check that I removed config/passwd, config/shadow, and config/smbpasswd MAC address = 00:25:22:e0:20:a2 Dec 20 20:04:36 Tower ifplugd(eth0)[1276]: client: dhcpcd: your IP address = 192.168.1.2 Dec 20 20:04:36 Tower ifplugd(eth0)[1276]: client: dhcpcd: MAC address = 00:25:22:e0:20:a2 Dec 20 20:04:36 Tower ifplugd(eth0)[1276]: client: dhcpcd: your IP address = 192.168.1.2 Dec 20 20:04:36 Tower ifplugd(eth0)[1276]: Program executed successfully. Dec 20 20:04:36 Tower rpc.statd[1322]: Version 1.1.4 Starting Dec 20 20:04:36 Tower emhttp: unRAID System Management Utility version 4.7 Dec 20 20:04:36 Tower emhttp: Copyright © 2005-2011, Lime Technology, LLC Dec 20 20:04:36 Tower emhttp: Basic key detected, GUID: Dec 20 20:04:36 Tower emhttp: shcmd (1): udevadm settle Dec 20 20:04:36 Tower emhttp: shcmd (2): mkdir /boot/config/shares Dec 20 20:04:36 Tower emhttp: Device inventory: Dec 20 20:04:36 Tower emhttp: pci-0000:00:11.0-scsi-0:0:0:0 host1 (sda) ST31500341AS_9VS2G5GP Dec 20 20:04:36 Tower emhttp: pci-0000:00:11.0-scsi-1:0:0:0 host2 (sdb) SAMSUNG_HD103SJ_S246J9KBA03078 Dec 20 20:04:36 Tower emhttp: pci-0000:00:11.0-scsi-2:0:0:0 host3 (sdc) WDC_WD10EADS-00M2B0_WD-WCAV5P830128 Dec 20 20:04:36 Tower emhttp: shcmd (3): modprobe -rw md-mod 2>&1 | logger Dec 20 20:04:36 Tower emhttp: shcmd (4): modprobe md-mod super=/boot/config/super.dat slots=0,0,0,0,0,0 2>&1 | logger Dec 20 20:04:36 Tower kernel: xor: automatically using best checksumming function: pIII_sse Dec 20 20:04:36 Tower kernel: pIII_sse : 11414.800 MB/sec Dec 20 20:04:36 Tower kernel: xor: using function: pIII_sse (11414.800 MB/sec) Dec 20 20:05:01 Tower login[1365]: ROOT LOGIN on `tty1' I noticed the line references Dec 20 20:04:36 Tower emhttp: unRAID System Management Utility version 4.7
December 20, 201213 yr Author I assume you mean bzroot and bzimage files. Does it matter that my bzroot and bzimage are much smaller in size.
December 20, 201213 yr Here are the last few lines of code for the 5.0 rc8a download from the following link: http://lime-technology.com/download/cat_view/49-unraid-server. Before I extrect 5.0 files I format my USB. Then I select file unRAID Server version 5.0-rc8a AiO Then copy bzimage and bzroot to the USB fob. Double check that I removed config/passwd, config/shadow, and config/smbpasswd MAC address = 00:25:22:e0:20:a2 Dec 20 20:04:36 Tower ifplugd(eth0)[1276]: client: dhcpcd: your IP address = 192.168.1.2 Dec 20 20:04:36 Tower ifplugd(eth0)[1276]: client: dhcpcd: MAC address = 00:25:22:e0:20:a2 Dec 20 20:04:36 Tower ifplugd(eth0)[1276]: client: dhcpcd: your IP address = 192.168.1.2 Dec 20 20:04:36 Tower ifplugd(eth0)[1276]: Program executed successfully. Dec 20 20:04:36 Tower rpc.statd[1322]: Version 1.1.4 Starting Dec 20 20:04:36 Tower emhttp: unRAID System Management Utility version 4.7 Dec 20 20:04:36 Tower emhttp: Copyright © 2005-2011, Lime Technology, LLC Dec 20 20:04:36 Tower emhttp: Basic key detected, GUID: Dec 20 20:04:36 Tower emhttp: shcmd (1): udevadm settle Dec 20 20:04:36 Tower emhttp: shcmd (2): mkdir /boot/config/shares Dec 20 20:04:36 Tower emhttp: Device inventory: Dec 20 20:04:36 Tower emhttp: pci-0000:00:11.0-scsi-0:0:0:0 host1 (sda) ST31500341AS_9VS2G5GP Dec 20 20:04:36 Tower emhttp: pci-0000:00:11.0-scsi-1:0:0:0 host2 (sdb) SAMSUNG_HD103SJ_S246J9KBA03078 Dec 20 20:04:36 Tower emhttp: pci-0000:00:11.0-scsi-2:0:0:0 host3 (sdc) WDC_WD10EADS-00M2B0_WD-WCAV5P830128 Dec 20 20:04:36 Tower emhttp: shcmd (3): modprobe -rw md-mod 2>&1 | logger Dec 20 20:04:36 Tower emhttp: shcmd (4): modprobe md-mod super=/boot/config/super.dat slots=0,0,0,0,0,0 2>&1 | logger Dec 20 20:04:36 Tower kernel: xor: automatically using best checksumming function: pIII_sse Dec 20 20:04:36 Tower kernel: pIII_sse : 11414.800 MB/sec Dec 20 20:04:36 Tower kernel: xor: using function: pIII_sse (11414.800 MB/sec) Dec 20 20:05:01 Tower login[1365]: ROOT LOGIN on `tty1' I noticed the line references Dec 20 20:04:36 Tower emhttp: unRAID System Management Utility version 4.7 I think that might be the answer... You formatted the flash drive and then only copied bzimage and bzroot to it? And yes, the bzimage and root from 4.7 are there, and it appears as if the config folder might not be? Or is it? Type ls -la /boot and ls -la /boot/config and post the output.
December 21, 201213 yr Author Looks like I made a mistake and copied the files wrong. Ok, I have download 5.0 rc8a and copied bzroot and bzimage from the zip file to my existing 4.7 settings located on the USB. Removed passwd and smb password from the USB config folder. The build was going well until I received a "waiting on USB subsystem error." This issues seems to be a continues loop error and I am unable to sign in with root with 5.0 rc8a to pull a syslog.
December 21, 201213 yr Author If I receive a USB Subsystem error after 1/2 Unraid system was loaded. Is this error due to the USB failed? Would it need to be replaced?
December 21, 201213 yr You may need run the new make-bootable because the version of syslinux has changed. This should only effect users with very old installations. On a PC, insert the flash and copy make_bootable.bat and syslinux.exe from the new distribution to the flash run Make_bootable.bat as Administrator. If this does not work then try a clean install.
December 21, 201213 yr Author Ok, just to make sure I have this correct. I need to copy from the 5.0 rc8a zip file the following files to the USB that currently has version 4.7: bzroot, bzimage, Make_bootable.bat, and syslinux Then run the Make_bootable.bat file. After that is complete install the USB back into the UnRaid server and boot up.
December 21, 201213 yr Ok, just to make sure I have this correct. I need to copy from the 5.0 rc8a zip file the following files to the USB that currently has version 4.7: bzroot, bzimage, Make_bootable.bat, and syslinux Then run the Make_bootable.bat file. After that is complete install the USB back into the UnRaid server and boot up. Follow the steps on the wiki for upgrading from 4.7 to 5: http://lime-technology.com/wiki/index.php/UnRAID_Server_Version_5.0-beta_Release_Notes
December 21, 201213 yr Author Followed the directions from the link listed below for upgrading v4.7. However I received "waiting on USB subsystem error." Never have the ability to set a tail syslog or pull a system log. I attempt to take a snapshot
December 21, 201213 yr Try copying syslinux and make_bootable from the new distribution to the flash and then run make_bootable as Administrator. This will do no harm.
December 22, 201213 yr Author This frustating.... I am back to version 4.7 Asrock 880 ge-le 8 GB Memory This is a new USB and a clean version of 4.7 with no add-ons Executed telent 192.168.1.3 80 root@Tower:~# telnet 192.168.1.2 80 Trying 192.168.1.2... telnet: connect to address 192.168.1.2: Connection refused telnet: Unable to connect to remote host: Connection refused Executed /root/mdcmd status | strings | grep -i Sta received a result /root/mdcmd: Line 11: /proc/mdcmd: No such File Then executed ps -e|grep emhttp received 1365 ? 00:00:00 emhttp then re-booted. Re-ran the above command and still received no such file. I have added my IP address to the host file. syslog.txt
December 22, 201213 yr The correct address is 192.168.1.3 root@Tower:~# telnet 192.168.1.2 80 Trying 192.168.1.2... telnet: connect to address 192.168.1.2: Connection refused telnet: Unable to connect to remote host: Connection refused 192.168.1.2 is incorrect.
December 22, 201213 yr Dec 22 02:49:42 Tower login[1366]: ROOT LOGIN on `tty1' Dec 22 03:03:08 Tower shutdown[1410]: shutting down for system reboot Dec 22 03:03:08 Tower init: Switching to runlevel: 1 Why is the system shutting down after you login?
Archived
This topic is now archived and is closed to further replies.