Swixxy

I assume by 'implemented' you mean can it run? And of course it can, its just a python script, much like sabnzbd, sickbeard etc are. It should be as simple as running the command 'python path/to/beets.py import /mnt/Music/' or whatever (i dont use beets, i just got those arguments from their github) If ive missed the point i appologize, the question just wasnt that clear to me.

Anybody know of a similar service on the pc? I use 'For the Record' at the moment to record TV shows, however its naming has something left to be desired since the EPG doesn't know the episode title, season number or episode number! Making it almost impossible for me to convert it into a compatible format for xbmc. This seems like the perfect thing to patch in, be able to feed a video file & it outputs the tvdb link (or the format to use Show Name.SXX.EXX) Anybody know of anything similar? This has seriously sparked my interest, and short of hooking it up to my phone to run automatically ( ;D Ultimate hackjob) i'd love to be able to do this.

Hello i'm not that familiar with creating users for use with ssh, how would i go about doing this? Also i've needed to change the sshd_config to set AllowGateways to yes, however when the package restarts this entry is removed and i have to edit it (and then reboot ssh again) every time. Sorry, i know this is probably all really simple stuff, but hopefully it wont take long to point me in the right Direction. Thanks

That wouldn't be a problem to do, however note that unless you have very memory intensive addons running, or a very low RAM set then a swap file will hardly ever be used and as such isn't really worth it all that much. I'm also pretty certain it should be ReiserFS however i'm not 100%, best to make a thread about it before proceeding (as most people will only check this thread for xbmc related things)

using it as a drive outside of the array seems like the best choice, if it was inside the array the parity drive writes would slow it down, making the fact its an SSD fairly pointless. Your best bet is to have it as a drive outside the array, and create a cron job to backup the database to your array, backing up thumbnails seems like a waste of space as they are fairly easy to recover, but obviously which shows you've watched/haven't watched etc isn't.

Thanks a lot Joe, so if i backup whats left on the disk and then run the preclear script on the cache drive it should (in theory) try to correct the bad sectors? If so, would there be any indication in the preclear script whether it has found and corrected them (or failed to) or should i perform a SMART report afterwards to see if any problems remain?

Sorry to bump this but its extremely important as if my cache drive is failing I need to know whether to purchase one to replace it asap or not, as my cache drive is used for quite a few things!

