tucansam

I realize this could be the host controller, the cable in between, the SAS expander, or the PCIe slot on the server... But I just plugged in 8 disks via a host/SAS expander combo and unraid immediately lost its mind, throwing 10k UDMA errors on some disks and up to 19k UDMA errors on others. All disks attached to the expander chain have the same issue. I used to get these a lot, using 5-in-3 backplanes, and usually fiddling with the SATA cable and/or ignoring the errors completely caused no major issues. But 100% of the disks, at once, and with such a high error count..... I'm nervous about adding any of them to the array at this point. Comments?

They're off.

You mean the thumbnails for movies and show posters? Or individual episodes an scenes? How do I turn them off?

/mnt/disks/ssd/appdata/PlexMediaServer/Library/Application Support/Plex Media Server/Cache/Transcode/Sync+/36266422/61/379844.mp4 /mnt/disks/ssd/appdata/PlexMediaServer/Library/Application Support/Plex Media Server/Cache/Transcode/Sync+/36266422/e8/254825.mp4 These are 700-1000MB each. Are these left over temp files from some failed watching of content? Can I delete them? I'm manually tar'ing my appdata folder and have noticed a ton: root@ffs2:/mnt/disks/ssd/appdata/PlexMediaServer/Library/Application Support/Plex Media Server/Cache# find . * | grep mp4 ./Transcode/Sync+/36266422/61/379844.mp4 ./Transcode/Sync+/36266422/e8/254825.mp4 ./Transcode/Sync+/36266422/5f/14352.mp4 ./Transcode/Sync+/36266422/32/14353.mp4 ./Transcode/Sync+/36266422/4b/14354.mp4 ./Transcode/Sync+/36266422/31/14355.mp4 ./Transcode/Sync+/36266422/e3/256938.mp4 ./Transcode/Sync+/36266422/47/256936.mp4 ./Transcode/Sync+/36266422/fb/256939.mp4 ./Transcode/Sync+/36266422/36/256940.mp4 Transcode/Sync+/36266422/61/379844.mp4 Transcode/Sync+/36266422/e8/254825.mp4 Transcode/Sync+/36266422/5f/14352.mp4 Transcode/Sync+/36266422/32/14353.mp4 Transcode/Sync+/36266422/4b/14354.mp4 Transcode/Sync+/36266422/31/14355.mp4 Transcode/Sync+/36266422/e3/256938.mp4 Transcode/Sync+/36266422/47/256936.mp4 Transcode/Sync+/36266422/fb/256939.mp4 Transcode/Sync+/36266422/36/256940.mp4 root@ffs2:/mnt/disks/ssd/appdata/PlexMediaServer/Library/Application Support/Plex Media Server/Cache#

OK So this still doesn't explain what all those huge files inside my plex directory on the actual appdata disk were for.

So /tmp is RAM, then, and I am free to put stuff there that I don't need to survive a reboot? Stupid question, I know. But before I accidentally fill up my 8GB USB unraid thumb drive I want to be certain. Mine has a lot of stuff in it: root@ffs2:~# ls /tmp ca.backup2/ fix.common.problems/ recycle.bin/ ca_notices/ notifications/ tmux-0/ community.applications/ plugins/ unassigned.devices/ emhttp/ preclear_assigned_disks1 user.scripts/ root@ffs2:~#

Not sure if I understand mappings or not. I think what happens inside a docker image is magic and I don't understand any of it, at all, even a little bit. /mnt/user/temp is a share exported by my unraid server as "temp" across the network, so I guess that would make it a host path, right?

Under Settings -> Transcoder, the "Transcoder temporary directory" is listed as /var/tmp. Correct me if I'm wrong, but that's essentially a non-persistent location on what is essentially a "ram disk?" That is to say, its not anywhere on /boot and its certainly not on my array anywhere. Which doesn't explain why huge files are showing up inside the plex folder under appdata. So I changed it to /mnt/user/temp which is a less than ideal location because its slow, however if it starts creating large files again, the array has enough room that it won't make a huge difference if I don't catch it right away. These files seem like temporary files, should they not be getting deleted by Plex during some maintenance event of some sort?

