icedragonslair

yes these were all running with no errors...that's why the 'What the heck'? Yes, I tried click here... mediaserver1-diagnostics-20190225-0020.zip

For any of my plugins which are only the few like CA Auto update & Fix common problems etc. also not able to turn on system notifications getting this in the header: System notifications are disabled. Click here to change notification settings. I just looked and they are all listed as author: anonymous, Version: Unknown and Status: unknown

What the heck is this?

Yeah I saw that too, its why I am confused, is t maybe spinning down? and if so how do I stop that from happening? By the way Constructor, Thank you so much, and same to all here that help myself and others

Parity check ran on new schedule last night except it is now finding a error Feb 23 01:00:01 mediaserver1 kernel: ata5.00: exception Emask 0x52 SAct 0x0 SErr 0x400c01 action 0x6 frozen Feb 23 01:00:01 mediaserver1 kernel: ata5.00: irq_stat 0x08000000, interface fatal error Feb 23 01:00:01 mediaserver1 kernel: ata5.00: exception Emask 0x52 SAct 0x0 SErr 0x400c01 action 0x6 frozen Feb 23 01:00:01 mediaserver1 kernel: ata5.00: irq_stat 0x08000000, interface fatal error With all the reading i have done this may just be a cable or power cable error (would make sense if there is a defective one, since I just changed them all). I have included diag mediaserver1-diagnostics-20190223-1205.zip

Trying that now, I have moved the scheduled day to Saturday. If it doesn't run tonight I will know and will post either way, thanks so much for the help, Ice

Nope still running every night, will change parity schedule to Monday

Ran last night, will see if the glitch is over tonight

This setting (sunday at 0100) has worked without a hitch on this version until about a week ago. I will however, update and reset calendar to monday instead mediaserver1-diagnostics-20190216-1027.zip

I set my parity schedule for weekly and at 1am (0100), since I had to replace all cables, it now runs every morning even though the schedule says otherwise. What do i have to do to get this back on schedule? mediaserver1-syslog-20190216-0919.zip

I seem to have this all moving along again after replacing all the cables. I have also replaced all power extensions with locking ones. There is however one issue, It seems the parity check is now running every night at 0100 hours, versus weekly at 0100 hours, even though I have turned off the scheduler and then turned it back on, with the correct date/time. Is there a way to reset this to default then set it again?

has anyone used latching sata cable splitters like these with iStar USA's BPN-DE350SS drive cage

Yes I did, Have I not only never had issues...but at the time of the advisory i checked to make sure all was in order (they are all shrouded). A lot better than the alternative I had before (begins with an 'S' lol) I normally use locking power and sata cables, but I have not tried them with the iStarUSA backplane cages see this Link Here

No to enabling eco mode on the PS, They were read errors...I reset all cables and am trying again...so far at 34% of the parity rebuild with no troubles.However, it was at 56% when this happened before, keep your fingers crossed...'ALL' new cables and extensions arrive on Friday (a 'just in case') and will swap them out then...New PS on the way for Monday, if it doesn't need it , it can sit on the shelf. new controller (8-port) planned for next week and I already have new memory and another board here...if I have too it means a new build and sell the old (or keep it for spares if I can afford too) As far as 'giving up and rebuilding' if this doesn't work than I may go a different way...meaning tossing in the towel and just use huge externals

Okay disk twelve just showed up with over 12,000 errors...giving up and rebuilding array, maybe going a different way Thank you for your help

Nope, Infact here... Let alone nothing has changed since there were no errors at all, and then the error and I started changing out cables and a power supply. I did just order round cables and new breakouts...at the very least I'll have plenty of spares

So is it normal when the rebuild starts that 7 more discs bring that same error? I have replaced the PS, and all cables and these disks are on 4 different controllers... These are now showing the same error: Parity Disk 1 Disk 4,9,10,11,12,13,16

Thank you so much for the help I have already ordered new ones except for the four breakouts that seem to be fine and I will be replacing those down the road Thanks again to all, Ice

So...no, or yes on keeping it as a parity drive?

I guess I'm concerned because I have never had one prior to this, since this is the parity drive is this a warranty issue I can rma for? And if not, should I recycle that drive for another (swap it out for an identical spare drive that I have) and then run the the parity rebuild?

This - 199-UDMA_CRC_Error_Count 1 popped up on my system after it told me the parity had errors, I replaced power and sata cable. also moved it to a different slot in a different cage (just in case) I am now running the third preclear to see if anything changes On the second preclear i just reseated everything and nothing changed Should I expect that error to go back to zero and if it doesn't what's my next step?

Rebooted and all seems fine at this point, will check performance over the next few days, thanks loads

Seems odd that it would just begin now after a few years of great performance, but I will reboot to see any changes. As far as LSI, Disabled Vet with Fixed income says no...lol

I just recently got this on my server 'irq 16: nobody cared" I did notice performance of the parity check was way down, then I found this. I didn't know if this had anything to do with the other, or not. Thanks for all the help Diagnostics belowmediaserver1-syslog-20181112-1138.zip

All good for now, another problem but staring a thread for that, thanks for everything