slayer

Members
  • Posts

    33
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

slayer's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. Does anyone know how to update ffmpeg? Is there a guide for doing this?
  2. If it helps someone. I have older Dell GX280 and this card doesn't allow it to post. In fact, I tried it in other newer Dells and it doesn't allow them to post either. I did read somewhere that Dell's PCI-E slots are limited to graphics cards only even though I found official Dell documentation that talks about PCI-E slot capabilities being able to use it for network, graphics and other purposes. Not sure what to make of it, I even thought that card was defective and seller was nice enough to send me another one, but new card does exactly same thing in Dell computers. Sort of disappointing.
  3. Thank you Joe. I will upgrade and will follow your advice.
  4. Joe, I've attached entire syslog. I can't see any errors. Perhaps I'm not looking at the right places? My wife actually restarted unRaid by just cycling power on server, without stopping array first. I since performed two NOCORRECT parity checks and both times it came back with those 66 errors that I can not find in syslog. Thanks for you help. syslog-2011-01-29.txt
  5. "Parity is Valid:. Last parity check 1 day ago . Parity updated 66 times to address sync errors." Yet during parity check there were no errors according to log: Jan 27 21:38:26 Tower kernel: mdcmd (60): check NOCORRECT Jan 27 21:38:26 Tower kernel: Jan 27 21:38:26 Tower kernel: md: recovery thread woken up ... Jan 27 21:38:26 Tower kernel: md: recovery thread checking parity... Jan 27 21:38:26 Tower kernel: md: using 1152k window, over a total of 976762552 blocks. Jan 28 01:01:15 Tower kernel: mdcmd (1478): spindown 1 Jan 28 01:01:15 Tower kernel: mdcmd (1479): spindown 2 Jan 28 01:36:46 Tower kernel: md: sync done. time=14299sec rate=68309K/sec Jan 28 01:36:46 Tower kernel: md: recovery thread sync completion status: 0 Jan 28 01:51:49 Tower kernel: mdcmd (1833): spindown 0 Am I missing something?
  6. Good catch Peter, I wondered about this myself but wasn't concerned about it as much as those errors. I have no idea how I can enable full 3Gbps rate. I will double check BIOS, but besides that I don't know what needs to be done as there are no jumpers on new drives any more. Thanks for your reply.
  7. Peter, Funny you say that it's Seagate 1TB drive, that's exactly what I have as my parity drive and I also have two 750GB data drives. I will try to figure out which drive is actually ATA1 and report here. Thanks alot.
  8. Joe! First of all let me thank you for all your help on these forums. Your support is invaluable to this community!!! And back to my errors. I figure I need to find out what drive is on ATA1 and proceed with trouble shooting?
  9. Hello forum members! I'm using version 4.5.4. I got some errors during monthly parity check: Jan 1 00:00:02 Tower kernel: mdcmd (184090): check Jan 1 00:00:02 Tower kernel: md: recovery thread woken up ... Jan 1 00:00:02 Tower kernel: md: recovery thread checking parity... Jan 1 00:00:02 Tower kernel: md: using 1152k window, over a total of 976762552 blocks. Jan 1 00:39:51 Tower kernel: ata1.00: exception Emask 0x12 SAct 0x0 SErr 0x1000500 action 0x6 Jan 1 00:39:51 Tower kernel: ata1.00: BMDMA stat 0x5 Jan 1 00:39:51 Tower kernel: ata1: SError: { UnrecovData Proto TrStaTrns } Jan 1 00:39:51 Tower kernel: ata1.00: failed command: READ DMA EXT Jan 1 00:39:51 Tower kernel: ata1.00: cmd 25/00:08:a7:a4:8c/00:01:0f:00:00/e0 tag 0 dma 135168 in Jan 1 00:39:51 Tower kernel: res 51/84:38:77:a5:8c/84:00:0f:00:00/e0 Emask 0x12 (ATA bus error) Jan 1 00:39:51 Tower kernel: ata1.00: status: { DRDY ERR } Jan 1 00:39:51 Tower kernel: ata1.00: error: { ICRC ABRT } Jan 1 00:39:51 Tower kernel: ata1: hard resetting link Jan 1 00:39:51 Tower kernel: ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Jan 1 00:39:51 Tower kernel: ata1.00: configured for UDMA/133 Jan 1 00:39:51 Tower kernel: ata1: EH complete It is also reported that: Parity is Valid:. Last parity check 3 days ago with no sync errors. Can someone tell me what these errors mean and if I should worry about them? Thanks so much.
  10. Gents, turns out that unlocking drive did the trick, no more errors of any kind. Please see attached log if interested. Thanks to all for taking time to help me out, I appreciate it very much. log2.txt
  11. Well, if the only problem with a drive is that it is locked then unlocking and using it would be ok by me, if it is really dead I still have warranty until 2012. I guess I win either way I just need to figure out if problems in a log and Seatools where due to drive being locked or they are genuine drive failure problems.
  12. I'm having second thoughts on that 320gb drive. Since I took it out of modded original XBOX it needs to be lnlocked? Perhaps it needs to be returned back to non XBOX condition in order to be recognized/used in PC/Linux environment?
  13. The drive in question is Seagate, I used Seatools and it failed both short and long tests showing 249 bad lba's, go figure. Just confirms one more time why backup systems like unRaid are necessary if data needs to be protected from loss.
  14. Gents, preclear did not run properly indicating some problems with drive according to SMART so I threw in 40Gb drive and low and behold after assigning to array drive started to clear, log is clean. I can't believe that 320gb drive is dead. It was just working in my xbox. Is it possible that it's not dead and something can be done?
  15. Got it, will run and return with results, although when I looked at preclear instructions they looked complicated to me Thanks for all input.