Think it has to do with my cache drive. (sda) the cache drive becomes unresponsive every so often recently (i expect at the same time this started happening) Is the drive dying or is this something fixable such as a bad sector on the drive? Any help would be much appreciated! Syslog is too large to upload, here is the trouble part (i think?) Nov 22 01:11:29 jbox kernel: ata1: EH complete Nov 22 01:11:31 jbox unmenu[13900]: bad method - 2407980 34750810 297356975 56133570 601143 32055797 261256552 17183970 0 27389270 733163502407980-^M Nov 22 01:11:31 jbox last message repeated 32 times Nov 22 01:11:32 jbox kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Nov 22 01:11:32 jbox kernel: ata1.00: BMDMA stat 0x65 Nov 22 01:11:32 jbox kernel: ata1.00: failed command: READ DMA EXT Nov 22 01:11:32 jbox kernel: ata1.00: cmd 25/00:08:20:5d:b8/00:00:a4:00:00/e0 tag 0 dma 4096 in Nov 22 01:11:32 jbox kernel: res 51/40:08:20:5d:b8/40:00:a4:00:00/e0 Emask 0x9 (media error) Nov 22 01:11:32 jbox kernel: ata1.00: status: { DRDY ERR } Nov 22 01:11:32 jbox kernel: ata1.00: error: { UNC } Nov 22 01:11:32 jbox kernel: ata1.00: configured for UDMA/33 Nov 22 01:11:32 jbox kernel: ata1.01: configured for UDMA/133 Nov 22 01:11:32 jbox kernel: ata1: EH complete Nov 22 01:11:35 jbox kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Nov 22 01:11:35 jbox kernel: ata1.00: BMDMA stat 0x65 Nov 22 01:11:35 jbox kernel: ata1.00: failed command: READ DMA EXT Nov 22 01:11:35 jbox kernel: ata1.00: cmd 25/00:08:20:5d:b8/00:00:a4:00:00/e0 tag 0 dma 4096 in Nov 22 01:11:35 jbox kernel: res 51/40:08:20:5d:b8/40:00:a4:00:00/e0 Emask 0x9 (media error) Nov 22 01:11:35 jbox kernel: ata1.00: status: { DRDY ERR } Nov 22 01:11:35 jbox kernel: ata1.00: error: { UNC } Nov 22 01:11:35 jbox kernel: ata1.00: configured for UDMA/33 Nov 22 01:11:35 jbox kernel: ata1.01: configured for UDMA/133 Nov 22 01:11:35 jbox kernel: ata1: EH complete Nov 22 01:11:37 jbox unmenu[13900]: bad method - 2407980 34750810 297356975 56133570 601143 32055797 261256552 17183970 0 27389270 733163502407980-^M Nov 22 01:11:37 jbox last message repeated 32 times Nov 22 01:11:38 jbox kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Nov 22 01:11:38 jbox kernel: ata1.00: BMDMA stat 0x65 Nov 22 01:11:38 jbox kernel: ata1.00: failed command: READ DMA EXT Nov 22 01:11:38 jbox kernel: ata1.00: cmd 25/00:08:20:5d:b8/00:00:a4:00:00/e0 tag 0 dma 4096 in Nov 22 01:11:38 jbox kernel: res 51/40:08:20:5d:b8/40:00:a4:00:00/e0 Emask 0x9 (media error) Nov 22 01:11:38 jbox kernel: ata1.00: status: { DRDY ERR } Nov 22 01:11:38 jbox kernel: ata1.00: error: { UNC } Nov 22 01:11:38 jbox kernel: ata1.00: configured for UDMA/33 Nov 22 01:11:38 jbox kernel: ata1.01: configured for UDMA/133 Nov 22 01:11:38 jbox kernel: ata1: EH complete Nov 22 01:11:41 jbox kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Nov 22 01:11:41 jbox kernel: ata1.00: BMDMA stat 0x65 Nov 22 01:11:41 jbox kernel: ata1.00: failed command: READ DMA EXT Nov 22 01:11:41 jbox kernel: ata1.00: cmd 25/00:08:20:5d:b8/00:00:a4:00:00/e0 tag 0 dma 4096 in Nov 22 01:11:41 jbox kernel: res 51/40:08:20:5d:b8/40:00:a4:00:00/e0 Emask 0x9 (media error) Nov 22 01:11:41 jbox kernel: ata1.00: status: { DRDY ERR } Nov 22 01:11:41 jbox kernel: ata1.00: error: { UNC } Nov 22 01:11:41 jbox kernel: ata1.00: configured for UDMA/33 Nov 22 01:11:41 jbox kernel: ata1.01: configured for UDMA/133 Nov 22 01:11:41 jbox kernel: ata1: EH complete Nov 22 01:11:43 jbox unmenu[13900]: bad method - 2407980 34750810 297356975 56133570 601143 32055797 261256552 17183970 0 27389270 733163502407980-^M Nov 22 01:11:43 jbox last message repeated 32 times Nov 22 01:11:43 jbox kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Nov 22 01:11:43 jbox kernel: ata1.00: BMDMA stat 0x65 Nov 22 01:11:43 jbox kernel: ata1.00: failed command: READ DMA EXT Nov 22 01:11:43 jbox kernel: ata1.00: cmd 25/00:08:20:5d:b8/00:00:a4:00:00/e0 tag 0 dma 4096 in Nov 22 01:11:43 jbox kernel: res 51/40:08:20:5d:b8/40:00:a4:00:00/e0 Emask 0x9 (media error) Nov 22 01:11:43 jbox kernel: ata1.00: status: { DRDY ERR } Nov 22 01:11:43 jbox kernel: ata1.00: error: { UNC } Nov 22 01:11:43 jbox kernel: ata1.00: configured for UDMA/33 Nov 22 01:11:43 jbox kernel: ata1.01: configured for UDMA/133 Nov 22 01:11:43 jbox kernel: sd 1:0:0:0: [sda] Unhandled sense code Nov 22 01:11:43 jbox kernel: sd 1:0:0:0: [sda] Result: hostbyte=0x00 driverbyte=0x08 Nov 22 01:11:43 jbox kernel: sd 1:0:0:0: [sda] Sense Key : 0x3 [current] [descriptor] Nov 22 01:11:43 jbox kernel: Descriptor sense data with sense descriptors (in hex): Nov 22 01:11:43 jbox kernel: 72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00 Nov 22 01:11:43 jbox kernel: a4 b8 5d 20 Nov 22 01:11:43 jbox kernel: sd 1:0:0:0: [sda] ASC=0x11 ASCQ=0x4 Nov 22 01:11:43 jbox kernel: sd 1:0:0:0: [sda] CDB: cdb[0]=0x28: 28 00 a4 b8 5d 20 00 00 08 00 Nov 22 01:11:43 jbox kernel: end_request: I/O error, dev sda, sector 2763545888 Nov 22 01:11:43 jbox kernel: Buffer I/O error on device sda1, logical block 345443228 Nov 22 01:11:43 jbox kernel: ata1: EH complete Nov 22 01:11:46 jbox kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Nov 22 01:11:46 jbox kernel: ata1.00: BMDMA stat 0x65 Nov 22 01:11:46 jbox kernel: ata1.00: failed command: READ DMA EXT Nov 22 01:11:46 jbox kernel: ata1.00: cmd 25/00:08:20:5d:b8/00:00:a4:00:00/e0 tag 0 dma 4096 in Nov 22 01:11:46 jbox kernel: res 51/40:08:20:5d:b8/40:00:a4:00:00/e0 Emask 0x9 (media error) Nov 22 01:11:46 jbox kernel: ata1.00: status: { DRDY ERR } Nov 22 01:11:46 jbox kernel: ata1.00: error: { UNC } Nov 22 01:11:46 jbox kernel: ata1.00: configured for UDMA/33 Nov 22 01:11:46 jbox kernel: ata1.01: configured for UDMA/133 Nov 22 01:11:46 jbox kernel: ata1: EH complete Nov 22 01:11:49 jbox kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Nov 22 01:11:49 jbox kernel: ata1.00: BMDMA stat 0x65 Nov 22 01:11:49 jbox kernel: ata1.00: failed command: READ DMA EXT Nov 22 01:11:49 jbox kernel: ata1.00: cmd 25/00:08:20:5d:b8/00:00:a4:00:00/e0 tag 0 dma 4096 in Nov 22 01:11:49 jbox kernel: res 51/40:08:20:5d:b8/40:00:a4:00:00/e0 Emask 0x9 (media error) Nov 22 01:11:49 jbox kernel: ata1.00: status: { DRDY ERR } Nov 22 01:11:49 jbox kernel: ata1.00: error: { UNC } Nov 22 01:11:49 jbox kernel: ata1.00: configured for UDMA/33 Nov 22 01:11:49 jbox kernel: ata1.01: configured for UDMA/133 Nov 22 01:11:49 jbox kernel: ata1: EH complete Nov 22 01:11:50 jbox unmenu[13900]: bad method - 2407980 34750810 297356975 56133570 601143 32055797 261256552 17183970 0 27389270 733163502407980-^M Nov 22 01:11:50 jbox last message repeated 33 times Nov 22 01:11:52 jbox kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Nov 22 01:11:52 jbox kernel: ata1.00: BMDMA stat 0x65 Nov 22 01:11:52 jbox kernel: ata1.00: failed command: READ DMA EXT Nov 22 01:11:52 jbox kernel: ata1.00: cmd 25/00:08:20:5d:b8/00:00:a4:00:00/e0 tag 0 dma 4096 in Nov 22 01:11:52 jbox kernel: res 51/40:08:20:5d:b8/40:00:a4:00:00/e0 Emask 0x9 (media error) Nov 22 01:11:52 jbox kernel: ata1.00: status: { DRDY ERR } Nov 22 01:11:52 jbox kernel: ata1.00: error: { UNC } Nov 22 01:11:52 jbox kernel: ata1.00: configured for UDMA/33 Nov 22 01:11:52 jbox kernel: ata1.01: configured for UDMA/133 Nov 22 01:11:52 jbox kernel: ata1: EH complete Nov 22 01:11:55 jbox kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Nov 22 01:11:55 jbox kernel: ata1.00: BMDMA stat 0x65 Nov 22 01:11:55 jbox kernel: ata1.00: failed command: READ DMA EXT Nov 22 01:11:55 jbox kernel: ata1.00: cmd 25/00:08:20:5d:b8/00:00:a4:00:00/e0 tag 0 dma 4096 in Nov 22 01:11:55 jbox kernel: res 51/40:08:20:5d:b8/40:00:a4:00:00/e0 Emask 0x9 (media error) Nov 22 01:11:55 jbox kernel: ata1.00: status: { DRDY ERR } Nov 22 01:11:55 jbox kernel: ata1.00: error: { UNC } Nov 22 01:11:55 jbox kernel: ata1.00: configured for UDMA/33 Nov 22 01:11:55 jbox kernel: ata1.01: configured for UDMA/133 Nov 22 01:11:55 jbox kernel: ata1: EH complete Nov 22 01:11:56 jbox unmenu[13900]: bad method - 2407980 34750810 297356975 56133570 601143 32055797 261256552 17183970 0 27389270 733163502407980-^M Nov 22 01:11:56 jbox last message repeated 32 times Nov 22 01:11:58 jbox kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Nov 22 01:11:58 jbox kernel: ata1.00: BMDMA stat 0x65 Nov 22 01:11:58 jbox kernel: ata1.00: failed command: READ DMA EXT Nov 22 01:11:58 jbox kernel: ata1.00: cmd 25/00:08:20:5d:b8/00:00:a4:00:00/e0 tag 0 dma 4096 in Nov 22 01:11:58 jbox kernel: res 51/40:08:20:5d:b8/40:00:a4:00:00/e0 Emask 0x9 (media error) Nov 22 01:11:58 jbox kernel: ata1.00: status: { DRDY ERR } Nov 22 01:11:58 jbox kernel: ata1.00: error: { UNC } Nov 22 01:11:58 jbox kernel: ata1.00: configured for UDMA/33 Nov 22 01:11:58 jbox kernel: ata1.01: configured for UDMA/133 Nov 22 01:11:58 jbox kernel: ata1: EH complete Nov 22 01:12:00 jbox kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Nov 22 01:12:00 jbox kernel: ata1.00: BMDMA stat 0x65 Nov 22 01:12:00 jbox kernel: ata1.00: failed command: READ DMA EXT Nov 22 01:12:00 jbox kernel: ata1.00: cmd 25/00:08:20:5d:b8/00:00:a4:00:00/e0 tag 0 dma 4096 in Nov 22 01:12:00 jbox kernel: res 51/40:08:20:5d:b8/40:00:a4:00:00/e0 Emask 0x9 (media error) Nov 22 01:12:00 jbox kernel: ata1.00: status: { DRDY ERR } Nov 22 01:12:00 jbox kernel: ata1.00: error: { UNC } Nov 22 01:12:00 jbox kernel: ata1.00: configured for UDMA/33 Nov 22 01:12:00 jbox kernel: ata1.01: configured for UDMA/133 Nov 22 01:12:00 jbox kernel: sd 1:0:0:0: [sda] Unhandled sense code Nov 22 01:12:00 jbox kernel: sd 1:0:0:0: [sda] Result: hostbyte=0x00 driverbyte=0x08 Nov 22 01:12:00 jbox kernel: sd 1:0:0:0: [sda] Sense Key : 0x3 [current] [descriptor] Nov 22 01:12:00 jbox kernel: Descriptor sense data with sense descriptors (in hex): Nov 22 01:12:00 jbox kernel: 72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00 Nov 22 01:12:00 jbox kernel: a4 b8 5d 20 Nov 22 01:12:00 jbox kernel: sd 1:0:0:0: [sda] ASC=0x11 ASCQ=0x4 Nov 22 01:12:00 jbox kernel: sd 1:0:0:0: [sda] CDB: cdb[0]=0x28: 28 00 a4 b8 5d 20 00 00 08 00 Nov 22 01:12:00 jbox kernel: end_request: I/O error, dev sda, sector 2763545888 Nov 22 01:12:00 jbox kernel: Buffer I/O error on device sda1, logical block 345443228 Nov 22 01:12:00 jbox kernel: ata1: EH complete Nov 22 01:12:02 jbox unmenu[13900]: bad method - 2407980 34750810 297356975 56133570 601143 32055797 261256552 17183970 0 27389270 733163502407980-^M Nov 22 01:12:02 jbox last message repeated 32 times Nov 22 01:12:06 jbox kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Nov 22 01:12:06 jbox kernel: ata1.00: BMDMA stat 0x65 Nov 22 01:12:06 jbox kernel: ata1.00: failed command: READ DMA EXT Nov 22 01:12:06 jbox kernel: ata1.00: cmd 25/00:08:e0:d4:b8/00:00:a4:00:00/e0 tag 0 dma 4096 in Nov 22 01:12:06 jbox kernel: res 51/40:08:e0:d4:b8/40:00:a4:00:00/e0 Emask 0x9 (media error) Nov 22 01:12:06 jbox kernel: ata1.00: status: { DRDY ERR } Nov 22 01:12:06 jbox kernel: ata1.00: error: { UNC } Nov 22 01:12:06 jbox kernel: ata1.00: configured for UDMA/33 Nov 22 01:12:06 jbox kernel: ata1.01: configured for UDMA/133 Nov 22 01:12:06 jbox kernel: ata1: EH complete Nov 22 01:12:09 jbox kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Nov 22 01:12:09 jbox kernel: ata1.00: BMDMA stat 0x65 Nov 22 01:12:09 jbox kernel: ata1.00: failed command: READ DMA EXT Nov 22 01:12:09 jbox kernel: ata1.00: cmd 25/00:08:e0:d4:b8/00:00:a4:00:00/e0 tag 0 dma 4096 in Nov 22 01:12:09 jbox kernel: res 51/40:08:e0:d4:b8/40:00:a4:00:00/e0 Emask 0x9 (media error) Nov 22 01:12:09 jbox kernel: ata1.00: status: { DRDY ERR } Nov 22 01:12:09 jbox kernel: ata1.00: error: { UNC } Nov 22 01:12:09 jbox kernel: ata1.00: configured for UDMA/33 Nov 22 01:12:09 jbox kernel: ata1.01: configured for UDMA/133 Nov 22 01:12:09 jbox kernel: ata1: EH complete Nov 22 01:12:09 jbox unmenu[13900]: bad method - 2407980 34750810 297356975 56133570 601143 32055797 261256552 17183970 0 27389270 733163502407980-^M Nov 22 01:12:09 jbox last message repeated 33 times Nov 22 01:12:11 jbox kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Nov 22 01:12:11 jbox kernel: ata1.00: BMDMA stat 0x65 Nov 22 01:12:11 jbox kernel: ata1.00: failed command: READ DMA EXT Nov 22 01:12:11 jbox kernel: ata1.00: cmd 25/00:08:e0:d4:b8/00:00:a4:00:00/e0 tag 0 dma 4096 in Nov 22 01:12:11 jbox kernel: res 51/40:08:e0:d4:b8/40:00:a4:00:00/e0 Emask 0x9 (media error) Nov 22 01:12:11 jbox kernel: ata1.00: status: { DRDY ERR } Nov 22 01:12:11 jbox kernel: ata1.00: error: { UNC } Nov 22 01:12:11 jbox kernel: ata1.00: configured for UDMA/33 Nov 22 01:12:12 jbox kernel: ata1.01: configured for UDMA/133 Nov 22 01:12:12 jbox kernel: ata1: EH complete Nov 22 01:12:14 jbox kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Nov 22 01:12:14 jbox kernel: ata1.00: BMDMA stat 0x65 Nov 22 01:12:14 jbox kernel: ata1.00: failed command: READ DMA EXT Nov 22 01:12:14 jbox kernel: ata1.00: cmd 25/00:08:e0:d4:b8/00:00:a4:00:00/e0 tag 0 dma 4096 in Nov 22 01:12:14 jbox kernel: res 51/40:08:e0:d4:b8/40:00:a4:00:00/e0 Emask 0x9 (media error) Nov 22 01:12:14 jbox kernel: ata1.00: status: { DRDY ERR } Nov 22 01:12:14 jbox kernel: ata1.00: error: { UNC } Nov 22 01:12:14 jbox kernel: ata1.00: configured for UDMA/33 Nov 22 01:12:14 jbox kernel: ata1.01: configured for UDMA/133 Nov 22 01:12:14 jbox kernel: ata1: EH complete Nov 22 01:12:15 jbox unmenu[13900]: bad method - 2407980 34750810 297356975 56133570 601143 32055797 261256552 17183970 0 27389270 733163502407980-^M Nov 22 01:12:15 jbox last message repeated 32 times Nov 22 01:12:17 jbox kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Nov 22 01:12:17 jbox kernel: ata1.00: BMDMA stat 0x65 Nov 22 01:12:17 jbox kernel: ata1.00: failed command: READ DMA EXT Nov 22 01:12:17 jbox kernel: ata1.00: cmd 25/00:08:e0:d4:b8/00:00:a4:00:00/e0 tag 0 dma 4096 in Nov 22 01:12:17 jbox kernel: res 51/40:08:e0:d4:b8/40:00:a4:00:00/e0 Emask 0x9 (media error) Nov 22 01:12:17 jbox kernel: ata1.00: status: { DRDY ERR } Nov 22 01:12:17 jbox kernel: ata1.00: error: { UNC } Nov 22 01:12:17 jbox kernel: ata1.00: configured for UDMA/33 Nov 22 01:12:17 jbox kernel: ata1.01: configured for UDMA/133 Nov 22 01:12:17 jbox kernel: ata1: EH complete