Disregard. Will not self test. Unable to read any attributes from the drive right now. SMART not in diags either. New disk on order (my spare didn't test well) and will be here tomorrow. Syslog shows write errors etc. Cables appear secure and server hasn't been touched or bumped.

Had a disk throw a red X. Counter on the main screen says 60 errors. I am trying to run an extended SMART test on it. The button greyed out (which I think means it working). DIags attached. ffs2-diagnostics-20210821-1827.zip

Went into raspi-config and under boot options I enabled "Wait for network at boot." Works now. FML.

I've tried _netdev, delay_connect, and x-systemd.after=network-online.target Nothing persists after a reboot.

A post I read elsewhere indicated that the network might not be available during the reading of /etc/fstab.... Since its on wifi, this is highly plausible, no? Interesting, I may investigate that a bit.

I've tried: #//192.168.0.5/temp /home/pi/temp cifs username=pi,password=password,uid=1007,gid=100,dir_mode=0770,file_mode=0770 0 0 #//192.168.0.5/temp /home/pi/temp cifs x-systemd.automount,users,credentials=/home/pi/.smbcred 0 0 //192.168.0.5/temp /home/pi/temp cifs credentials=/home/pi/.smbcred,iocharset=utf8,sec=ntlm 0 0 The last one is from the reference site you linked. The commented one in the middle works with "sudo mount -a" but none will survive a reboot. The first the third throw syntax errors with "sudo mount -a" I've tried about a half dozen other variations that googled turned up, just didn't keep track of them. Funny thing is, I can use just about any syntax or options I want when mounting manually from the command line; they all work. Nothing survives a reboot.

Did it ever work? I have been trying for hours, have tried every incarnation of syntax I can find online, and cannot get it to mount with rear/write access for user "pi" via the mount command, and cannot get the share to mount at all using /etc/fstab

Hey guys, I noticed some giant MP4 files in my plex appdata share..... /mnt/disks/ssd/appdata/PlexMediaServer/Library/Application Support/Plex Media Server/Cache/Transcode/Sync+/36266422/61/379844.mp4 /mnt/disks/ssd/appdata/PlexMediaServer/Library/Application Support/Plex Media Server/Cache/Transcode/Sync+/36266422/e8/254825.mp4 These are 700-1000MB each. Are these left over temp files from some failed watching of content? Can I delete them? I'm manually tar'ing my appdata folder and have noticed a ton: root@ffs2:/mnt/disks/ssd/appdata/PlexMediaServer/Library/Application Support/Plex Media Server/Cache# find . * | grep mp4 ./Transcode/Sync+/36266422/61/379844.mp4 ./Transcode/Sync+/36266422/e8/254825.mp4 ./Transcode/Sync+/36266422/5f/14352.mp4 ./Transcode/Sync+/36266422/32/14353.mp4 ./Transcode/Sync+/36266422/4b/14354.mp4 ./Transcode/Sync+/36266422/31/14355.mp4 ./Transcode/Sync+/36266422/e3/256938.mp4 ./Transcode/Sync+/36266422/47/256936.mp4 ./Transcode/Sync+/36266422/fb/256939.mp4 ./Transcode/Sync+/36266422/36/256940.mp4 Transcode/Sync+/36266422/61/379844.mp4 Transcode/Sync+/36266422/e8/254825.mp4 Transcode/Sync+/36266422/5f/14352.mp4 Transcode/Sync+/36266422/32/14353.mp4 Transcode/Sync+/36266422/4b/14354.mp4 Transcode/Sync+/36266422/31/14355.mp4 Transcode/Sync+/36266422/e3/256938.mp4 Transcode/Sync+/36266422/47/256936.mp4 Transcode/Sync+/36266422/fb/256939.mp4 Transcode/Sync+/36266422/36/256940.mp4 root@ffs2:/mnt/disks/ssd/appdata/PlexMediaServer/Library/Application Support/Plex Media Server/Cache# Safe to delete?

Unable to add shares in 6.9.2. Enter the info, click the button to create the share, nothing happens except my "50gb" is changed to 50000000. Nothing else happens, no browser thinking, nada. Share never gets created. Diags. Thanks. ffs2-diagnostics-20210813-2052.zip

Just picked up a 9200-16E and an 8088-8088 external mini-sas cable for cheap, hope it all goes together and works!

A couple follow ups. The expander that will exist in the JBOD is 3gbps. This is for simple media storage, largely, so I hope that doesn't present a significant bottleneck. The expander has one port on it (externally). I hope that a single port-to-port connection between the server and the JBOD doesn't present a bottleneck. Assuming I can get a 6gbps host adapter cheaply, I assume that if I connect a 6gbps controller to a 3gbps expander, it will work, it will just down-clock to 3gbps? And one final.. Something like an LSI 9200-8E can handle 8 drives, right? Vs a -16 which can handle 16? Or does it not matter, because the expander is taking one external port and converting it two more internal ports? Trying to figure out what sort of internal controller I need to get 15 drives in the JBOD. Thanks.

Hey gang. I just picked up an HP HPE Smart SAS expander (https://h20195.www2.hpe.com/v2/getpdf.aspx/c04111623.pdf?ver=20) to use in a spare tower case I have. I have three 5x drive cages in that tower and I want to support 15 disks in it, connected to my current unraid server. Curious what sort of controller card I will need in the unraid server itself. I've got an LSI in it now, controlling 16 internal disks. Will a second LSI with a simple matching external port, and then cable, get the job done? I'm sure I'm complicating this, it seems pretty straight forward, but I want to make sure I get the correct controller to support an SAS expander in essentially an external JBOD. Thanks.

Months later the server can suddenly see the UPS again.

I upgraded a few months ago, maybe less. I generally check on the system a few times a week, and run the upgrade checker when I remember. No I haven't read the threads.

Yes, sorry. My mistake. I don't ever remember seeing that before. I don't know, I installed Nerd Pack, I'm pretty sure it came with everything. I don't recall choosing. I appreciate the help but I have no idea what this means.

Reboot worked. Now I have /mnt/user and /mnt/user0 which appear to be the same thing W T F This thread looks relevant

I started and stopped the array.... No effect. Will reboot now. Diags attached before I do. ffs2-diagnostics-20210711-1604.zip