mazma

Hey Scott, Not that I'm aware off. I did find his post and compared by directory structure and it was correct anyway.

We have quite a large library so I was trying to avoid re-adding everything as it would mess up whats been watched, on deck etc etc. In the end I've just done exactly that, kids are going crazy lol

I'm in the process of moving over to this whole docker thing - I have a basic grasp on it so bear with me. For years I've been running UnRaid v5 and used to just download Plex PMS and copy it to my flash drive and I was good. There was a little plugin where I could specify the library and temp location, stop , restart etc and that was it. Previously I pointed the plugin to /mnt/user/PlexLibrary for the library etc. So when adding the Docker in the path field I did: Container Volume: /config > Host Path: /mnt/user/PlexLibrary Firing up Plex and there is no library although looking in settings its picked my Plex settings etc. As for the library I found a post that suggest adding /mnt/ to the docker path. No difference. What I am doing wrong here?

Yup, on the pre-flight check of the NewzNab install. Entering Pear on the command line returns "command not found" so I'm guessing its not installed. Downloaded the installer and tried to run: php go-pear.phar as instructed. The installer starts then quits with Beginning install... XML Extension not found Php -m returns: [php Modules] bz2 Core curl date dba dom ereg gmp json libvirt libxml openssl pcre Reflection SimpleXML sockets SPL standard zip zlib which shows the Xml extensions. I have no idea beyond this. My newznab install was on a Mac before.

Just installed this via Docker. What is the username/password for the webgui ?

I'm further back as PEAR isn't installed. When I try to install it I get an XML Extension isn't installed error. I checked my Php config and it looks like all the xml is there. Did you have this issue?

Trying to install NewzNab my unRaid (had it working for years on a separate Mac). One of the requirements is PEAR. I've followed the installer guide for PEAR but installer quits with "XML Extension not found" Spent plenty of time with Google and I haven't been able to find an answer. Would welcome any advice as I can't proceed without resolving this. Thanks!

Is it possible to install SVN on Unraid6.b12?

Hey All, Just upgraded to unRaid6.b12. Previously I was running NewzNab on an old mac mini and I'm looking to have this run in my unRaid server instead. I saw there was a MariaDB docker which I've installed but I have no idea on how to progress after that. What about a web server ?

Hey Peeps, I want to convert an existing drive in the array into a cache drive. I've moved the data on to other drives. Do I just need to run the New Config tool and go from there? Unraid 6b12. Thanks!

Just been reading up on this Docker thing. I think I understand it so bear with me. Has anyone "dockerized" NewzNab?

Poked at all the cables and none were loose. Rebooted and all appears ok, i.e. no errors etc. Running a parity check. Weird.

