bombz

Hasn't been a good week for me. So this all started on Sept 23rd when I was away and disk 3 failed (the server was frozen). Upon reboot I had disk 3 (WD 4TB RED) showing "Device is disabled, content emulated" When I returned to work on the server. I removed the drive and installed another WD 4TB Red. The drive was detected, and added, and rebuild began (approx 20-22 hours). During that parity, the device went yellow, and contents was emulated. (sigh) Parity finished rebuild So reading some more online, I read about cabling and my SAS card. I changed out the breakout cable + moved the SAS card to another PCIe16X Again I started the server and ran a parity check. Everything checked, and was 100% successful. I rebooted the server and it came back online with no concerns. I then started to write data to my array etc. During the copy I found 'taracopy' say network device (unraid) unassailable. I went back to the WebGUI and refreshed and then saw another error on Disk 3 "Device is disabled, content emulated" The device had a RED X and I checked out the Dashboard, and it was also FAILING S.M.A.R.T. I checked the .log file and there is a ton of write/sector errors. Keep in mind both of these WD 4TB REDs were precleared prior to use (from brand new) Now I have another WD 4TB RED sealed, and may pre-clear it before adding (takes 48 hours) But what I am trying to determine if it is actually the drives itself or the SAS card [ CONTROLLER: SUPERMICRO AOC-SASLP-MV8 ] or something else. Very sad and time consuming, need to get back and operational. I was looking if there was any assistance. syslog posted below syslog.txt

Fair enough, I appreciate the information. I wonder now how I can fix these plugin errors, to make everything nice and clean. I will keep poking away at it

So I use my disk mapping from windows PC I just browse from one disk and move to another. I suppose I am not doing this efficiently. I am all ears to learn the specifics on how to do this better for sure! (stupid windows) lol :-)

Ah, new forum, I just noticed sigs are off by default. I have adjusted and added mine back too I always browse my array by my disk mapped drives. I never WRITE to shares. Shares are there just for READ ONLY. As for moving/copying data (which is slow in general) I have found copying to array from local PC or Disk-to-Disk within array tends to be slower then what i have seen in the past perhaps it is due to not having turbo mode enabled at all? I am using Taracopy for disk copy. move (Windows PC)

OK. I thank you for the response. Again I am new to this process. I am running out of room/space in my case, so I want to remove some smaller size disks, and replace them with a bigger disk. So it seems I need to add the new disk to the array, copy data from the (2x) disks I am removing to the newly installed one. Then remove the (2x) disks (via gui) and run a new parity sync. I want to free up space in my case, so I can get dual parity up and running successfully. I will read over your instructions in detail some more later as I am just heading out. I appreciate the community support SO much. I love UnRaid ! I am deferentially confused with the process. I have read the Wiki over and over, it makes sense, I suppose I am nervous of data loss 01) removing (2x) 1.5 TB disks 02) replacing with (1x) 4TB disk My plan. Take screen shots of WEBGUI (desk setup) for visual reference (in case needing to re-assign disks) 01) Add 4TB disk to array (new disk) 02) copy all data from (2x) 1.5TB disk to the new 4TB disk added in the array 03) remove (2x) 1.5 TB disks from array 04) parity sync and protect array I think I am doing this correct ? I don't have to remove (2x) disks at once, I can do it the slow and steady way, and just do one at a time, which is probably much wiser

Hello, I have recently hooked up a UPS to my system, and tested it, and everything seems to be working OK.... well the one thing that doesn't happen is the UPS turning off AFTER safe shutdown, regardless things seem to be working as they should. My question is, that I am seeing a plugin failure and would like to correct these plugins, but not sure how to go about it. I have posted some screens to assist everyone with what I am looking at. I would love to hear any feedback. Thank you! I am not sure if i need to be posting the log file etc. Please let me know if any more information is required !

OK So basically I want to copy all data over to another drive or device first. Remove any global shares MAKE NOTE of the drive assignments ( via screenshot etc ) Tools > New Config (etc) Once parity is rebuilt with the new config and data is secure, I can then add the new drive It always scares me doing these parity syncs and moving devices around, i don't want to lose data obviously

Hello, I have been working on my server, and these days as disks are getting larger, I am wondering what the process is to combine (2x) disk(s) to (1x) disk(s). For example: I have a total of 12 disk(s) in my array. I want to combine (2x) of these disk(s) but not have UnRAID detect a missing disk in my array. What is the best method to shrink my physical disk(s) array. I was reading this, and wanted to make sure I am on the correct track for doing this procedure when the time comes :-) https://wiki.lime-technology.com/Shrink_array Thank you!

Hello again everyone, I have now decided I need a new UPS. I have been looking at this one (.ca / Canada) I have read some peoples posts here and I think I have decided on this one. Can anyone give me any feedback before I pull the trigger? Thank you. https://www.amazon.ca/CyberPower-CP1500AVRLCD-Intelligent-Mini-Tower-Features/dp/B000FBK3QK/ref=sr_1_1?s=electronics&ie=UTF8&qid=1498157676&sr=1-1&keywords=CyberPower+ups Looking forward to hearing back

