thequinox

Members
  • Posts

    16
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

thequinox's Achievements

Noob

Noob (1/14)

0

Reputation

  1. In the disk properties, one was set to RiserFS and one was set to XFS, as expected. I switched the RiserFS to XFS, and the XFS to RiserFS, and that did the trick. So somehow they were just mixed up. I'm starting the rebuild to the 2TB now. Thanks a lot guys!
  2. Sorry for the late reply. I have procured another 2TB drive and attempted the instructions you linked to, but ran into a problem. The new drive shows as unmountable, as expected, but so do two of my other good drives. The 2TB assigned currently as Disk 5 is the one I am using to replace the failed drive, but I haven't had any problems with mounting the other 3TB drives in the past. If I recall correctly one of the 3TBs was XFS, if that makes any difference. The slots they're assigned to don't matter as long as the correct parity disk is selected, correct? fileserver-diagnostics-20160520-1714.zip
  3. Thanks for the link Johnnie. I did a search before posting but I didn't come across that one. It's almost exactly what I'm facing so thank you for getting me the link. It's interesting that his super.dat failed as well. Is that a known bug with unRAID 6? I'll have to do some searching. Lastly, does the new drive have to be the exact same size as the failed disk? I have a brand new 4TB sitting here ready to go in, wouldn't the rebuild procedure be basically the same as the expansion procedure? Thanks again.
  4. I looked at my last backup, but unfortunately I've added another drive since then, so I don't think it will be of any use. I have attached the requested diagnostic file. I think I just need to tell unraid that the parity is valid, then the rebuild will proceed as if there was a normal disk failure. Just not sure the right way to go about that. fileserver-diagnostics-20160514-2116.zip
  5. Bump for visibility. Hoping someone knows the correct course of action?
  6. My house lost power and the system was improperly shut down. Usually when this happens I just have to do a parity check when starting the array back up. I had a UPS but it died, probably time to get a new one. Anyway, this time upon boot all my drives were unassigned. I did some searching on the forum, ran a checkdisk on my flash drive, it's fine. The .dat file used to house the assigned drives however was 0 bytes. I deleted the file and went to start assigning the drives back, but noticed I was missing one. Looked at the syslog and found that one drive was failing to respond. It detected something was there, but first tried 3Gbps, then 1.5Gbps, then it timed out. So looks like I lost a drive in the power failure as well. Now, I have an extra drive I can put in. I slid it in and it was detected no problem, however because it was an improper shut down my parity isn't trusted. I know the fileserver wasn't doing anything at the time because it was in the middle of the day and no one was home, so I personally think the parity is fine. Do I put in the new drive, and just hit rebuild? I'm worried that if I do that the parity drive may be overwritten with the blank drive instead of the other way around. What are the correct steps to go through to prevent any data loss? Thanks guys. Update: I was able to borrow a 2TB drive, rebuild with it, and then expand with my spare 4TB. The server is now up and running. Many thanks to johnnie.black and RobJ!
  7. I would like to know if there's a way to set my user shares to read-only for everyone. I know you can do it if you set user level permissions, but in my house I don't use credentials to access my shares, they're just open. I've done some searching and it looks like back in version 4 you could set the export option to "Export Read-Only", however I didn't have that option in v5, and I just upgraded to v6.1 and don't see it either. My array is almost full and I'd like to pull the parity drive and put in a bigger one to get ready to expand. However, I would like to set the array to read only during this so if there was another disk failure I could put the old parity drive back in and it would still be valid. I don't plan on using it much during the parity check, but they can take a while and I'd like to be able to grab some files if need be. Does anyone know how to do this, or if there is a much more elegant solution to what I want? Thanks,
  8. Transaction went through and the Plus key is up and running.
  9. I already ordered a key with the above GUID. I figure if it isn't right then the transaction won't go through. In such an event I'll just have to dig up another drive.
  10. I figured it probably worked like that. Thanks for the information. I guess I will just buy a pro license with this GUID and see if it works or not. Worst comes to worst I buy a new flash drive. I'll post back the results.
  11. I have two quick questions that I couldn't find answered in the wikis, thought maybe a senior member could share a minute and clarify this for me. First off, I have a Kingston DataTraveler in my server with the GUID of 0951-1603-0000-0000000000AF. Now I need to buy a license but it says the last twelve didgets should not be zeros. There is an "AF" on the end of mine so it's not "all" zeros, but it doesn't look like much of a serial number to me. Is this ok? Secondly, where does unRAID store it's system data? If this flash drive dies, how would I get the server back up? If I put a new flash drive in wouldn't it be missing all the data on my array? Would I have to tell it which drive is which again? I was under the impression that no unRAID data was on the HDDs so it must be on the USB drive. Should I be backing it up? Thanks
  12. Thanks Mopar_Mudder I was actually able to get it working though! I was fiddling with PLoP before but I couldn't get it to work. It would just hang while booting up. I tried a different floppy and VOILA! Now I remember why I hated these things so much Anyway, I was able to make a kicker disk just fine with that. It was pretty straight forward, but for anyone who wants to do it again, here is what I did: ---- Step 1. Download PLoP and extract the .zip Step 2. Download "rawwritewin" as reccomended on the PLoP website and use it to write "plpbt.img" to a floppy. Step 3. Run plpcfgbt.exe in the command line with the arguments "plpcfgbt stm=hidden cnt=on cntval=1 dbt=usb plpbt.bin". This will change the settings in plbt.bin to boot straight to usb instead of bringing up the main menu. Step 4. Copy the newly edited version of plpbt.bin to your floppy. Replace the existing one. ---- That's pretty much all I did. Very straight forward and it works great! I would give your floppy a test right after step 2 though, just to make sure PLoP loads correctly before you start messing with it. Now, to try and figure out UnRAID and move my stuff onto the new server. Wish me luck
  13. Does anyone have a newer link to the kicker files that keep being referenced? I am trying to get an old P4 up and running but that website seems to be down. If someone could point me to another mirror, or if someone who has them already could host them again, it would be greatly appreciated to me and all others wanting to do this in the future. Thank you
  14. Looks like that is a PCIe chip. I only have PCI at my disposal on this box, hence the original question of whether one or two cheap cards would give better performance. There is also this guy http://www.ncix.com/products/index.php?sku=28106K (SiL 3124) It claims to be SATA II, but is it worth the increase in price? Can PCI even deliver close to SATA II speeds? 1) One card or two 2) SATA or SATAII on PCI 3) Reliability? I don't expect the world from these cheap cards, but if anyone has any experience with them I would love to hear it. Ideas?