bulkymicrowav

Members
  • Posts

    9
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

bulkymicrowav's Achievements

Noob

Noob (1/14)

0

Reputation

  1. I'm responding to this post in hopes it helps someone else. I'm a linux noob and I had the same problem as listed above without completely clear instructions for the solution. I was migrating from 5 RC10 to 5.0.5. I attempted to follow the instructions for upgrading on the link found in the changelong "http://lime-technology.com/wiki/index.php/Upgrade_Instructions". it reads: The problem is that starting on 5.0.4 they introduced the syslinux folder to zip file and the syslinux.cfg file resides in that folder. I copied over both bzimage and bzroot and the syslinux folder. I then ran the make_bootable.bat and attempted to start up my unraid server and I just got caught on an error of something along the lines of menu c32 or something. After a few other attempts even bringing 5.0RC10 back on just to check the flash drive I ended up with this: I added ".old" extenstions to menu.c32 and syslinux.cfg to the files located in the root directory of the flash drive example: "syslinux.cfg.old" Copied and over wroter bzimage, bzroot, make_bootable.bat, memtest, readme.txt, and the syslinux folder from the zip file Run the make_bootable.bat Right click the drive choose "eject" Installed in powered on my unraid server It booted just fine although it started with all drives mounted and running, I never saw "Stopped. Configuration valid." Also I probably could just have deleted the files I added ".old" instead. Like I said I am a linux noob, but I hope that this will help someone in the same situation I was in.
  2. I little update. Things have been stable since I moved the drives off of the AOC-SASLP-MV8. No red balls. I know that a few of my older drives are approaching the end of their lives. I did do a pre-clear on the two drives that did give me the red balls last month they passes the pre-clear test results with "No SMART attributes are FAILING_NOW" but a couple of "near_thresh" line items. Going to add my second 3TB Red drive this week. I've attached the pre-clear results from the drive that gave me my first red ball. There is only one line with a "near_thresh" indication, it's the End-to-End_Error = 1 1 0 near_thresh 150 Is this something that I should be concerned about? Would this have caused the first red ball? Or am I right in suspecting AOC-SASLP-MV8? preclear_HD154UI.txt
  3. So I guess I did miss something. The array rebuilt and I checked parity without any errors so for now it seems to be in a good place. Replacing the drive is next on my list. Is there a way to do a test to get similar results like a pre-clear but without completely clearing the drive in the process? If so I'd like to run it on the other drives in the array. In the mean time I'm going to pre-clear (ie test) the two drives I removed/replaced in the past two weeks. Also since I think I've narrowed down the issue to the AOC-SASLP-MV8 card is there any type of test/diagnostic I can do that to really see if that is the issue?
  4. I should have thanked you when I first got everyone's quick reponse but I wanted to wait till I got my 1 cycle pre-clear results first. I didn't know that unraid would keep it red until some intervention was done first. The drive passed under pre-clear.I've attached the report just in case I missed something. I have re-arranged my drives in my unraid system so that none of them are going through the AOC-SASLP-MV8. As of this moment I'm thinking this might be issue. Wished it wasn't but better than a bad motherboard and going the headache of changing that out. Going to re-assign the drive and let it rebuild. I'll update with the outcome. preclear_results_Seagate_1.5TB_9XW00BCZ.txt
  5. A little update. Installed rfstools and yareg to take a look at the latest red ball drive within windows. Randomly checked files and it all seems ok. Decided to switch drives around to different physical slots on my unraid system to see if that changes anything. All the red balls have been located on the slots associated with the SUPERMICRO AOC-SASLP-MV8. Perhaps this is the issue....? Put the seemingly ok drive back in the system and I still get the red ball of death. I decided to pre-clear this one on a one cycle. Currently in post-read at 28%. Adding drives is not a quick process in unraid is it? I'm currently wondering what the pre-clear results will be and if it's all good if I will have a red ball when it's done or not. Got another 3tb Red drive in today think I'm going to back up my critical data on that before anything else goes down the tubes. Any advise would be appreciated.
  6. If I find that drive is fine then is it the control card? Is there a way I can test to see what the real issue is? Isn't there a way to read an unraid drive when it's plugged into windows?
  7. Unraid 5.0 RC 10 I've had 4.7 running for about a year with little to no problems. But still a relative noob. Decided to jump the gun give 5.0 a try started with rc9 then quickly moved to rc10. Things were running fairly smoothly installed sabnzbd, sickbeard, couchpotato. Got my first redball next to one on my drives on Jan 10th. Little surprised but since it was a about 4 years old 1.5TB samsung I wasn't worried. Had another 1.5TB sitting around that was working fine so pre-cleared that installed and everythign was going smoothly. While that was pre-clearing and all I ordered a 3TB Red drive to update my parity drive. Got that, started a 3 cycle pre-clear (6 days if anyone was wondering) no errors. Swapped out the older 2TB parity drive with the new 3TB let everything rebuild. Things seemed to go fine. Went to do a parity check it was chugging away I went to bed. Woke up refreshed my screen and behold another red ball on a different drive. This time a 1.5TB seagate. Thought that was odd but just a coincidence. Since I still had my old parity drive hanging out I pre-cleared that just fine, let the system rebuild last night and this morning right after I clicked to do a parity check I refreshed to see how long it was going to take.. 3rd red ball on another drive. At this stage I no longer think my old drives a just dying and something is going on. TL;DR Multiple drive failures thinking it's no longer a coincidence. Other issue I was going to address but may/may not be related. Sickbeard keeps loosing system settings I have to keep running the install wizard. Then after having it shut down for a number of days with this fiasco it's no longer installed, simply gone I never un-installed it. Sab, sick, and couch are all stored on my cache drive. PLEASE NOTE. If this is not related to my drive failures I don't need to address this now. syslog-2013-02-05.txt
  8. Thanks to everyone for their input. I never really thought about fill rate before. I guess I just saw it as "It's time for a new drive lets just get the largest I could afford." Since I combined all of those 1.5TB to make my unraid I saw I was at about 70% capacity even with a new 2TB drive as storage I just figured I'd fill everything up within a couple of years. This will be the first new drive since my initial build so I guess my fill rate isn't that high. I am going with a 2TB and wait for 5.0 final. This seems to be the best option for me at this very moment. Again I really appreciate everyone's input and it's great to know that so many haven't had issues going to a 5.0rc
  9. I'm currently running 4.7 without any issues for 165 days of uptime (including a power failure). I am going to be in need of some more space here in the not too distant future. I currently have 9 drives. (2) 2TB, (6) 1.5TB, and 80GB cache. Obviously one of the 2TB is the parity drive. I am capable of having 20 drives in total in my current system. I am considering adding a 2TB for extra data or adding a 3TB as the Parity and moving the current 2TB parity to a data drive. Either way I still going to add 2TB drive as data but with the possibility of having the 3TB for any future upgrades. Since I have had such success with 4.7 I am wary of updating to any of the 5.0 RC for fear that it simply won't work. From my experience with electronics and such I have the philosophy of "If it works don't upgrade it". Am I being paranoid about updating? Should I just wait it out for the official release? Or should I just go with another 2TB? Thanks! For reference I have: ASUS M4A88T-M AM3 AMD 880G HDMI Micro ATX AMD Motherboard SUPERMICRO AOC-SASLP-MV8 PCI Express x4 Low Profile SAS RAID Controller and Two generic (but recommended) PCI and PCIE sata cards.