Rules for parity2 are the same as parity, it needs to be as large or larger than your data disks, current parity size doesn't matter. Thank you as well!

As has been repeated many times, unRAID is not a backup - it just provides tolerance against disk failure. Irreplaceable files should still be backed up elsewhere - preferably at several locate/ns if they are really important. When using dual parity it is not a requirement that both parity drives are the same size - just that they equal or exceed the size of the largest data drive. Much appreciated. Sorry I am behind the times with lack of information on some things. I always like to be sure, as unRAID is really important to me ! Thank you for the update

Hey everyone, I just recently upgraded to the latest 'official' UnRAID and I saw it had the new added GUI from the local server (nice touch team) and with that DUAL PARITY! I didn't even know about it but it seems really awesome. I read over what garycase had said about this a bit. My server is my 'baby' I don't have a backup of it, as that would get expensive to backup or mirror a duplicate 25ish TB of data. This dual parity is intriguing to me as it seems to have EXTRA protection if more then one drive fails. As if now I have a 6TB parity disk, so with that, if you decide to run dual parity, do the parity disks HAVE to MATCH in size 2x6TB in this case, as general rule is parity has the be the biggest size in the array. I think I want to use this feature for extra protection... any pointers? Should I be doing the same process? (Pre-clear the disk + add to array + run parity check) and I am done. I want to make sure I am understanding this correctly. Any pointers , suggestions, recommendation are welcome! Thanks team

I am going to try to DISABLE AHCI and leave it on IDE, as well disable C1 CPU states to see if that helps -- I am guessing it won't but I am out of ideas, besides trying new SAS breakout cables (which I don't have) or purchasing a new PSU

Can anyone assist with what this means ? I just put a new system board in and SAS card , been running for a few days now I see these errors Sep 1 00:52:30 UnRAID kernel: sas: sas_ata_task_done: SAS error 8a Sep 1 00:52:30 UnRAID kernel: ata15.00: both IDENTIFYs aborted, assuming NODEV Sep 1 00:52:30 UnRAID kernel: ata15.00: revalidation failed (errno=-2) Sep 1 00:52:30 UnRAID kernel: mvsas 0000:04:00.0: Phy7 : No sig fis Sep 1 00:52:34 UnRAID kernel: sas: sas_form_port: phy7 belongs to port6 already(1)! Sep 1 00:52:35 UnRAID kernel: ata15: hard resetting link Sep 1 00:52:35 UnRAID kernel: ata15.00: configured for UDMA/133 Sep 1 00:52:35 UnRAID kernel: ata15: EH complete Sep 1 00:52:35 UnRAID kernel: sas: --- Exit sas_scsi_recover_host: busy: 0 failed: 0 tries: 1 Sep 1 01:02:17 UnRAID kernel: sas: Enter sas_scsi_recover_host busy: 1 failed: 1 Sep 1 01:02:17 UnRAID kernel: sas: trying to find task 0xffff8803e478ad00 Sep 1 01:02:17 UnRAID kernel: sas: sas_scsi_find_task: aborting task 0xffff8803e478ad00 Sep 1 01:02:17 UnRAID kernel: sas: sas_scsi_find_task: task 0xffff8803e478ad00 is aborted Sep 1 01:02:17 UnRAID kernel: sas: sas_eh_handle_sas_errors: task 0xffff8803e478ad00 is aborted Sep 1 01:02:17 UnRAID kernel: sas: ata15: end_device-1:6: cmd error handler Sep 1 01:02:17 UnRAID kernel: sas: ata9: end_device-1:0: dev error handler Sep 1 01:02:17 UnRAID kernel: sas: ata10: end_device-1:1: dev error handler Sep 1 01:02:17 UnRAID kernel: sas: ata11: end_device-1:2: dev error handler Sep 1 01:02:17 UnRAID kernel: sas: ata12: end_device-1:3: dev error handler Sep 1 01:02:17 UnRAID kernel: sas: ata13: end_device-1:4: dev error handler Sep 1 01:02:17 UnRAID kernel: sas: ata14: end_device-1:5: dev error handler Sep 1 01:02:17 UnRAID kernel: sas: ata15: end_device-1:6: dev error handler Sep 1 01:02:17 UnRAID kernel: ata15.00: exception Emask 0x0 SAct 0x8 SErr 0x0 action 0x6 frozen Sep 1 01:02:17 UnRAID kernel: ata15.00: failed command: READ FPDMA QUEUED Sep 1 01:02:17 UnRAID kernel: ata15.00: cmd 60/00:00:e8:64:b9/02:00:20:00:00/40 tag 3 ncq 262144 in Sep 1 01:02:17 UnRAID kernel: res 40/00:00:01:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout) Sep 1 01:02:17 UnRAID kernel: ata15.00: status: { DRDY } Sep 1 01:02:17 UnRAID kernel: ata15: hard resetting link Sep 1 01:02:19 UnRAID kernel: drivers/scsi/mvsas/mv_sas.c 1430:mvs_I_T_nexus_reset for device[6]:rc= 0 Sep 1 01:02:19 UnRAID kernel: sas: sas_ata_task_done: SAS error 8a Sep 1 01:02:19 UnRAID kernel: sas: sas_ata_task_done: SAS error 8a Sep 1 01:02:19 UnRAID kernel: ata15.00: both IDENTIFYs aborted, assuming NODEV Sep 1 01:02:19 UnRAID kernel: ata15.00: revalidation failed (errno=-2) Sep 1 01:02:19 UnRAID kernel: mvsas 0000:04:00.0: Phy7 : No sig fis Sep 1 01:02:23 UnRAID kernel: sas: sas_form_port: phy7 belongs to port6 already(1)! Sep 1 01:02:24 UnRAID kernel: ata15: hard resetting link Sep 1 01:02:24 UnRAID kernel: ata15.00: configured for UDMA/133 Sep 1 01:02:24 UnRAID kernel: ata15: EH complete Sep 1 01:02:24 UnRAID kernel: sas: --- Exit sas_scsi_recover_host: busy: 0 failed: 0 tries: 1