Hey thanks a lot for lending your expertise. Got another error unfortunately though, root@jbox:/boot/ffmpeg-HEAD-a7e5679# ./configure --enable-gpl --enable-nonfree --enable-postproc --enable-pthreads --enable-libmp3lame --enable-libx264 --enable-libxvid --enable-x11grab --disable-shared --enable-static; ERROR: libx264 version must be >= 0.118. If you think configure made a mistake, make sure you are using the latest version from Git. If the latest version fails, report the problem to the [email protected] mailing list or IRC #ffmpeg on irc.freenode.net. Include the log file "config.log" produced by configure as this will help solving the problem. So i suppose i have to compile libx264 as well? I have it downloaded from their git, however following instructions online to compile it for unraid seems to fail. I assume as you have libx264 in your arguments you also compiled it yourself? A step like before for libx264 would be great! (Sorry to be a pain!)

Hey, has anybody compiled ffmpeg to a binary file that could give me some pointers? I've tried using the slackware pkg ( http://connie.slackware.com/~alien/slackbuilds/ffmpeg/pkg/13.37/ffmpeg-0.8.6-i486-1alien.tgz ) the pkg seems to install fine using installpkg however i'm at a bit of a loss to the whereabouts of the ffmpeg binary file? The reason I'm after doing this is because the latest subsonic build uses a newer ffmpeg, however my ffmpeg is out dated and i cant find a prebuild file to replace it with anywhere. I'm pretty good with linux knowledge in general, i just haven't had much practice at compiling things & dealing with things of this nature, and as its running on my unraid box i don't want to risk running into problems by mistake! Many thanks