Ok, so the admin panel did load but its extremely slow. Disk 4 shows 992 errors but the disk is still listed as green, not red. The server is running a parity check. Looks like the log keeps repeating the same thing: Apr 3 16:58:00 Tower kernel: ata11.00: exception Emask 0x50 SAct 0x0 SErr 0x280900 action 0x6 frozen Apr 3 16:58:00 Tower kernel: ata11.00: irq_stat 0x08000000, interface fatal error Apr 3 16:58:00 Tower kernel: ata11: SError: { UnrecovData HostInt 10B8B BadCRC } Apr 3 16:58:00 Tower kernel: ata11.00: failed command: READ DMA Apr 3 16:58:00 Tower kernel: ata11.00: cmd c8/00:20:57:c9:02/00:00:00:00:00/e0 tag 0 dma 16384 in Apr 3 16:58:00 Tower kernel: res 50/00:00:00:00:00/00:00:00:00:00/a0 Emask 0x50 (ATA bus error) Apr 3 16:58:00 Tower kernel: ata11.00: status: { DRDY } Apr 3 16:58:00 Tower kernel: ata11: hard resetting link Apr 3 16:58:01 Tower kernel: ata11: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Apr 3 16:58:01 Tower kernel: ata11.00: configured for UDMA/33 Apr 3 16:58:01 Tower kernel: ata11: EH complete Apr 3 16:58:01 Tower kernel: ata11.00: exception Emask 0x50 SAct 0x0 SErr 0x280900 action 0x6 frozen Apr 3 16:58:01 Tower kernel: ata11.00: irq_stat 0x08000000, interface fatal error Apr 3 16:58:01 Tower kernel: ata11: SError: { UnrecovData HostInt 10B8B BadCRC } Apr 3 16:58:01 Tower kernel: ata11.00: failed command: READ DMA Apr 3 16:58:01 Tower kernel: ata11.00: cmd c8/00:20:57:c9:02/00:00:00:00:00/e0 tag 0 dma 16384 in Apr 3 16:58:01 Tower kernel: res 50/00:42:00:00:00/00:00:00:00:00/a0 Emask 0x50 (ATA bus error) Apr 3 16:58:01 Tower kernel: ata11.00: status: { DRDY } Apr 3 16:58:01 Tower kernel: ata11: hard resetting link Apr 3 16:58:02 Tower kernel: ata11: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Apr 3 16:58:02 Tower kernel: ata11.00: configured for UDMA/33 Apr 3 16:58:02 Tower kernel: ata11: EH complete Apr 3 16:58:32 Tower kernel: ata11.00: exception Emask 0x40 SAct 0x0 SErr 0x880800 action 0x6 frozen Apr 3 16:58:32 Tower kernel: ata11: SError: { HostInt 10B8B LinkSeq } Apr 3 16:58:32 Tower kernel: ata11.00: failed command: WRITE DMA Apr 3 16:58:32 Tower kernel: ata11.00: cmd ca/00:08:4f:c8:02/00:00:00:00:00/e0 tag 0 dma 4096 out Apr 3 16:58:32 Tower kernel: res 40/00:42:00:00:00/00:00:00:00:00/a0 Emask 0x44 (timeout) Apr 3 16:58:32 Tower kernel: ata11.00: status: { DRDY } Apr 3 16:58:32 Tower kernel: ata11: hard resetting link Apr 3 16:58:32 Tower kernel: ata11: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Apr 3 16:58:32 Tower kernel: ata11.00: configured for UDMA/33 Apr 3 16:58:32 Tower kernel: ata11: EH complete Apr 3 16:59:03 Tower kernel: ata11.00: exception Emask 0x40 SAct 0x0 SErr 0x880800 action 0x6 frozen Apr 3 16:59:03 Tower kernel: ata11: SError: { HostInt 10B8B LinkSeq } Apr 3 16:59:03 Tower kernel: ata11.00: failed command: WRITE DMA Apr 3 16:59:03 Tower kernel: ata11.00: cmd ca/00:08:5f:c6:02/00:00:00:00:00/e0 tag 0 dma 4096 out Apr 3 16:59:03 Tower kernel: res 40/00:42:00:00:00/00:00:00:00:00/a0 Emask 0x44 (timeout) Apr 3 16:59:03 Tower kernel: ata11.00: status: { DRDY } Apr 3 16:59:03 Tower kernel: ata11: hard resetting link Apr 3 16:59:03 Tower kernel: ata11: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Apr 3 16:59:03 Tower kernel: ata11.00: configured for UDMA/33 Apr 3 16:59:03 Tower kernel: ata11: EH complete Apr 3 16:59:34 Tower kernel: ata11.00: exception Emask 0x40 SAct 0x0 SErr 0x880800 action 0x6 frozen Apr 3 16:59:34 Tower kernel: ata11: SError: { HostInt 10B8B LinkSeq } Apr 3 16:59:34 Tower kernel: ata11.00: failed command: WRITE DMA Apr 3 16:59:34 Tower kernel: ata11.00: cmd ca/00:08:3f:c5:02/00:00:00:00:00/e0 tag 0 dma 4096 out Apr 3 16:59:34 Tower kernel: res 40/00:42:00:00:00/00:00:00:00:00/a0 Emask 0x44 (timeout) Apr 3 16:59:34 Tower kernel: ata11.00: status: { DRDY } Apr 3 16:59:34 Tower kernel: ata11: hard resetting link Apr 3 16:59:34 Tower kernel: ata11: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Apr 3 16:59:34 Tower kernel: ata11.00: configured for UDMA/33 Apr 3 16:59:34 Tower kernel: ata11: EH complete I tried smartctl -a -A /dev/sdk >/boot/smart.txt but the command hasn't responded.

