tucansam

I have disk high temp set at 42F, critical set at 48F -- no spinner ever gets past 41, even in the summer during a parity check. I have two m2 SSDs, and one of them alters to a high temp (44F) every single day. I'm not sure what its dong (trim?) but its happening consistently. The google machine says an SSD can operate up to 50F happily. How can I set SSD temp alarms separately from mechanical disk temp alarms?

Got it working, not sure how. But MAN, this is WAY more complicated than it was a decade ago when I ran an old version on an old linux. I have no idea how to begin doing this. I've managed to set up the source, an can see it. The camera itself handles motion detection, and films in 30s clips, which is fine. I literally just need the camera to write videos to my unraid server instead of the SD card in it. Nothing more complicated than that.

ZM never connects, unable to access GUI

Docker -> ZM Icon -> "WebGUI" Also tried directly inputting the URL and port, both http and https No change, does not work. Same error.

Yep. Tried it. Fresh install, I'm getting this: ZoneMinder Error Unable to connect to ZM db using dsn mysql:host=localhost;dbname=zm;charset=utf8 SQLSTATE[HY000] [2002] No such file or directory ZoneMinder will retry connection in 25 seconds. I've tried about 8 different CCTV/RTSP apps from the app center under unraid. They either flat-out don't work, won't start, 404 on their supposed GUIs....

Fresh install, unable to open the GUI.

Edited conf file, set password. Got it to start, at least. 404 errors on all attempts to access gui, whether host, bridge, br0, etc. cannot connect.

I have a camera that I want to use via RTSP, and I'd like to set up unraid as an RTSP server. I see five apps in the application community that are available. Four seem to be purpose and/or brand specific, and the one that appears to work generically is in beta. Can anyone recommend an RTSP server app for unraid that will work with most/all IP cams? Thanks.

Sab is suddenly placing TV shows in the main share ("/mnt/tv_shows") instead of the show/season folder ("mnt/tv_shows/show1") This is new behavior as of a couple hours ago, haven't had this issue in more than half a decade. I've checked, re-checked, and checked again all the paths, switches, checkboxes, etc. I'm not sure what else to look for. ETA Is it sonarr that is doing the moving? I've never been able to get this straight. Does the download client sort and move, or does sonarr/radarr? I've checked settings there too, can't find anything wrong.

No idea whatsoever what that even means, but I'm off to research.

I don't know any other way. What's the best method?

Unfortunately docker won't let me set the appdata path. I'm in the docker tab in the web gui. I was able to set the path to "/mnt/disks/ssd1/docker.img" for the docker file, but its giving me a "path doesn't exist" error for "/mnt/disks/ssd2/appdata." When I browse from that form field, it only shows me directories in /mnt/user -- it will only look to the array for an appdata path. Is it possible to store the appdata on an ssd mounted with unassigned devices, not in the user shares?

You're backing up appdata daily? How many docker applications are you running? My appdata directory is 102GB, and the Plex instance alone is several million files. I'm backing it up weekly. Five or six dockers running, the usual suspects I suppose. And docker.img is not super critical? Where is the config data for each (sab, plex, etc) stored -- appdata or in the docker.img file?

I've had the exact same problem since day one, years upon years now. It really only makes a difference when I try to move files between drives or folders. I get permission denied errors and either have to go to the shell prompt to chmod/chown or use docker safe new permissions. All of my media that gets downloaded suffers the same thing, movies, music, TV shows.

I've finally upgraded my server after 10+ years. My final task is to copy the contents of an old Evo 850 SSD to two new m.2 SSDs. Is it worth placing docker.img and appdata on different SSDs, for the sake of performance? Thanks.

Happened to notice that sab hadn't downloaded a tv show in weeks. Movies are fine. Sonarr, under activity, has every entry with a yellow clock next to it that say "Pending -- Download client is unavailable." Not sure where to begin troubleshooting -- literally no setting has changed in my setup in almost a decade. Clicking "Test" in settings give me a green check mark. Ideas welcome. ETA Looking at the config page under Radarr, it exactly mirrors Sonarr. Yet Sonarr will not work.