Has anybody upgraded ffmpeg? Been using subsonic with no problems for ages and now i recently upgraded to the new subsonic build (4.6b1) and since then it seems to be using a newer ffmpeg version than i have (says -preset argument is invalid in debug log etc) as the transcoding string has changed. Is there an easy way to upgrade ffmpeg to a newer version?

This is what i'm doing at the moment, however i have about 100~ TV shows, so moving them around takes quite a lot of time! Just seems silly that there is no 'ignore Split-Level if drive is full' option in unraid, would just be an if statement more or less in the code - Yet would remove the need for me to manually move files about every few months to avoid my cache drive filling up

Yes i mean split-level sorry. Edited. I just mean while the idea behind split level is a great idea as generally you don't want to spin up 2 disks just to watch one thing, if the disk that the split level is saying to use is full, then I think there should be an option to have it split across to another disk. My problem: My TV shows automatically get added to different disks, if i have 10 active shows on the same disk then by the time the disk fills up, some shows are still airing meaning their episodes are left on the cache disk with nowhere to go, as the disk is full. Somebody must have had this problem also? The only way to fix it is manually move the TV show folders across, which means checking every show folder to see which season folder it contains, and whether theres any new episodes and if so, moving it to a different drive. That's a lot of effort every time a drive fills, and with more drives = even more time consumed going through them