Was happily watching a movie via Plex when all of a sudden the server became unresponsive. Rebooted and still the same, the admin panel time outs. Can access the box via telnet and mount shares. The syslog shows plenty of errors on disk4. Can someone confirm its just a single disk? Why is this preventing me from loading up the admin panel? unRaid 5.0.5. Mods made are simple features, sab, sick beard. Apr 3 16:36:17 Tower kernel: Descriptor sense data with sense descriptors (in hex): Apr 3 16:36:17 Tower kernel: 72 0b 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00 Apr 3 16:36:17 Tower kernel: 00 00 00 00 Apr 3 16:36:17 Tower kernel: sd 10:0:0:0: [sdk] Apr 3 16:36:17 Tower kernel: ASC=0x0 ASCQ=0x0 Apr 3 16:36:17 Tower kernel: sd 10:0:0:0: [sdk] CDB: Apr 3 16:36:17 Tower kernel: cdb[0]=0x28: 28 00 00 02 23 cf 00 04 00 00 Apr 3 16:36:17 Tower kernel: end_request: I/O error, dev sdk, sector 140239 Apr 3 16:36:17 Tower kernel: md: disk4 read error, sector=140176 Apr 3 16:36:17 Tower kernel: md: disk4 read error, sector=140184 Apr 3 16:36:17 Tower kernel: md: disk4 read error, sector=140192 Apr 3 16:36:17 Tower kernel: md: disk4 read error, sector=140200 Apr 3 16:36:17 Tower kernel: md: disk4 read error, sector=140208 Apr 3 16:36:17 Tower kernel: ata11: EH complete Apr 3 16:36:17 Tower kernel: md: disk4 read error, sector=140216 Apr 3 16:36:17 Tower kernel: md: disk4 read error, sector=140224 Apr 3 16:36:17 Tower kernel: md: disk4 read error, sector=140232 Apr 3 16:36:17 Tower kernel: md: disk4 read error, sector=140240 Apr 3 16:36:17 Tower kernel: md: disk4 read error, sector=140248 Apr 3 16:36:17 Tower kernel: md: disk4 read error, sector=140256 Apr 3 16:36:17 Tower kernel: md: disk4 read error, sector=140264 Apr 3 16:36:17 Tower kernel: md: disk4 read error, sector=140272 Apr 3 16:36:17 Tower kernel: md: disk4 read error, sector=140280 Apr 3 16:36:17 Tower kernel: md: disk4 read error, sector=140288 Apr 3 16:36:17 Tower kernel: md: disk4 read error, sector=140296 Apr 3 16:36:17 Tower kernel: md: disk4 read error, sector=140304 Apr 3 16:36:17 Tower kernel: md: disk4 read error, sector=140312 Apr 3 16:36:17 Tower kernel: md: disk4 read error, sector=140320 Apr 3 16:36:17 Tower kernel: md: disk4 read error, sector=140328 Apr 3 16:36:17 Tower kernel: md: disk4 read error, sector=140336 Apr 3 16:36:17 Tower kernel: md: disk4 read error, sector=140344 Apr 3 16:36:17 Tower kernel: md: disk4 read error, sector=140352 Apr 3 16:36:17 Tower kernel: md: disk4 read error, sector=140360 Apr 3 16:36:17 Tower kernel: md: disk4 read error, sector=140368 Apr 3 16:36:17 Tower kernel: md: disk4 read error, sector=140376 Apr 3 16:36:17 Tower kernel: md: disk4 read error, sector=140384 Apr 3 16:36:17 Tower kernel: md: disk4 read error, sector=140392 Apr 3 16:36:17 Tower kernel: md: disk4 read error, sector=140400 Apr 3 16:36:17 Tower kernel: md: disk4 read error, sector=140408 Apr 3 16:36:17 Tower kernel: md: disk4 read error, sector=140416 Apr 3 16:36:17 Tower kernel: md: disk4 read error, sector=140424 Apr 3 16:36:17 Tower kernel: md: disk4 read error, sector=140432 Apr 3 16:36:17 Tower kernel: md: disk4 read error, sector=140440 Apr 3 16:36:17 Tower kernel: md: disk4 read error, sector=140448 Apr 3 16:36:17 Tower kernel: md: disk4 read error, sector=140456 Apr 3 16:36:17 Tower kernel: md: disk4 read error, sector=140464 Apr 3 16:36:17 Tower kernel: md: disk4 read error, sector=140472 Apr 3 16:36:17 Tower kernel: md: disk4 read error, sector=140480 Apr 3 16:36:17 Tower kernel: md: disk4 read error, sector=140488 Apr 3 16:36:17 Tower kernel: md: disk4 read error, sector=140496 Apr 3 16:36:17 Tower kernel: md: disk4 read error, sector=140504 Apr 3 16:36:17 Tower kernel: md: disk4 read error, sector=140512 Apr 3 16:36:17 Tower kernel: md: disk4 read error, sector=140520 Apr 3 16:36:17 Tower kernel: md: disk4 read error, sector=140528 Apr 3 16:36:17 Tower kernel: md: disk4 read error, sector=140536 Apr 3 16:36:17 Tower kernel: md: disk4 read error, sector=140544 Apr 3 16:36:17 Tower kernel: md: disk4 read error, sector=140552 Apr 3 16:36:17 Tower kernel: md: disk4 read error, sector=140560 Apr 3 16:36:17 Tower kernel: md: disk4 read error, sector=140568 Apr 3 16:36:17 Tower kernel: md: disk4 read error, sector=140576 Apr 3 16:36:17 Tower kernel: md: disk4 read error, sector=140584 Apr 3 16:36:17 Tower kernel: md: disk4 read error, sector=140592 Apr 3 16:36:17 Tower kernel: md: disk4 read error, sector=140600 Apr 3 16:36:17 Tower kernel: md: disk4 read error, sector=140608 Apr 3 16:36:17 Tower kernel: md: disk4 read error, sector=140616 Apr 3 16:36:17 Tower kernel: md: disk4 read error, sector=140624 Apr 3 16:36:17 Tower kernel: md: disk4 read error, sector=140632 Apr 3 16:36:17 Tower kernel: md: disk4 read error, sector=140640 Apr 3 16:36:17 Tower kernel: md: disk4 read error, sector=140648 Apr 3 16:36:17 Tower kernel: md: disk4 read error, sector=140656 Apr 3 16:36:17 Tower kernel: md: disk4 read error, sector=140664 Apr 3 16:36:17 Tower kernel: md: disk4 read error, sector=140672 Apr 3 16:36:17 Tower kernel: md: disk4 read error, sector=140680 Apr 3 16:36:17 Tower kernel: md: disk4 read error, sector=140688 Apr 3 16:36:17 Tower kernel: md: disk4 read error, sector=140696 Apr 3 16:36:17 Tower kernel: md: disk4 read error, sector=140704 Apr 3 16:36:17 Tower kernel: md: disk4 read error, sector=140712 Apr 3 16:36:17 Tower kernel: md: disk4 read error, sector=140720 Apr 3 16:36:17 Tower kernel: md: disk4 read error, sector=140728 Apr 3 16:36:17 Tower kernel: md: disk4 read error, sector=140736 Apr 3 16:36:17 Tower kernel: md: disk4 read error, sector=140744 Apr 3 16:36:17 Tower kernel: md: disk4 read error, sector=140752 Apr 3 16:36:17 Tower kernel: md: disk4 read error, sector=140760 Apr 3 16:36:17 Tower kernel: md: disk4 read error, sector=140768 Apr 3 16:36:17 Tower kernel: md: disk4 read error, sector=140776 Apr 3 16:36:17 Tower kernel: md: disk4 read error, sector=140784 Apr 3 16:36:17 Tower kernel: md: disk4 read error, sector=140792 Apr 3 16:36:17 Tower kernel: md: disk4 read error, sector=140800 Apr 3 16:36:17 Tower kernel: md: disk4 read error, sector=140808 Apr 3 16:36:17 Tower kernel: md: disk4 read error, sector=140816 Apr 3 16:36:17 Tower kernel: md: disk4 read error, sector=140824 Apr 3 16:36:17 Tower kernel: md: disk4 read error, sector=140832 Apr 3 16:36:17 Tower kernel: md: disk4 read error, sector=140840 Apr 3 16:36:17 Tower kernel: md: disk4 read error, sector=140848 Apr 3 16:36:17 Tower kernel: md: disk4 read error, sector=140856 Apr 3 16:36:17 Tower kernel: md: disk4 read error, sector=140864 Apr 3 16:36:17 Tower kernel: md: disk4 read error, sector=140872 Apr 3 16:36:17 Tower kernel: md: disk4 read error, sector=140880 Apr 3 16:36:17 Tower kernel: md: disk4 read error, sector=140888 Apr 3 16:36:17 Tower kernel: md: disk4 read error, sector=140896 Apr 3 16:36:17 Tower kernel: md: disk4 read error, sector=140904 Apr 3 16:36:17 Tower kernel: md: disk4 read error, sector=140912 Apr 3 16:36:17 Tower kernel: md: disk4 read error, sector=140920 Apr 3 16:36:17 Tower kernel: md: disk4 read error, sector=140928 Apr 3 16:36:17 Tower kernel: md: disk4 read error, sector=140936 Apr 3 16:36:17 Tower kernel: md: disk4 read error, sector=140944 Apr 3 16:36:17 Tower kernel: md: disk4 read error, sector=140952 Apr 3 16:36:17 Tower kernel: md: disk4 read error, sector=140960 Apr 3 16:36:17 Tower kernel: md: disk4 read error, sector=140968 Apr 3 16:36:17 Tower kernel: md: disk4 read error, sector=140976 Apr 3 16:36:17 Tower kernel: md: disk4 read error, sector=140984 Apr 3 16:36:17 Tower kernel: md: disk4 read error, sector=140992 Apr 3 16:36:17 Tower kernel: md: disk4 read error, sector=141000 Apr 3 16:36:17 Tower kernel: md: disk4 read error, sector=141008 Apr 3 16:36:17 Tower kernel: md: disk4 read error, sector=141016 Apr 3 16:36:17 Tower kernel: md: disk4 read error, sector=141024 Apr 3 16:36:17 Tower kernel: md: disk4 read error, sector=141032 Apr 3 16:36:17 Tower kernel: md: disk4 read error, sector=141040 Apr 3 16:36:17 Tower kernel: md: disk4 read error, sector=141048 Apr 3 16:36:17 Tower kernel: md: disk4 read error, sector=141056 Apr 3 16:36:17 Tower kernel: md: disk4 read error, sector=141064 Apr 3 16:36:17 Tower kernel: md: disk4 read error, sector=141072 Apr 3 16:36:17 Tower kernel: md: disk4 read error, sector=141080 Apr 3 16:36:17 Tower kernel: md: disk4 read error, sector=141088 Apr 3 16:36:17 Tower kernel: md: disk4 read error, sector=141096 Apr 3 16:36:17 Tower kernel: md: disk4 read error, sector=141104 Apr 3 16:36:17 Tower kernel: md: disk4 read error, sector=141112 Apr 3 16:36:17 Tower kernel: md: disk4 read error, sector=141120 Apr 3 16:36:17 Tower kernel: md: disk4 read error, sector=141128 Apr 3 16:36:17 Tower kernel: md: disk4 read error, sector=141136 Apr 3 16:36:17 Tower kernel: md: disk4 read error, sector=141144 Apr 3 16:36:17 Tower kernel: md: disk4 read error, sector=141152 Apr 3 16:36:17 Tower kernel: md: disk4 read error, sector=141160 Apr 3 16:36:17 Tower kernel: md: disk4 read error, sector=141168 Apr 3 16:36:17 Tower kernel: md: disk4 read error, sector=141176 Apr 3 16:36:17 Tower kernel: md: disk4 read error, sector=141184 Apr 3 16:36:17 Tower kernel: md: disk4 read error, sector=141192 Apr 3 16:36:17 Tower kernel: ata11.00: exception Emask 0x50 SAct 0x0 SErr 0x280900 action 0x6 frozen Apr 3 16:36:17 Tower kernel: ata11.00: irq_stat 0x08000000, interface fatal error Apr 3 16:36:17 Tower kernel: ata11: SError: { UnrecovData HostInt 10B8B BadCRC } Apr 3 16:36:17 Tower kernel: ata11.00: failed command: READ DMA Apr 3 16:36:17 Tower kernel: ata11.00: cmd c8/00:00:cf:27:02/00:00:00:00:00/e0 tag 0 dma 131072 in Apr 3 16:36:17 Tower kernel: res 50/00:02:00:00:00/00:00:00:00:00/a0 Emask 0x50 (ATA bus error) Apr 3 16:36:17 Tower kernel: ata11.00: status: { DRDY } Apr 3 16:36:17 Tower kernel: ata11: hard resetting link Apr 3 16:36:18 Tower kernel: ata11: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Apr 3 16:36:18 Tower kernel: ata11.00: configured for UDMA/33 Apr 3 16:36:18 Tower kernel: ata11: EH complete Apr 3 16:36:18 Tower kernel: ata11.00: exception Emask 0x50 SAct 0x0 SErr 0x280900 action 0x6 frozen Apr 3 16:36:18 Tower kernel: ata11.00: irq_stat 0x08000000, interface fatal error Apr 3 16:36:18 Tower kernel: ata11: SError: { UnrecovData HostInt 10B8B BadCRC } Apr 3 16:36:18 Tower kernel: ata11.00: failed command: READ DMA Apr 3 16:36:18 Tower kernel: ata11.00: cmd c8/00:00:cf:27:02/00:00:00:00:00/e0 tag 0 dma 131072 in Apr 3 16:36:18 Tower kernel: res 50/00:02:00:00:00/00:00:00:00:00/a0 Emask 0x50 (ATA bus error) Apr 3 16:36:18 Tower kernel: ata11.00: status: { DRDY } Apr 3 16:36:18 Tower kernel: ata11: hard resetting link Apr 3 16:36:18 Tower kernel: ata11: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Apr 3 16:36:18 Tower kernel: ata11.00: configured for UDMA/33 Apr 3 16:36:18 Tower kernel: ata11: EH complete Apr 3 16:36:18 Tower kernel: ata11.00: exception Emask 0x50 SAct 0x0 SErr 0x280900 action 0x6 frozen Apr 3 16:36:18 Tower kernel: ata11.00: irq_stat 0x08000000, interface fatal error Apr 3 16:36:18 Tower kernel: ata11: SError: { UnrecovData HostInt 10B8B BadCRC } Apr 3 16:36:18 Tower kernel: ata11.00: failed command: READ DMA Apr 3 16:36:18 Tower kernel: ata11.00: cmd c8/00:00:cf:27:02/00:00:00:00:00/e0 tag 0 dma 131072 in Apr 3 16:36:18 Tower kernel: res 50/00:02:00:00:00/00:00:00:00:00/a0 Emask 0x50 (ATA bus error) Apr 3 16:36:18 Tower kernel: ata11.00: status: { DRDY } Apr 3 16:36:18 Tower kernel: ata11: hard resetting link Apr 3 16:36:19 Tower kernel: ata11: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Apr 3 16:36:19 Tower kernel: ata11.00: configured for UDMA/33 Apr 3 16:36:19 Tower kernel: ata11: EH complete Apr 3 16:36:19 Tower kernel: ata11.00: exception Emask 0x50 SAct 0x0 SErr 0x280900 action 0x6 frozen Apr 3 16:36:19 Tower kernel: ata11.00: irq_stat 0x08000000, interface fatal error Apr 3 16:36:19 Tower kernel: ata11: SError: { UnrecovData HostInt 10B8B BadCRC } Apr 3 16:36:19 Tower kernel: ata11.00: failed command: READ DMA Apr 3 16:36:19 Tower kernel: ata11.00: cmd c8/00:00:cf:27:02/00:00:00:00:00/e0 tag 0 dma 131072 in Apr 3 16:36:19 Tower kernel: res 50/00:02:00:00:00/00:00:00:00:00/a0 Emask 0x50 (ATA bus error) Apr 3 16:36:19 Tower kernel: ata11.00: status: { DRDY } Apr 3 16:36:19 Tower kernel: ata11: hard resetting link Apr 3 16:36:19 Tower kernel: ata11: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Apr 3 16:36:19 Tower kernel: ata11.00: configured for UDMA/33 Apr 3 16:36:19 Tower kernel: ata11: EH complete Apr 3 16:36:19 Tower kernel: ata11.00: exception Emask 0x50 SAct 0x0 SErr 0x280900 action 0x6 frozen Apr 3 16:36:19 Tower kernel: ata11.00: irq_stat 0x08000000, interface fatal error Apr 3 16:36:19 Tower kernel: ata11: SError: { UnrecovData HostInt 10B8B BadCRC } Apr 3 16:36:19 Tower kernel: ata11.00: failed command: READ DMA Apr 3 16:36:19 Tower kernel: ata11.00: cmd c8/00:00:cf:27:02/00:00:00:00:00/e0 tag 0 dma 131072 in Apr 3 16:36:19 Tower kernel: res 50/00:02:00:00:00/00:00:00:00:00/a0 Emask 0x50 (ATA bus error) Apr 3 16:36:19 Tower kernel: ata11.00: status: { DRDY } Apr 3 16:36:19 Tower kernel: ata11: hard resetting link Apr 3 16:36:20 Tower kernel: ata11: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Apr 3 16:36:20 Tower kernel: ata11.00: configured for UDMA/33 Apr 3 16:36:20 Tower kernel: ata11: EH complete Apr 3 16:36:20 Tower kernel: ata11.00: exception Emask 0x50 SAct 0x0 SErr 0x280900 action 0x6 frozen Apr 3 16:36:20 Tower kernel: ata11.00: irq_stat 0x08000000, interface fatal error Apr 3 16:36:20 Tower kernel: ata11: SError: { UnrecovData HostInt 10B8B BadCRC } Apr 3 16:36:20 Tower kernel: ata11.00: failed command: READ DMA Apr 3 16:36:20 Tower kernel: ata11.00: cmd c8/00:00:cf:27:02/00:00:00:00:00/e0 tag 0 dma 131072 in Apr 3 16:36:20 Tower kernel: res 50/00:02:00:00:00/00:00:00:00:00/a0 Emask 0x50 (ATA bus error) Apr 3 16:36:20 Tower kernel: ata11.00: status: { DRDY } Apr 3 16:36:20 Tower kernel: ata11: hard resetting link Apr 3 16:36:21 Tower kernel: ata11: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Apr 3 16:36:21 Tower kernel: ata11.00: configured for UDMA/33 Apr 3 16:36:21 Tower kernel: sd 10:0:0:0: [sdk] Apr 3 16:36:21 Tower kernel: Result: hostbyte=0x00 driverbyte=0x08 Apr 3 16:36:21 Tower kernel: sd 10:0:0:0: [sdk] Apr 3 16:36:21 Tower kernel: Sense Key : 0xb [current] [descriptor] Apr 3 16:36:21 Tower kernel: Descriptor sense data with sense descriptors (in hex): Apr 3 16:36:21 Tower kernel: 72 0b 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00 Apr 3 16:36:21 Tower kernel: 00 00 00 00 Apr 3 16:36:21 Tower kernel: sd 10:0:0:0: [sdk] Apr 3 16:36:21 Tower kernel: ASC=0x0 ASCQ=0x0 Apr 3 16:36:21 Tower kernel: sd 10:0:0:0: [sdk] CDB: Apr 3 16:36:21 Tower kernel: cdb[0]=0x28: 28 00 00 02 27 cf 00 01 00 00 Apr 3 16:36:21 Tower kernel: end_request: I/O error, dev sdk, sector 141263 Apr 3 16:36:21 Tower kernel: md: disk4 read error, sector=141200 Apr 3 16:36:21 Tower kernel: ata11: EH complete