ddrescue worked! I was able to decrypt, and then mount, the resulting image file. looks like more than 99% of my data is in tact.

First I'd be trying anything like this. Any chance there are guides online?

Thank you Jorge. I realize this is purely speculative, but would it be worth a try to buy an exact same disk and use the logic board from it on the old disk, to see if that keeps it up long enough to recover data? ddrescue has run all night and is showing that its about 75% complete, and it claims it has recovered some data. I guess we'll see when it finishes. A four-hour ETA for finishing turned into almost 12, and it still not done.

This is what I get when I try to mount a disk I need to get some info off of: -- Nov 13 18:34:09 ffs1 kernel: ata2: SATA max UDMA/133 abar m2048@0xf7d36000 port 0xf7d36180 irq 27 Nov 13 18:34:09 ffs1 kernel: ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Nov 13 18:34:09 ffs1 kernel: ata2.00: NCQ Send/Recv Log not supported Nov 13 18:34:09 ffs1 kernel: ata2.00: ATA-9: ST3000VN000-1HJ166, W6A0TZ31, SC60, max UDMA/133 Nov 13 18:34:09 ffs1 kernel: ata2.00: 5860533168 sectors, multi 0: LBA48 NCQ (depth 32), AA Nov 13 18:34:09 ffs1 kernel: ata2.00: NCQ Send/Recv Log not supported Nov 13 18:34:09 ffs1 kernel: ata2.00: configured for UDMA/133 Nov 13 18:34:09 ffs1 kernel: sd 2:0:0:0: [sdb] 5860533168 512-byte logical blocks: (3.00 TB/2.73 TiB) Nov 13 18:34:09 ffs1 kernel: sd 2:0:0:0: [sdb] 4096-byte physical blocks Nov 13 18:34:09 ffs1 kernel: sd 2:0:0:0: [sdb] Write Protect is off Nov 13 18:34:09 ffs1 kernel: sd 2:0:0:0: [sdb] Mode Sense: 00 3a 00 00 Nov 13 18:34:09 ffs1 kernel: sd 2:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Nov 13 18:34:09 ffs1 kernel: sdb: sdb1 Nov 13 18:34:09 ffs1 kernel: sd 2:0:0:0: [sdb] Attached SCSI disk Nov 13 18:34:38 ffs1 emhttpd: ST3000VN000-1HJ166_W6A0TZ31 (sdb) 512 5860533168 Nov 13 18:34:38 ffs1 emhttpd: read SMART /dev/sdb Nov 13 18:36:41 ffs1 unassigned.devices: Disk with ID 'ST3000VN000-1HJ166_W6A0TZ31 (sdb)' is not set to auto mount. Nov 13 18:36:50 ffs1 emhttpd: shcmd (154): /usr/sbin/cryptsetup luksOpen /dev/sdb1 W6A0TZ31 Nov 13 18:37:19 ffs1 kernel: ata2.00: READ LOG DMA EXT failed, trying PIO Nov 13 18:37:19 ffs1 kernel: ata2: failed to read log page 10h (errno=-5) Nov 13 18:37:19 ffs1 kernel: ata2.00: exception Emask 0x1 SAct 0xf SErr 0x0 action 0x0 Nov 13 18:37:19 ffs1 kernel: ata2.00: irq_stat 0x40000001 Nov 13 18:37:19 ffs1 kernel: ata2.00: failed command: WRITE FPDMA QUEUED Nov 13 18:37:19 ffs1 kernel: ata2.00: cmd 61/02:00:41:80:00/00:00:00:00:00/40 tag 0 ncq dma 1024 out Nov 13 18:37:19 ffs1 kernel: ata2.00: status: { DRDY DF ERR } Nov 13 18:37:19 ffs1 kernel: ata2.00: error: { ABRT } Nov 13 18:37:19 ffs1 kernel: ata2.00: failed command: WRITE FPDMA QUEUED Nov 13 18:37:19 ffs1 kernel: ata2.00: cmd 61/20:08:48:80:00/00:00:00:00:00/40 tag 1 ncq dma 16384 out Nov 13 18:37:19 ffs1 kernel: ata2.00: status: { DRDY DF ERR } Nov 13 18:37:19 ffs1 kernel: ata2.00: error: { ABRT } Nov 13 18:37:19 ffs1 kernel: ata2.00: failed command: WRITE FPDMA QUEUED Nov 13 18:37:19 ffs1 kernel: ata2.00: cmd 61/20:10:c0:40:51/00:00:22:00:00/40 tag 2 ncq dma 16384 out Nov 13 18:37:19 ffs1 kernel: ata2.00: status: { DRDY DF ERR } Nov 13 18:37:19 ffs1 kernel: ata2.00: error: { ABRT } Nov 13 18:37:19 ffs1 kernel: ata2.00: failed command: WRITE FPDMA QUEUED Nov 13 18:37:19 ffs1 kernel: ata2.00: cmd 61/20:18:60:2a:6b/00:00:22:00:00/40 tag 3 ncq dma 16384 out Nov 13 18:37:19 ffs1 kernel: ata2.00: status: { DRDY DF ERR } Nov 13 18:37:19 ffs1 kernel: ata2.00: error: { ABRT } Nov 13 18:37:19 ffs1 kernel: ata2.00: both IDENTIFYs aborted, assuming NODEV Nov 13 18:37:19 ffs1 kernel: ata2.00: revalidation failed (errno=-2) Nov 13 18:37:19 ffs1 kernel: ata2: hard resetting link Nov 13 18:37:25 ffs1 kernel: ata2: link is slow to respond, please be patient (ready=0) Nov 13 18:37:27 ffs1 kernel: ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Nov 13 18:37:27 ffs1 kernel: ata2.00: both IDENTIFYs aborted, assuming NODEV Nov 13 18:37:27 ffs1 kernel: ata2.00: revalidation failed (errno=-2) Nov 13 18:37:32 ffs1 kernel: ata2: hard resetting link Nov 13 18:37:38 ffs1 kernel: ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Nov 13 18:37:38 ffs1 kernel: ata2.00: both IDENTIFYs aborted, assuming NODEV Nov 13 18:37:38 ffs1 kernel: ata2.00: revalidation failed (errno=-2) Nov 13 18:37:38 ffs1 kernel: ata2.00: disabled Nov 13 18:37:38 ffs1 kernel: ata2: EH complete Nov 13 18:37:38 ffs1 kernel: sd 2:0:0:0: [sdb] tag#15 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 cmd_age=18s Nov 13 18:37:38 ffs1 kernel: sd 2:0:0:0: [sdb] tag#15 CDB: opcode=0x8a 8a 00 00 00 00 00 22 6b 2a 60 00 00 00 20 00 00 Nov 13 18:37:38 ffs1 kernel: blk_update_request: I/O error, dev sdb, sector 577448544 op 0x1:(WRITE) flags 0x1000 phys_seg 4 prio class 0 Nov 13 18:37:38 ffs1 kernel: sd 2:0:0:0: [sdb] tag#16 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 cmd_age=18s Nov 13 18:37:38 ffs1 kernel: sd 2:0:0:0: [sdb] tag#16 CDB: opcode=0x8a 8a 00 00 00 00 00 22 51 40 c0 00 00 00 20 00 00 Nov 13 18:37:38 ffs1 kernel: blk_update_request: I/O error, dev sdb, sector 575750336 op 0x1:(WRITE) flags 0x1000 phys_seg 4 prio class 0 Nov 13 18:37:38 ffs1 kernel: sd 2:0:0:0: [sdb] tag#17 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 cmd_age=18s Nov 13 18:37:38 ffs1 kernel: sd 2:0:0:0: [sdb] tag#17 CDB: opcode=0x8a 8a 00 00 00 00 00 00 00 80 48 00 00 00 20 00 00 Nov 13 18:37:38 ffs1 kernel: blk_update_request: I/O error, dev sdb, sector 32840 op 0x1:(WRITE) flags 0x1000 phys_seg 4 prio class 0 Nov 13 18:37:38 ffs1 kernel: sd 2:0:0:0: [sdb] tag#18 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 cmd_age=18s Nov 13 18:37:38 ffs1 kernel: sd 2:0:0:0: [sdb] tag#18 CDB: opcode=0x8a 8a 00 00 00 00 00 00 00 80 41 00 00 00 02 00 00 Nov 13 18:37:38 ffs1 kernel: blk_update_request: I/O error, dev sdb, sector 32833 op 0x1:(WRITE) flags 0x1000 phys_seg 2 prio class 0 Nov 13 18:37:38 ffs1 kernel: sd 2:0:0:0: [sdb] tag#19 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 cmd_age=0s Nov 13 18:37:38 ffs1 kernel: sd 2:0:0:0: [sdb] tag#19 CDB: opcode=0x35 35 00 00 00 00 00 00 00 00 00 Nov 13 18:37:38 ffs1 kernel: blk_update_request: I/O error, dev sdb, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0 Nov 13 18:37:38 ffs1 kernel: sd 2:0:0:0: [sdb] tag#20 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 cmd_age=0s Nov 13 18:37:38 ffs1 kernel: sd 2:0:0:0: [sdb] tag#20 CDB: opcode=0x88 88 00 00 00 00 00 00 00 00 40 00 00 00 01 00 00 Nov 13 18:37:38 ffs1 kernel: blk_update_request: I/O error, dev sdb, sector 64 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 Nov 13 18:37:38 ffs1 kernel: sd 2:0:0:0: [sdb] tag#21 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 cmd_age=0s Nov 13 18:37:38 ffs1 kernel: sd 2:0:0:0: [sdb] tag#21 CDB: opcode=0x88 88 00 00 00 00 00 00 00 00 40 00 00 00 01 00 00 Nov 13 18:37:38 ffs1 kernel: blk_update_request: I/O error, dev sdb, sector 64 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 Nov 13 18:37:38 ffs1 kernel: sd 2:0:0:0: [sdb] tag#22 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 cmd_age=0s Nov 13 18:37:38 ffs1 kernel: sd 2:0:0:0: [sdb] tag#22 CDB: opcode=0x88 88 00 00 00 00 00 00 00 00 40 00 00 00 01 00 00 Nov 13 18:37:38 ffs1 kernel: blk_update_request: I/O error, dev sdb, sector 64 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 Nov 13 18:37:38 ffs1 kernel: sd 2:0:0:0: [sdb] tag#23 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 cmd_age=0s Nov 13 18:37:38 ffs1 kernel: sd 2:0:0:0: [sdb] tag#23 CDB: opcode=0x88 88 00 00 00 00 00 00 00 00 50 00 00 00 08 00 00 Nov 13 18:37:38 ffs1 kernel: blk_update_request: I/O error, dev sdb, sector 80 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0 Nov 13 18:37:38 ffs1 kernel: sd 2:0:0:0: [sdb] tag#24 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 cmd_age=0s Nov 13 18:37:38 ffs1 kernel: sd 2:0:0:0: [sdb] tag#24 CDB: opcode=0x88 88 00 00 00 00 00 00 00 00 50 00 00 00 01 00 00 Nov 13 18:37:38 ffs1 kernel: blk_update_request: I/O error, dev sdb, sector 80 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 Nov 13 18:37:38 ffs1 kernel: Buffer I/O error on dev sdb1, logical block 16, async page read Nov 13 18:37:38 ffs1 kernel: Buffer I/O error on dev sdb1, logical block 17, async page read Nov 13 18:37:38 ffs1 kernel: Buffer I/O error on dev sdb1, logical block 18, async page read Nov 13 18:37:38 ffs1 kernel: Buffer I/O error on dev sdb1, logical block 19, async page read Nov 13 18:37:38 ffs1 kernel: Buffer I/O error on dev sdb1, logical block 20, async page read Nov 13 18:37:38 ffs1 kernel: Buffer I/O error on dev sdb1, logical block 21, async page read Nov 13 18:37:38 ffs1 kernel: Buffer I/O error on dev sdb1, logical block 22, async page read Nov 13 18:37:38 ffs1 kernel: Buffer I/O error on dev sdb1, logical block 23, async page read Nov 13 18:37:38 ffs1 kernel: Buffer I/O error on dev sdb1, logical block 16, async page read Nov 13 18:37:38 ffs1 kernel: Buffer I/O error on dev sdb1, logical block 17, async page read -- syslog shows this at the end of the attempt: -- Nov 13 18:37:38 ffs1 kernel: Buffer I/O error on dev sdb1, logical block 20, async page read Nov 13 18:37:38 ffs1 kernel: Buffer I/O error on dev sdb1, logical block 21, async page read Nov 13 18:37:38 ffs1 kernel: Buffer I/O error on dev sdb1, logical block 22, async page read Nov 13 18:37:38 ffs1 kernel: Buffer I/O error on dev sdb1, logical block 23, async page read Nov 13 18:37:38 ffs1 kernel: Buffer I/O error on dev sdb1, logical block 16, async page read Nov 13 18:37:38 ffs1 kernel: Buffer I/O error on dev sdb1, logical block 17, async page read Nov 13 18:37:38 ffs1 unassigned.devices: Mount of 'W6A0TZ31' failed: 'mount: /mnt/disks/W6A0TZ31: can't read superblock on /dev/mapper/W6A0TZ31. ' Nov 13 18:37:38 ffs1 unassigned.devices: Partition 'W6A0TZ31' cannot be mounted. -- I've read about ddrescue, but am uncertain how to proceed. This is a member disk out of an encrypted btrfs array. Can ddrescue still be used to make an attempt at recovery? Thanks.

