June 1, 201016 yr Set up the trial version of unRAID on my new server yesterday, and configured it with 3 disks: one parity and two data. All three disks are 2tb in size, and the array setup went fine overnight. I copied over about 300GB of data this morning and all went well - so far so good. Received my pro.key file from Lime by email this afternoon, and carried out the following steps: 1) Stopped array using web ui 2) Power Down using web ui 3) put USB stick in my desktop machine and copied the file to the config directory 4) returned the USB stick to the unRAID server and powered up. My array now has no members? Why did the configuration go away? How can I get it back? I put in an email to support@lime-technology but decided to post here in case it's an easy fix. Thanks all.
June 1, 201016 yr Set up the trial version of unRAID on my new server yesterday, and configured it with 3 disks: one parity and two data. All three disks are 2tb in size, and the array setup went fine overnight. I copied over about 300GB of data this morning and all went well - so far so good. Received my pro.key file from Lime by email this afternoon, and carried out the following steps: 1) Stopped array using web ui 2) Power Down using web ui 3) put USB stick in my desktop machine and copied the file to the config directory 4) returned the USB stick to the unRAID server and powered up. My array now has no members? Why did the configuration go away? How can I get it back? I put in an email to support@lime-technology but decided to post here in case it's an easy fix. Thanks all. Without a syslog to analyze, we have no way to help. Perhaps you did not "safely" eject the flash drive on the PC before moving it back to the unRAID server? Going forward, the flash drive is accessible on the LAN as \\tower\flash You could have copied the pro.key file to the flash drive without removing the flash drive from the unRAID server at all. How to get a syslog for analysis is found under troubleshooting in the wiki.
June 1, 201016 yr Author I did a safe eject, and unRAID is now registered to me as a legit pro version, but the array is gone. As a side note, for some reason I was unable to browse the files on the USB key from my win7 desktop before (the share appeared empty) which is why I was shuffling the usb stick back and forth. Strangely, since the upgrade to pro I can now browse the files with no problem. Downloaded putty; syslog attached. syslog.doc
June 2, 201016 yr I did a safe eject, and unRAID is now registered to me as a legit pro version, but the array is gone. As a side note, for some reason I was unable to browse the files on the USB key from my win7 desktop before (the share appeared empty) which is why I was shuffling the usb stick back and forth. Strangely, since the upgrade to pro I can now browse the files with no problem. Downloaded putty; syslog attached. It appears as if the files on the flash drive that define the array are not there??? I'm as confused as you. Assuming the flash drive is writable, and we do not yet know, since you've not re-defined your array since booting. don't fear, your files are still there, it is just the devices are not assigned on the "Devices" page. (Or rather, it does not seem like the config/disk.cfg file is present) Before you do anything, try logging in using putty and typing cat /boot/config/disk.cfg Regardless, you'll need to use the "devices" page to assign the disks once more. They should be recognized as already formatted and be accepted with their data. Make sure to assign the parity drive to the parity position in the array. Then, issue the initconfig command, then refresh your browser. All the drives should show as blue. It should say something about it being a new array. None of the drives should show as un-formatted. Press "Start" to start the array.
June 2, 201016 yr Author I should mention one other thing that may be impacting this. This is a SanDisk MicroCruzer stick which I picked because it was on the compatibility list. It came with a hidden U3 partition I think. When I initially followed the "getting started" instructions and formatted the drive in Windows, the U3 partition was still there. When I put the stick into the desktop to copy the pro.key file, I got an autoplay notification for the U3 partition which I promptly closed, but perhaps it was somehow 'activated'? Grasping at straws here since I while my Windows knowledge is very high, I have zero experience with Linux. I'm also using Win7 for the 1st time which, as usual, works a little differently than 3.11/95/NT/2k/XP/2003/Vista. That might be why I can now see the files when I browse to Tower\flash, not sure. My theory is sketchy though, in that the unRAID server still boots successfully, so at least at some point it is seeing the volume UNRAID. I could also try imaging the key and then deleting the U3 partition to see what happens. I will also try those commands you mentioned; thanks Joe.
June 2, 201016 yr I should mention one other thing that may be impacting this. This is a SanDisk MicroCruzer stick which I picked because it was on the compatibility list. It came with a hidden U3 partition I think. When I initially followed the "getting started" instructions and formatted the drive in Windows, the U3 partition was still there. When I put the stick into the desktop to copy the pro.key file, I got an autoplay notification for the U3 partition which I promptly closed, but perhaps it was somehow 'activated'? Grasping at straws here since I while my Windows knowledge is very high, I have zero experience with Linux. I'm also using Win7 for the 1st time which, as usual, works a little differently than 3.11/95/NT/2k/XP/2003/Vista. That might be why I can now see the files when I browse to Tower\flash, not sure. My theory is sketchy though, in that the unRAID server still boots successfully, so at least at some point it is seeing the volume UNRAID. I could also try imaging the key and then deleting the U3 partition to see what happens. I will also try those commands you mentioned; thanks Joe. You MUST delete the U3 partition. Who knows what it did. There is special software needed to get rid of the U3 stuff. It is not as simple as deleting a partition. If it "autoran" something, then there were other nasties on the flash drive too. Joe L.
June 2, 201016 yr Author Probably a good thing for Lime to add to their USB stick preparation page... http://lime-technology.com/support/unraid-server-installation Nothing actually auto-ran, it was just that Win7 popped up with the usual annoying dialog box when it detects a new partition (I hadn't disabled that functionality yet, but it's off now.) I'll look into getting rid of that U3 partition and rebooting. I won't lose any data since I still have the source disk, just a little surprised that the array was missing.
June 2, 201016 yr Probably a good thing for Lime to add to their USB stick preparation page... http://lime-technology.com/support/unraid-server-installation Nothing actually auto-ran, it was just that Win7 popped up with the usual annoying dialog box when it detects a new partition (I hadn't disabled that functionality yet, but it's off now.) I'll look into getting rid of that U3 partition and rebooting. I won't lose any data since I still have the source disk, just a little surprised that the array was missing. Actually, it is mentioned here: http://lime-technology.com/wiki/index.php?title=USB_Flash_Drive_Preparation&curid=1431&diff=5130&oldid=5128 Quote: If your flash drive had pre-installed "U3" software, it will need to be removed before you format and install unRAID on it. U3 Un-Install software is available here. A U3 removal tool specific to SanDisk drives can be found here.
June 2, 201016 yr Author ha ha. So it is. I don't know, maybe it's just me, but I find the start-up process to be rather painful; especially for a $100+ piece of software. Learning how to do anything is a matter of sifting through the main Lime pages, the wiki, the official docs, the unofficial-but-up-to-date docs, the forums etc. Part of the fun I guess. Your suggestions for getting the array back online seem to have worked perfectly though. Luckily I wrote down the serial number of the parity drive so I was able to reselect it, plus the two data drives. Ran initconfig and started the array; it seems the parity volume is rebuilding now, so it's looking good. Thanks again Joe.
June 2, 201016 yr ha ha. So it is. I don't know, maybe it's just me, but I find the start-up process to be rather painful; especially for a $100+ piece of software. Learning how to do anything is a matter of sifting through the main Lime pages, the wiki, the official docs, the unofficial-but-up-to-date docs, the forums etc. Part of the fun I guess. Your suggestions for getting the array back online seem to have worked perfectly though. Luckily I wrote down the serial number of the parity drive so I was able to reselect it, plus the two data drives. Ran initconfig and started the array; it seems the parity volume is rebuilding now, so it's looking good. Thanks again Joe. Lime-technology has never permitted any users to modify their "official" pages, and they are out-of-date in many areas with respect to recent changes in the user-interface. Luckily, the un-official pages are in much better shape.
Archived
This topic is now archived and is closed to further replies.