From Intel I've been running Plex for about 5 years and its only now with different devices like ATV and iPads and those that access our library remotely where the hardware is starting to show its age. I don't need integrated graphics on an unRaid box, just the ability to process multiple streams. Also having the ability to benefit from the Xeon's VT features would be useful further down the line.

You considered the Xeon processors (E3 family) as they have features specifically for transcoding according to Intel's website plus virtualization features. I'm also considering wiring in more ethernet. We have one ATV that is on ethernet and because Plex serves the file in DirectPlay it doesn't do anything to the processor. Certainly a way for me to get more out of the current hardware I have (Core 2 Duo).

Hey all, I've happily been running a well used Plex media server on a 2.66ghz intel core 2 duo with 4 gb ram for 3 years or so. With the addition of more devices and friends viewing the library remotely the box is doing more transcoding. For the most part its fine except when you want to watch something and someone else is transcoding a film remotely then it seems to struggle. A single film transcoding to an iPad makes the cpu spike to 100% constantly. I've seen some Intel Core 2 Quad Q9650's on ebay and wondered whether this would be a good way to go? I'm trying to avoid upgrading the whole motherboard etc. Will unRaid or Plex media server make use of the extra cores?

Is the Lian Li D8000 the best option of 20+ disk case if you don't want a rack case? Thing is I noticed its discontinued on New Egg. I currently have 11 disks, I can fit one more in at a push - don't want to go to two boxes plus I'd like to eventually go virtualized.

Hadn't even thought of those! That might work to as well as longer psi cables from moddiy.com

Hey All, Been happily running unRaid with 11 disks for 3 years or so (9 data) but running out of room and weighing up upgrade options. My current case can accommodate 15 drives via 4/3 caddies but my PSU only supports 12 sata connections. Right now a PSU that can do 16 sata is $330, the price of a Norco case. So, does the number of supported sata connections by my psu (Corsair 750w 80 Golf Plus) become redundant in a Norco 4220 box because the PSU is powering the backplane instead of connections to individual drives? I'm looking to add another 2 or 3 data drives that I have spare.