Jump to content

smakovits

Members
  • Posts

    881
  • Joined

  • Last visited

Everything posted by smakovits

  1. I was curious if a script existed for when a person adds new drives, the script goes through and redistributes all the existing data to level capacity across all drives. Typically I will do this manually cutting and pasting data, but I was just curious if there was a script out there that can automate the process.
  2. OK, maybe I will try to add the cache disk back in then and test add-on removal. I just figured because things worked when the cache was removed that surely it was an issue with the disk.
  3. I had the same issue. Toggle auto start to no, apply, then yes and apply and test. For whatever reason yes might not me yes and it needs reset. At least in my case it did
  4. Last night I went to restart my unRaid 5 RC3 box and when I woke this morning is was still starting. After reading a few posts, I thought to try removing my cache drive, so I set my server to not start on boot, removed the cache drive and everything started fine. It is connected to a MV8SATA card and the cache drive used to work fine in the past, I had it removed for a bit, then added it back and it was working, till last night. The crazy thing is that in the log I can see that it "moved" files in the middle of the night, so it was partially running even though it would not "start". The drive looked OK in the last smart report, so i am not sure what it could be and I am hoping there is something more informative in the log. syslog-20120910-072014.zip
  5. so the only reason one would use s300 vs /d is because they have an EZRX drive? Just curious if it matters otherwise, I dont have an EZRX yet, just EARX, EARS and EADS
  6. In the end it appears that the likely issue is my flash got jacked and in turn it messed up my go script. Once I formatted and installed 4.7 clean and booted with my configuration, it would not boot with my go script. So I went back to the default and have to just now install everything from scratch. Heck, might be a good time to upgrade to 5. Thoughts? Seems pretty safe, no? Long story short, check disk did say it fixed something on the flash, so not sure if that was part of it or not, but the main issue in the end was a corrupt go script.
  7. I used "/s300" What's the difference? Just added 2 replacement drives because of high lcc and did 300 on them
  8. had one of these the other day, now I have two... » multi_zone_error_rate=7 » multi_zone_error_rate=2 Is this something to be concerned about. I am replacing 2 1.5TB drives because of » load_cycle_count=450308 If yes, thats 4 of 8 drives, yikes!
  9. formatted my flash drive, copied files over, ran make boot and restored all the directories that werent otherwise there. I put in the new drive that will be rebuilt and powered up Now, system boots and I can ping it, but I cannot reach the web gui. edit: poke around a bit more and found that my go script is corrupt. Curious if there is anything that can be done to recover it, if not, I start again. Other than that, I am back up and running. data is rebuilding to the new disk.
  10. just ran a quick test. Attempted to boot the flash in a random computer and things fail in the same spot. Therefore, it is assumed I need to attempt to format as a next step and got from there. Is it worth going to 5 from this point or wait till I know I am functioning again?
  11. OK, so I ran a check disk and it said it found and fixed and error, but still the same issue remains. Windows sees it and everything looks normal, so I am not sure what to think. time to format and see if I cant get everything back like that? Can I copy off all content, format prep and copy data back?
  12. OK, so if I am understanding, it could be a corrupt flash which windows might just fix. Because it starts the boot process I must assume it is not dead. Either way, even if it is recovered, should I consider replacement? In the event that windows fails at helping me and I cannot recover any data from the drive, then that is the worst case part I assume. Luckily I printed the disk config prior to starting last night, so I would be able to re-assign if needed, lets hope not. I hope to have some time late tonight. I will post my findings. Fingers crossed for a simple check disk
  13. OK, as a test before leaving the house this morning. I put back the drive I was replacing just to make sure it was nothing to do with the pre-clear being run on a v5 Unraid system. The results were the same, therefore, I am now suspecting the issue resides at my flash drive. Did the flash go bad? Did one of the files just become corrupted? Whatever the answer, is my data at risk? Where do I start in an effort to get my system back online?
  14. Been running 4.7 fine for a while now. Had the disk idle issue on some drives to my LLC or what not was over 400k, so I wanted ot be proactive and just replace the drives before they fail. I took my first drive, precleared it in another system (v5 - test system) and was ready to start re-building it when during boot I got the following: VFS: Cannot open Root device "<NULL>" or unknown block (8,1) Please append a correct "root=" boot option, here are the available partitions: Kernel Panic - Not Synching: VFS: unable to mount root fs on unknown-block (8,1) Pid: 1, comm: swapper not tainted 2.6.32.9 -unraid #8 Call Trace then there is a bunch more junk... I read on a few other posts about older versions that the issue is on the usb and the formatting. However, this was working for the longest time. Totally freaking out since I was in the middle of replacing a drive and now I dont know what to do to get the system back as well as the disk re-built? Should I replace the original drive for the time being until I get this issue resolved? I so hope it is an easy fix. Thanks! I see there are some posts that do reference 5.0 even and my test system is 5.0, but it was never added to the array or anything, strictly just ran preclear -A and thats it, didnt think it made a difference at that point. The only thing I could try is adding back the old drive but for now the system is powered off as await advice
  15. I was just curious about the changes that will happen, do things like unmenu go away and somply stop working? Do I need to remove the entry for it from my go script? How different is the plugin system in 5.0? Are the plugins still the same or is it completely different? I see things like sickbeard and couch potatoe and it just shows things are way more advanced. Just trying to figure out what I should expect with the upgrade. I use light HTTP for my a-110's so is that still around? Thanks!
  16. I guess it is a good thing then that I didnt install it yet...Just waiting on 5.0 full I guess. I also read that my mobo should be compatible, what is all that about?
  17. do you still get sustained ~90MB writes/network copies to your unraid?
  18. Can I run WDidle3 /d with all my drive connected or is it better to do one at a time, then boot, verify all systems are go, shutdown, do the next one, etc... With 8 drives one at a time could be a while. I read that all data is preserved during the process so whats the best way to go about this?
  19. OK, so I should just worry about disabling via WDIDLE and then modifying the count to a number that wont flag things. Then just monitor drive health for the future to make sure things continue to function. Just out of curiosity, how long does it take for WDIDLE to do its thing? Is it pretty quick? Would it also be recommended to do a reboot after each run to ensure that the disk is still functional and recognized by the OS?
  20. OK, I will just work to disable then... Just a note, the brand new drive I put in a week ago, 4616 LLC already... Also, what is IDLE3? Is that something else I should worry about? Thanks
  21. I am getting ready to run this on all my drives since I have some high counts, but I am debating RMA-ing all old drives...reason being, when I look at mymain and all the yellow highlights of the load counts, I dont like it. Call it OCD, but I rather it not be there. Luckily I only have 8 drives at the moment, one is new so it leaves 7. I figure RMA all with the advanced RMA, I get 7 new drives, disable and preclear each and then one at a time add them to the array and rebuild the data. It would be a 2 week process as it takes 24 hours to preclear and about the same to rebuild the data. I guess I could preclear all at once, so that would shave a few days... Any thoughts or am I just crazy and being OCD about seeing the highlighted load counts.
  22. If the drive is an AF drive and has the jumper in place, it should list as MBR unaligned right? My server is set to 4k-aligned. My non-jumpered AF formatted -A shows, MBR: 4K-aligned All others that are either not AF or AF with jumper show, MBR: unaligned This is correct, right? Thanks.
×
×
  • Create New...