Argyll

Members
  • Posts

    10
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

Argyll's Achievements

Noob

Noob (1/14)

0

Reputation

  1. Those boards might be a little hard to find. Check the Builds forum and the Hardware Compatibility Page for an idea of what people are/have used. Also, rajahal's prototype builds will list everything you might need. OK, well that actually was quite painful. As there doesn't appear to be an actual 'blessed' board (Level 3) that is still made or readily available I had to kind of just sort things out as I could and hope for the best. I ended up with: ASUS P7H55-M Motherboard Intel i3 Chip 8gb Memory 2x PCIe 1x Highpoint 2300 RocketRaid cards - I did upgrade these to BIOS 2.5 but didn't make any other setting changes. 1x PCI Promise Sata 300 TX4 card (from old system) This let me get all 15 drives appearing with an UnRAID 4.7 Pro boot thumb drive. Of course their placement within the array is not correct and I have not started to re-assign them back so as to hopefully get my array back up. I am getting some errors and concerning messages in the log and wanted people far smarter than I with UnRAID to take a look before I start to assign the drives as I am DESPERATE not to lose the data on my array. I have attached by SysLog below and would be very grateful if an expert could take a look and tell me if there is anything that jumps out at them as needing correction before I start assigning drives back into the array. In particular it appears that some of the drives are being downgraded from 300 to 150? Also, this slightly terrifying warning regarding the 2300 cards stating that they ALWAYS corrupt drives was a bit unsettling, especially as I had selected the card because of the Wiki listing. Maybe it has nothing to do with UnRAID but I thought I had better ask. Thanks in advance for your time and assistance! It is greatly appreciated! NAS02_System_Log.txt
  2. OK thanks! Sorry I wasn't clear, the memory test did run, it just gets bunches and bunches of errors while it runs... I can try just with one stick. Although this last boot everything did as before but my screen is now kind of scrambled up with blue blocks of text appearing randomly. I fear the mobo is dying... ugh.... I guess I definitely got my moneys worth after 6 years of steady service, but still disappointing. OK, I will assume that if I buy one of the motherboards used by LimeTech in their server builds I will be OK.
  3. Yes, I believe it is referring to the bot drive and non of your data drives. So long as you do not assign anything right now you should be fine. Thanks so much for all of your help! Well, made a 4.7 boot USB and carefully moved over my keys and the minimum number of necessary .cfg files along with the shares details. I get the same panic. I rebooted again and this time selected memory test instead of boot and got a whole bunch of errors. Looks like the memory on the mobo has somehow dynamically gone bad, or the motherboard is dying. Although it attempts to boot, etc. so I am not sure whether I just need to go get another motherboard or just invest in a new memory chips. If I have to go to a new motherboard is there any secret in keeping the array in tact even if drives get put on different controllers, etc? Or does UnRAID figure it out every boot? Sorry, to be so 'dull' but this thing has run like a tank for over 6 years and I just haven't had to mess with it (which is FANTASTIC).
  4. OK, I can begin that process. But before I do, I just want to check. The error is referring to the flash drive and has nothing to do with my drive arrays correct? I just am a little scared that 28TB of stuff might now not be accessible... ;-)
  5. Thanks for quick idea! I did and it comes back clean. I bought a backup flash back in 2005 and license, so far I have resisted using it given that I have never updated it with newer versions, etc. I could try it just to see if it will boot up with the really old version, but I don't want to do anything to corrupt my array.
  6. I have been running a 15 drive UnRAID array since 2005 and have been just thrilled. All of the sudden this morning the unit booted and received a Kernel Panic: VFS: Couldn't open root device "(NULL)" or unknown-block(8,1) Please append a correct "root=" boot option here are the available partit[runs off screen so I can't read] Kernel panic - not syncing: VFS: Unable to mount root on unknown-block(8,1) Pid: 1, comm: swapper not tainted 2.6.32.9-UnRAID #5 Any ideas?