So the drive works in another bay? And other drives work in bay that the 'faulty' drive doesn't work in?

Hey guys, just a quick question. I Recently filled up all of my drives and have just added another drive to the array, all went through with no problems. However, i currently have my split-level setting for TV shows set at 2 TV -Show Name --Season Number ---Episode.ext However, as the other drives are full (all showing as zero free space in unraid) will i need to move the Season folders for the shows that are still updating to my new drive? Or will unraid see that the drive with the correct season is full and so create the TV/Show Name/Season Number/ folder on another drive and fill it that way as a fail-safe? If not, is there any way to enable this? I Love split-level as i tend to watch a few episodes of a show at a time, meaning the other drives can remain spun down - However if a drive fills up, i'd like it to be able to put the files onto a drive that is empty as a failsafe, rather than just not moving it. Is this the case? Thanks

Hello all, I just have a quick question in regards to moving my current production unraid server to be running off of an ESXi server. My server is running perfectly fine at the moment, all set up and running flawlessly however i would like to be able to run a few VM's on the box that i can't run alongside unraid at present, such as a virtualised desktop so i can setup some thin clients around the house, rather than each family member requiring a high powered computer to run effectively. However i only currently have the one unraid server, which has at present 6TB of media (Movies tv shows etc) as well as subsonic, sabnzbd, couchpotato, sickbeard, headphones and a minecraft server all set up and running perfectly fine. I've been reading about how to get it working, however providing i disconnect the hard drives and so on, would it really be a case of just installing it and then plugging unraid back in? (More or less) without risk of unraid deciding the drives are incorrect? Or would there be a real risk of data loss. While i see that ESXi is overkill for the use at the moment, something like VMware server seems to involve changing the unraid kernel and general tinkering that goes beyond the scope of looking up documentation online, something that i feel is beyond me. Anybody had any experience doing this or something similar that they can share how well it went? (Or what to watch out for!)