How do I mount an encrypted disk, either with unassigned devices or manually from the shell prompt? I have older disks from the array that I need to pull data from -- some mount fine, some refuse to mount. I have a few disks that I no longer need, and have used unassigned devices to format encrypted so I can store files there as a cold backup, but they will format but refuse to mount.

I'm quite confused about SATA plug and play. I have an unraid server that I use for backups and general testing. 8 disks on an LSI, and zero disks on the six onboard SATA ports, however those six ports have been used in the past to plug disks in for various purposes. I use unassigned devices to manage disks on those ports. I've successfully plugged in, and mounted and used, disks on those onboard ports while unraid was running. I've also had no reaction from the server whatsoever when I plug disks in. In fact, using the exact same disks, I sometimes get them recognized, and sometimes not. When they are not recognized, a reboot gets them seen by unraid/unassigned devices. I have also used a USB dock for the same purpose, however literally every disk I plug in immediately starts throwing SMART errors, and I believe the USB dock is to blame. I am confused. Does SATA PnP/hot swap work with unraid or not?

End of keyboard-interactive prompts from server Linux 5.10.28-Unraid. root@ffs1:~# more /boot/config/plugins/dynamix/dynamix.plugin.control.cfg ,row4,row6,row10 root@ffs1:~# Now I'm even more confused. I just want to confirm my flash drive is not corrupted, and get this annoying error message to go away.

Thanks. Not government action. I usually take older or broken disks to the shooting range for destruction. But I have a few that are relatively new I may try to sell, or give to friends to repurpose. Just wanted to make sure any private data would be wiped "well enough" if I preclear them first. Thanks.

Fix common problems keeps saying this: Your flash drive has possible corruption on /boot/config/plugins/dynamix/dynamix.plugin.control.cfg. Post your diagnostics in the forum for more assistance More Information Diags attached. ffs1-diagnostics-20221109-1912.zip