Hmm I wonder if I can simply replace my current CM 4in3 drive bays for hot swap inserts --- got me thinking ... I like that last post... looks nice

Let me know if you come across anything -- 15 would be a nice number / hot-swap drive bays I am tossing a different CPU and RAM in this week, due to my issue last week. My system seems so armature compared to some of the systems ran here

I guess I don't really NEED that -- I have 12 now, I could use another 4 (as I have 4 sitting around) not being used as my case is at full capacity

Hello everyone, I wanted to ask if anyone had some decent case recommendations for unraid -- I am looking for something like a 20 drive case. Something that has great cooling and perhaps hot-swap bays for easy upgrading. Thanks

I wasn't sure of another alternative when all this happened, so I replaced it with the same Supermicro card. I have the card installed on my new motherboard and a parity check/sync is running

Thanks man --- just got the part today, no harm in double checking -- I'll follow up with how it goes

Hello, Last week I had an issue with my UnRaid server. It seemed after investigation that my SuperMicro AOC-SASLP-MV8 REV 1,01 (must have) caught on fire. The card is half black. Also plastic from the PCI-E slot that melted on to the board, right beside the slot. Funny thing is the motherboard still POSTs but I won't be using it for UnRAID anymore In this case half my array disks run off this card. I ordered a new motherboard + the same SAS card for replacement. What I am curious about is how this may have happened. There was no power outage or anything to that extent. Could it have been just a short circuit? Under powered PSU ? or just old age and I got lucky there was not more damage. I wanted to be sure also with the replacement SAS card, the UnRAID environment will resume as normal .... i.e. the new SAS card won't push new IDs to the disks or something causing my data or array to fail. Sorry there is a first time for everything and I wanted to be sure and check with the community that I am going down the correct path. My SAS card should be arriving tomorrow or the next day. Thanks everyone.

Hello, I have a quick question and I am not sure if anyone has thought of this setup like I have. Being PLEX is not a QOS service at all, I wanted to set limitations on PLEX for times-of-day that it uses less bandwidth (traffic out/upload speed). My example goal is to simply tell plex: from 8pm - 12am use less traffic (so if you have 20mbit upload) plex use 10mbit at this time. I was not sure if there was a docker config that allowed this for plex. I have looked into my router dynamic QOS and it SUCKS (lol) once enabled on the router, it harms the over all bandwidth of the whole network... I am guessing makes the CPU chug, I have looked up fourms on this, and it is apparent. So I have counted that solution out. other then that, all I can think of is pfsense (which I am just looking into, over my head at this moment) or being my UnRAID server has decent specs for QOS, I perhaps it can control everything for this MINOR adjustment I need to do, limit outbound traffic daily at specific times. Any suggestions I would apprecaite.

One last question, if I do RMA this drive (because the number is changing) I assume UNrAID supports 6TB drives with no issue. Just pre-clear the drive and good to go ?

OK, so it did go from 38 to 39 over a two to three day span --- for general knowledge when should I be worried?? Sorta sucks I am seeing this on the parity drive, being it isn't that old -- however, it would still be within warranty to RMA it as well ... think it would be wise just to try to RMA it for the sake of it, or leave it for a bit till it gets worse. I guess parity would be a drive that has more read/writes on it then others..... There is nothing i'd hate more then 2 drives failing (i'd be screwed) -- thanks for the response, and let me know your thoughts

After doing a parity check it seems the same result stants on the drive in question Parity Disk (highlighted orange) 197 Current pending sector 0x0032 200 200 000 Old age Always Never 39 any thoughts ? I have also done a SMART EXTENDED SELF-TEST - to which the drive passed... I am not sure if this highlighted area of the disk should be a concern or not. :-/