I currently have a system with 3TB drives (have drive as my parity so downgrading isn't an easy option) However my controller card is the AOC-SASLP-MV8 which is currently having issues. What cards are you guys using on the latest beta? and any downsides to them?

It might, but if you only have 6 drives then I suggest taking the card out entirely, until you need it. It was just in as a breakout cable for a 4 in 3 cage seemed a lot neater than 4 sata cables going across the mobo Thanks, and final question: If i got sata cables and plugged them straight into sata ports would it still recognize the drives in the correct positions (parity etc?) or will i have to unassign all drives prior to disconnect and then reassign them

If i were to disconnect the drives from the Supermicro AOC-SASLP-MV8 and connect them to the mobo sata connectors woudl this temporarily fix the issue? I only have 6 drives in total so i have enough ports without the card for the time being

I have a 3TB drive hooked up for my parity, is there any other option? e.g patching the drivers? or any tips for what to look for to possibly try and fix the problem myself? or is it literally just a, can't do anything until a fix is supplied

I've got the INT13 off and now i can spin down my drives, however this SAS error is still occuring. I've connected to my unraid box from work, however i can't reboot the server (was going to use the file manager to copy/paste it into a txt document) is there any way i can download a file to my local machine via telnet? This problem has made unraid unuseable for me, as it 'crashes' and all shares etc becoem unresponsive within a day! Makes the spouse very unhappy! haha

Sorry, just read the post regarding controllers and realised iv'e missed a step when setting up these cards Would this INT13 bios setting be the problem?

Today i woke up and my unraid servers webui is not responding, neither are any of the shares I can telnet into the machine, but thats about as far as it gets. I forced a reset on my box before i could grab the syslog (Stupid i know!) however i was viewing it at the time through telnet in vi so managed to just ctrl-c the screen at the time and managed to get the important bit Sep 21 20:47:01 jbox logger: ### subsonic_delete_thumbs_ram.sh ### Sep 21 21:26:54 jbox kernel: sas: command 0xf5f219c0, task 0xf74efcc0, timed out Sep 21 21:26:54 jbox kernel: sas: command 0xf5df8d80, task 0xefb3b900, timed out Sep 21 21:26:54 jbox kernel: sas: trying to find task 0xf74efcc0 Sep 21 21:26:54 jbox kernel: sas: sas_scsi_find_task: aborting task 0xf74efcc0 Sep 21 21:26:54 jbox kernel: drivers/scsi/mvsas/mv_sas.c 1818:<7>mv_abort_task() Sep 21 21:26:54 jbox kernel: drivers/scsi/mvsas/mv_sas.c 1747:mvs_query_task:rc= Sep 21 21:26:54 jbox kernel: sas: I_T nexus reset for dev 010U: I_T recoverd to Sep 21 21:26:54 jbox kernel: drivers/scsi/mvsas/mv_sas.c 2198:port 1 ctrl sts=0x Sep 21 21:26:54 jbox kernel: drivers/scsi/mvsas/mv_sas.c 2200:Port 1 irq sts = 0 Sep 21 21:26:54 jbox kernel: drivers/scsi/mvsas/mv_sas.c 2226:phy1 Unplug Notice Sep 21 21:26:54 jbox kernel: drivers/scsi/mvsas/mv_sas.c 2198:port 1 ctrl sts=0x Sep 21 21:26:54 jbox kernel: drivers/scsi/mvsas/mv_sas.c 2200:Port 1 irq sts = 0 Sep 21 21:26:54 jbox kernel: drivers/scsi/mvsas/mv_sas.c 2198:port 1 ctrl sts=0x Sep 21 21:26:54 jbox kernel: drivers/scsi/mvsas/mv_sas.c 2200:Port 1 irq sts = 0 Sep 21 21:26:54 jbox kernel: sas: sas_form_port: phy1 belongs to port1 already(1 Sep 21 21:26:57 jbox kernel: drivers/scsi/mvsas/mv_sas.c 1701:mvs_I_T_nexus_rese Sep 21 21:26:57 jbox kernel: sas: sas_ata_task_done: SAS error 8d Sep 21 21:26:57 jbox kernel: sas: trying to find task 0xefb3b900 Sep 21 21:26:57 jbox kernel: sas: sas_scsi_find_task: aborting task 0xefb3b900 Sep 21 21:26:57 jbox kernel: sas: sas_scsi_find_task: task 0xefb3b900 is done Sep 21 21:26:57 jbox kernel: sas: sas_eh_handle_sas_errors: task 0xefb3b900 is d Sep 21 21:26:57 jbox kernel: ata5: sas eh calling libata port error handler [78dSep 21 21:26:57 jbox kernel: ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 Sep 21 21:26:57 jbox kernel: ata5.00: res 01/04:ff:00:00:00/00:00:00:00:00/40 Em Sep 21 21:26:57 jbox kernel: ata5.00: error: { ABRT } Sep 21 21:26:57 jbox kernel: ata5: hard resetting link Sep 21 21:26:57 jbox kernel: sas: sas_ata_hard_reset: Found ATA device. Sep 21 21:26:57 jbox kernel: ata5.00: configured for UDMA/133 Sep 21 21:26:57 jbox kernel: ata5: EH complete Sep 21 21:26:57 jbox kernel: ata6: sas eh calling libata port error handler Sep 21 21:26:57 jbox kernel: ata6.00: exception Emask 0x0 SAct 0x0 SErr 0x0 acti Sep 21 21:26:57 jbox kernel: ata6.00: res 01/04:ff:00:00:00/00:00:00:00:00/40 Em Sep 21 21:26:57 jbox kernel: ata6.00: error: { ABRT } Sep 21 21:26:57 jbox kernel: ata6: hard resetting link Sep 21 21:26:57 jbox kernel: drivers/scsi/mvsas/mv_sas.c 2198:port 1 ctrl sts=0x Sep 21 21:26:57 jbox kernel: drivers/scsi/mvsas/mv_sas.c 2200:Port 1 irq sts = 0 Sep 21 21:26:57 jbox kernel: drivers/scsi/mvsas/mv_sas.c 2226:phy1 Unplug Notice Sep 21 21:26:57 jbox kernel: drivers/scsi/mvsas/mv_sas.c 2198:port 1 ctrl sts=0x Sep 21 21:26:57 jbox kernel: drivers/scsi/mvsas/mv_sas.c 2200:Port 1 irq sts = 0 Sep 21 21:26:57 jbox kernel: drivers/scsi/mvsas/mv_sas.c 2278:plugin interrupt b Sep 21 21:26:59 jbox kernel: drivers/scsi/mvsas/mv_sas.c 2139:phy1 Attached Devi Sep 21 21:26:59 jbox kernel: drivers/scsi/mvsas/mv_sas.c 2198:port 1 ctrl sts=0x Sep 21 21:26:59 jbox kernel: drivers/scsi/mvsas/mv_sas.c 2200:Port 1 irq sts = 0 Sep 21 21:26:59 jbox kernel: drivers/scsi/mvsas/mv_sas.c 2226:phy1 Unplug Notice Sep 21 21:26:59 jbox kernel: drivers/scsi/mvsas/mv_sas.c 2198:port 1 ctrl sts=0x Sep 21 21:26:59 jbox kernel: drivers/scsi/mvsas/mv_sas.c 2200:Port 1 irq sts = 0 Sep 21 21:26:59 jbox kernel: drivers/scsi/mvsas/mv_sas.c 2198:port 1 ctrl sts=0x Sep 21 21:26:59 jbox kernel: drivers/scsi/mvsas/mv_sas.c 2200:Port 1 irq sts = 0 Sep 21 21:26:59 jbox kernel: sas: sas_form_port: phy1 belongs to port1 already(1 Sep 21 21:26:59 jbox kernel: drivers/scsi/mvsas/mv_sas.c 1701:mvs_I_T_nexus_rese Sep 21 21:26:59 jbox kernel: ata6.00: configured for UDMA/133TA device. Sep 21 21:26:59 jbox kernel: ata6: EH complete Sep 21 21:26:59 jbox kernel: ata7: sas eh calling libata port error handler Sep 21 21:26:59 jbox kernel: ata8: sas eh calling libata port error handler Sep 21 21:26:59 jbox kernel: sas: --- Exit sas_scsi_recover_host Sep 21 21:42:49 jbox kernel: sas: command 0xf5f21c00, task 0xf74efcc0, timed out Sep 21 21:42:49 jbox kernel: sas: command 0xf02e6b40, task 0xf75cd900, timed out Sep 21 22:40:58 jbox in.telnetd[4959]: connect from ** (** Sep 21 22:41:12 jbox login[496[31d[35d LOGIN on '/dev/pts/1' from '** Sep 21 22:47:01 jbox logge[36d## subso[40ddelete_thumbs_ram.sh ###ot Sep 21 23:47:02 jbox logger: ### subsonic_delete_thumbs_ram.sh ### [78dSep 22 00:17:08 jbox in.telnetd[5044]: connect from **(** Sep 22 00:17:12 jbox login[5045]: ROOT LOGIN on '/dev/pts/2' from '** Sep 22 00:23:17 jbox in.telnetd[5065]: connect from 194.129.65.79 (** Sep 22 00:23:23 jbox login[5066]: ROOT LOGIN on '/dev/pts/2' from ** Sep 22 00:26:47 jbox e[46dp: unRAID System[50dagement Utility version 5.0-beta12 Sep 22 00:26:47 jb[51dmhttp: Pro key detected,[55dD: 0951-1643-330F-FB70E605229C Sep 22 00:39:28 jbox in.telnetd[5109]: connect from** (** Sep 22 0[65d[A[57dox login[5110]: invalid password for 'root' on '/dev/pts/3' f Sep 22 00:39:43 jbox in.telnetd[5111]: connect fro[** (** Sep 22 00:39:47 jbox login[5112]: invalid password for[67d[b' on '/dev/pts/3' f [76d[72d0:39:52 jbox login[5112]: ROOT LOGIN on '/dev/pts/3[78dom note: telnet was still responsive, however nothing else was (webui etc etc), at the bottom of the log you see me attempt to restart emhttp - which didnt work. Is this a problem with my Supermicro AOC-SASLP-MV8, 8-Port SAS/SATA 300MB/s PCI-e Controller Card I currently have two of these in the system, i had a problem with this card where my drives were unable to spin back up again, but i've disabled drives spinning down

Whenever i start unmenu up and navigate to the page, my unraid webui crashes (and unmenu stops responding) the syslog shows nothing but unmenu status: starting unmenu web-server unmenu loads up, then the bottom part of the page shows 'page cannot be loaded' and from then on, the entire thing is unresponsive. Note: i was performing a parity check when this happened. All web servers etc seem to be down too (python based servers not responsive either) Any clues? i can still telnet in perfectly fine

So that i can scan through my media using sickbeard, couchpotato etc to rebuild the list, is there a path i can point to that is essentially the user share? I was thinking /mnt/user/TV however i've noticed you also get user0, user1 etc? Are these just all ghosts of the share and safe to point at? or are they created when a user requests an smb share?