February 28, 200719 yr I followed the instructions VERY carefully but my system will not boot from the new Cruzer USB2 Key.. Here's step by step what I read & did.... Pre-3.0 Upgrade Instructions Step 1 - Request a registration key from Lime Technology Done & received... Obtain a new Flash and plug it into your running unRAID server; I bought a 512MB Sandisk Cruzer...and Plugged it in... ...then use telnet to open a command window and type the following command: cat /proc/scsi/usb-storage-1/1 Done! The output of the comand should look something like this: Host scsi1: usb-storage Vendor: SanDisk Corporation Product: Cruzer Micro Serial Number: 20051739920A3B20EB5A Protocol: Transparent SCSI Transport: Bulk GUID: 078151511739920a3b20eb5a Attached: Yes It did indeed look something like that Copy this text into an email and send it to Lime Technology support and we will send you a registration key for your new Flash. I emailed the info to support and today got a licence key back... Step 2 - Set up your new Flash After receiving your registration key, follow the instructions for unRAID Server Basic to make your new Flash bootable with the unRAID Server software installed. OK, so now we're off to a different document to find out how to make a new bootable key with the unraid server software on it...... Preparation unRAID Server must be installed on a 128MB or larger USB Flash Storage device. Use a good quality Flash such as: * Lexar Firefly * SanDisk Cruzer Micro * Sony Micro Vault Tiny (and they mean tiny) Be sure to review the Hardware Compatibility page when designing your server. That's fine, I read this before buying... We're OK here.... Note: If you are upgrading from a pre-3.0 release of unRAID Server' date=' please read this first.[/quote'] That's the document that just sent us here...OK, right let's continue & make this key... Instructions Step 1 Plug the Flash into your PC and delete all the existing files and directories on it, or re-format it using Windows (FAT or FAT32, Quick Format is fine). OK, Done! Step 2 Download the syslinux tool to a simple directory, for example, c:\, and then run it by clicking on Start/Run. In the dialog box enter: c:\syslinux.exe f: (Instead of c:\ use whatever directory you downloaded syslinux to, and instead of f: use whatever drive letter Windows mounted your Flash on). The syslinx tool will create a hidden file named ldlinux.sys on the Flash and make it bootable. The complete distribution of syslinux is available here. OK, Done, in my case the USB key was on g: Step 3 Download unRAID Server and extract the files from the zip archive to your Flash. OK, I downloded the 3.0 Final version for now as a safe bet. Step 4Click on the Safely Remove Hardware tool tray icon and select your Flash to be safely removed. Done..... Now back to the "Upgrade Instructions"... Copy the registration key file to the config directory of the Flash. OK, so I plug back in the Cruzer I was just told to remove.... pro.key copied to the config directory on the Cruzer USB Key.... Step 3 - Capture your current configuration Use telnet to open a command window on your currently running unRAID server and type the following command: dd if=/dev/sda2 of=/boot/super.dat bs=4096 count=1 This will create a file named super.dat that contains your current array configuration. Done, came up with an "In" & an "out" Message, but no apparent problems... Next, close the telnet window and navigate to the flash share and copy the following three files to the config directory of your new Flash: * super.dat * ident.cfg * network.cfg Note: the model.cfg file is no longer used, and you should use the disk.cfg file which comes with the new release. Found the files & duly copied them to the config folder on the new Cruzer USB key... Step 5 - Boot the new Flash Power down your server, and then boot back up using the new Flash. OK will do.. Note: the default disk.cfg file included with the unRAID Server download is fine for all IDE-based servers. If you are currently running a SATA or mixed SATA/IDE system, please refer to the Documentation for more instructions. I'm all IDE so nothing to do but reboot. I stop the array from a web browser, switch off, replace the old Unraid Key with the new Cruzer key and......... NOTHING! I get the drives being detected but as soon as the cruzer should boot, just a flashing Cruzer drive. It's not flashing in an erratic "Loading" fashion, just a slow even blinking..... any one have an idea what's wrong? If you've got this far... thank you for reading Mark.
February 28, 200719 yr I your running unRAID server; Step 2 Download the syslinux tool to a simple directory, for example, c:\, and then run it by clicking on Start/Run. In the dialog box enter: c:\syslinux.exe f: (Instead of c:\ use whatever directory you downloaded syslinux to, and instead of f: use whatever drive letter Windows mounted your Flash on). The syslinx tool will create a hidden file named ldlinux.sys on the Flash and make it bootable. The complete distribution of syslinux is available here. OK, Done, in my case the USB key was on g: Where did you execute the syslinux file from? Other than that try pinging the server after you boot it up. Go to run type in 'CMD' and then type in ping xxx.xxx.xxx.xxx. Are you using a manual ip address or letting your router assign it one? If the latter log on to your router to find the ip address. Try typing the ip address into the address bar of your browser instead of the servers name. If you plug your usb key into your windows machine you can check to see if the ldlinux.sys file is present. Just make sure under Tools>Folder Options>View that the Hide protected operating system files is unchecked.
February 28, 200719 yr Author Hi Erik, well done for reading my Loooong post. I felt it important to demonstrate that I took great care in getting this right, I didn't just take a quick stab at how to do it, I followed the instructions carefully. Where did you execute the syslinux file from? I downloaded the syslinux tool, copied it to the d:\ directory on my PC (D: is a 2nd HDD, not the CD/DVD Drive). The Cruzer was plugged into my PC and was allocated "G:" by Windows XP. My Precise command lines were... cd d:\ syslinux g: Other than that try pinging the server after you boot it up. It doesn't boot up... It does all the pre-operating-system bits, drive detection etc. but the UnRaid stuff just never loads. Go to run type in 'CMD' and then type in ping xxx.xxx.xxx.xxx. Are you using a manual ip address or letting your router assign it one? If the latter log on to your router to find the ip address. Try typing the ip address into the address bar of your browser instead of the servers name. My IP is fixed, I tried pinging & using the web browser. If you plug your usb key into your windows machine you can check to see if the ldlinux.sys file is present. Just make sure under Tools>Folder Options>View that the Hide protected operating system files is unchecked. ldlinux.sys is present on the USB key and reported as being 10kb in Windows. I don't know what's wrong... The system still boots just fine from the old USB key (v2.06 of UnRaid) so it's not a bios corruption. Can anyone shed any light on it. Many thanks, Mark.
February 28, 200719 yr The only step you might have not preformed is to go into your bios and choose your NEW usb drive as the boot device. In other words, your old USB drive was chosen as the boot device. When it is unplugged, and your new flash drive put in its place odds are the boot device is now defaulted to one of your hard disks. So... press F2 (or whatever key gets you into your bios when booting) and then try selecting the NEW USB drive (via its serial number) as your boot device. Save the bios config and see if it then boots. I had the same exact issue and every time I switched flash drives when trying to get my flash drive bootable I has to reset the boot device in the bios. Joe L.
February 28, 200719 yr Author Hi Joe, Thanks for your input.... The only step you might have not preformed is to go into your bios and choose your NEW usb drive as the boot device. In other words, your old USB drive was chosen as the boot device. When it is unplugged, and your new flash drive put in its place odds are the boot device is now defaulted to one of your hard disks. You are correct that I hadn't done this step, however having now done it it make no difference, it still will not boot. I've also tried changing some other settings, telling the Bios to boot from USB-DISK, USB-ZIP, etc. as well as disabling all USB boot devices and relying on the specific named device in the boot order. The Unraid continues to boot from the original key when I use that, but this new Cruzer just will not boot. I tried using different USB ports, I also reformatted the Cruzer again, this time as Fat32 (I used FAT last time), and when through the whole upgrade procedure again. I'm at a loss to see why it won't book. I'm wondering whther there's something specific about the Cruzer I bought? It's called a Cruiser Crossfire 512MB. I hadn't appreciated that there was more than 1 type of Cruzer but could it be specific to this model? I really hope not. I've been considering copying everything off my old key & trying that, but that really is a "no return to v2.06" strategy so I can't risk it. Thanks, Mark.
February 28, 200719 yr Don't mess up your old USB drive... Instead, use the HP formatting tool to format your new drive. Then when you get to the syslinux command, try syslinux -sam g: instead of just plain "syslinux g:" That might just get you up and running. You can read my series of steps I faces when using a 1 Gig Sandisk drive on my unRaid server. I ended up having to set the cylinders/heads/sectors using the linux version of fdisk using advanced mode. I also had to use the other options to syslinux as I had described to write the master boot record. Here is the thread I created a few months ago... http://lime-technology.com/forum/index.php?topic=359.0 Joe L.
March 1, 200719 yr I'll consider myself lucky then both new usb drives worked from the start and I have the standard hardware config. It must be specific to certain flash drives that cause problems. FWIW I have a Kingston Data Traveler 2.0 512MB thats new and an older Lexar Jump drive 256
March 1, 200719 yr Author I tried Joe's syslinux -sam but still no luck... I went back & re-read and hadn't picked up on the HP USB Boot utility... I downloaded & ran that, then when through the careful procedure listed above again and...... It boots! Yeah! However..... No drives seem allocated to the array, so I stop the array and assign each one in device list order and parity is now recalculating.. It appears that the drives are now in a different order, but that's fine.. everything will hopefully be "standard" from now on (I hope!) Thanks for the help. Mark.
March 1, 200719 yr Author I just went to check the parity rebuild progress, mainly to make sure that the drives weren't getting too hot and I can't get the web interface to start up. If I telnet to the box I can list the contents drives 2 to 11 but when I check /mnt/disk1 the cursor just sits there. I tried logging in on the UnRaid server it'sself and I get the sam... the cursor just sits there. I'm getting worried that 1 & Parity may have been the wrong way round and the rebuild is building parity on my old Disk1. I hope not I need some urgent advice......Should I reboot? or wait another 800 minutes or so (how long it last reported until parity is rebuilt and see if the web interface comes back online. [EDIT]If I need to stop UnRaid I'll have to do it via Telnet Command Line...Is that OK? Thanks, Mark.
March 1, 200719 yr I just went to check the parity rebuild progress, mainly to make sure that the drives weren't getting too hot and I can't get the web interface to start up. If I telnet to the box I can list the contents drives 2 to 11 but when I check /mnt/disk1 the cursor just sits there. I tried logging in on the UnRaid server it'sself and I get the sam... the cursor just sits there. I'm getting worried that 1 & Parity may have been the wrong way round and the rebuild is building parity on my old Disk1. I hope not I need some urgent advice......Should I reboot? or wait another 800 minutes or so (how long it last reported until parity is rebuilt and see if the web interface comes back online. [EDIT]If I need to stop UnRaid I'll have to do it via Telnet Command Line...Is that OK? Thanks, Mark. If you assigned the wrong drives as parity / disk1 not sure of the best approach, but one thing for sure don't interrupt it in the middle... at least not at this point. The following is all theoretical... I've never done this, but if you think you lost all of disk1 already, there is not too much to lose by trying. DO THIS AT YOUR OWN RISK... OR AT LEAST WAIT FOR INSTRUCTIONS FROM TOM. I am assuming you assigned the drives and then started the array. (but did apparently did not put them back in the same respective roles) unRaid thought the parity needed re-calculating, and started to re-calculate it. LET IT FINISH!!! DO NOT STOP IT!!! Now... you will need to verify this with Tom if you did get the two drives reversed, but... Tom has said he uses EVEN parity. So... I'm thinking that the re-build process does not look at the file systems on the drives at all, but treats them as just a stream of bits. Lets say the first bit on each of your data drives before you mixed them up is as follows: (disk1 through disk10) 0 1 1 1 0 1 0 0 0 1 The equivalent bit on the parity drive would then be a "1" to make an even number of "1"s. Ok... now... you accidentally swapped disk1 with the parity drive. So now, the first bit on each of your data drives is as follows: 1 1 1 1 0 1 0 0 0 1 <- note the first drive now has the bit value that was on the parity drive before you swapped them... If unRaid now calculates parity you would end up with a "0" written to the parity drive for that bit position. Hey... that is the same bit value that used to be on the disk1 data drive in that position.... I'm thinking that if you let the parity process finish you might find your parity rebuild process will have re-created an image of disk1 on the parity drive. So... since things are already well under way let the parity re-build finish. DO NOT WRITE ANYTHING TO THE ARRAY WHILE DOING THIS, OR AFTER, UNTIL YOU GET THINGS BACK THE WAY YOU WANT Once the parity re-build is finished, STOP THE ARRAY. If you cannot get to the web-based-page, type the following once all the lights on the disk drives stop flashing... (Log in via telnet) Then type: flush stop Power down and then UNPLUG both disk1 and the parity DRIVE. (That way they will NOT get overwritten) Power up. The array will not start... Go to the disk assignment page and un-assign the parity drive. (In other words, you will be bringing up the array without a parity drive. At the same time, if disk1 is still assigned, un-assign it too. Power down. Plug disk1 back in. Leave the parity drive unplugged. (Don't want the unRaid to attempt to write to it yet) Power up once more and start the Array with no parity drive assignned. (and the real parity drive unplugged) Assign disk1 as its proper role as a data drive. Re-start the array. With any luck, your disk1 contents will be back. If so, shut down, power down, plug the real parity drive back in Power up. Stop the array, assign the real parity drive its role as parity. Start the array once more and wait while it re-calculates parity. Now... As I said, this is entirely un-tested by me. YOU ARE AT YOUR OWN RISK. YOU COULD MAKE THINGS WORSE. THIS PROCESS WILL NOT WORK IF YOU HAVE WRITTEN TO ANY DRIVE WITH THE DRIVE ROLES SWAPPED. Joe L.
March 1, 200719 yr Author Hi Joe, Wow! Thanks for that. Having thought a bit more it is unlikely that I got the disks (parity & disk1) the wrong way round, when I look at where the other disks are now it's more likely that the parity recalculation is simply because of drive allocation. Remember I haven't re-cabled anything, simply upgraded to version 3 of UnRaid.. Disks Parity through 3 are on the motherboard IDE controllers, Disk2 is still Disk2 and Disk3 is still Disk3 so it's unlikely that Parity & Disk1 are now the wrong way around I must have got the 2 IDE controller cards the wrong way around when I originally built my server.. Here is the rest of the drive position changes... 4 is now 8 5 is now 9 6 is now 10 7 is now 11 8 is now 4 9 is now 5 10 is now 6 11 is now 7 All drives appeared to be populated, I could see the space left on each volume and the parity rebuild appeared to be progressing just fine on all 11 data disks. I'm not sure why the web interface & access to disk1 seems to have stopped though. Other than the drive lights on the front of the server I have no way of knowing when the rebuild is complete. I'm wondering whether the problem with disk1 is what is holding up the Web interface? If I end up losing the data on Disk1 it won't be the end of the world, I use that one for backups of other PCs around the house so as long as they don't decide to go wrong in the next day or so I should be OK. It is most likely that Parity will need to be rebuilt again due to what appears to be a lack of access to Disk1. and I'm wondering whether to abandon this attempt to rebuild parity and start again? If you concur that this would probably be the best course of action what would be the safest command line method, bearing in mind parity is clearly rebuilding at present? I have no problem waiting for this parity rebuild to finish, but the consequences of losing the data on Disk1 isn't as severe as it may have been had some of the other disks been affected Thanks so much, you've gone way beyond what I could have hoped for already in terms of your help. Mark.
March 1, 200719 yr Mark, I would wait for the current parity calc to complete... (somewhere about 800 minutes or so from when you started and when all the disk lights stop flashing.) As I said, it you did manage to swap the drives roles you might be able to recover. Let the parity re-calc finish. DO NOT WRITE ANYTHING TO ANY DISK IN THE ARRAY!! Log in via telnet and type: sync stop wait a bit then powerdown Unplug the two disks you think you got swapped. Power up and un-assign those two drives in the array. Re-start it without a parity drive. Stop it (cleanly this time, hopefully) Plug back in the original disk1 data drive. (the one that temporally was assigned as a parity role) and power up. Once up, you will probably be able to assign it as data disk1. If unRaid asks if you want to re-format it... STOP... do not. My idea did not work as expected. You will need to re-group otherwise. If disk1 is /dev/hdb1 then you might be able to type fdisk -l /dev/hdb and see if it is partitioned. As I said, it might just be re-building it now as you watch the lights blink on the drives... Are your parity drive and disk1 the same size? (About the only way I can figure you could swap them and still get things to work) Joe L.
March 1, 200719 yr Author Are your parity drive and disk1 the same size? (About the only way I can figure you could swap them and still get things to work)That solves it! Definitely not the wrong way around... Parity drive is bigger than Disk1..Of course! I should have realised that. OK, so I'll wait until tomorrow to make sure the parity rebuild has finished then follow your instructions to reboot. It's a relief, I know I haven't lost any critical data, Thanks once again.... Mark.
March 1, 200719 yr do a tail -f /var/log/syslog i think when rebuilding parity that it outputs a %complete line every so often.. that may have been for some other operation but i remember seeing something like that.. even if the %complete lines aren't for parity rebuild you should get some message output when it completes.
March 1, 200719 yr Author do a tail -f /var/log/syslog i think when rebuilding parity that it outputs a %complete line every so often.. that may have been for some other operation but i remember seeing something like that.. even if the %complete lines aren't for parity rebuild you should get some message output when it completes. I ran this at 20:26 Local time.... Hal login: root Linux 2.4.33. root@Hal:~# [b]tail -f /var/log/syslog[/b] Mar 2 12:14:34 Hal last message repeated 7 times Mar 2 12:15:44 Hal last message repeated 7 times Mar 2 12:16:54 Hal last message repeated 7 times Mar 2 12:18:04 Hal last message repeated 7 times Mar 2 12:19:14 Hal last message repeated 7 times Mar 2 12:20:24 Hal last message repeated 7 times Mar 2 12:21:34 Hal last message repeated 7 times Mar 2 12:22:44 Hal last message repeated 7 times Mar 2 12:23:54 Hal last message repeated 7 times Mar 2 12:25:04 Hal last message repeated 7 times Doesn't look right does it? Mark.
Archived
This topic is now archived and is closed to further replies.