a12vman

Members
  • Posts

    137
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

a12vman's Achievements

Apprentice

Apprentice (3/14)

4

Reputation

1

Community Answers

  1. Anyone have any ideas? This is showing up every day around the same time. I am not seeing any issues from anything else. Can any of these identifiers be used to tie back to a specific Docker or Process that is running? kernel: traps: unrar7[5211] trap invalid opcode ip:562a90ff41a1 sp:7fffe2a97c48 error:0 in unrar7[562a90ff1000+4b000]
  2. I am seeing this daily in my syslog: kernel: traps: lsof[13954] general protection fault ip:14b81e3ccc6e sp:9e3ce931b6829a07 error:0 in libc-2.37.so[14b81e3b4000+169000] How do I isolate? mediatower-diagnostics-20240112-1352.zip
  3. Ok my biggest concern is preserving my plex metadata. I changed the docker vdisk and appdata location as below. I enabled docker. Plex now shows as empty. In looking at the filesystem the original plex appdata on the array is unchanged at 4.5GB. It re-created the appdata on cache_nvme as a new install only 4 MB. The other Dockers like Emby & Sonarr have the same issue but others like Deluge & Duplicacy are ok. What did I do wrong?
  4. Can I change Docker Vdisk & Storage Location to run off the array for the time being?
  5. I noticed a few errors on my NVME drive(holds System,Docker,AppData,Domains) after a recent 6.12.6 upgrade.. I picked up a new SSD, formatted it & added as a Cache Drive. Last night I stopped docker & VM services. Went to System,Appdata,Docker,Domains shares & changed secondary storage to Array, Mover action set to Cache-->Array. Kicked off the Mover & let it run overnight. This morning I confirmed the mover wasnt running. Went to the same shares, changed primary storage to Crucial_Cache, set Mover Action to Array-->Cache. Started the Mover. Within minutes it failed. sdi is the new cache drive and filled the system log. When I look at Shares, Appdata and System are Green and living on Array. Docker and Domains show that files are unprotected. Looking at MC I have Docker.img on Mnt\User\Docker. Domains is still on the NVME Cache even though I set action to NVME-->Array. Am I incredibly unlucky with a bad SSD or could I have a problem with the controller? What are my next steps? I don't want to make the problem worse. I do have a full backup of AppData that I took before I started all of this. Dec 30 06:12:07 MediaTower kernel: BTRFS error (device sdi1): bdev /dev/sdi1 errs: wr 6, rd 0, flush 0, corrupt 0, gen 0 Dec 30 06:12:07 MediaTower kernel: BTRFS error (device sdi1): bdev /dev/sdi1 errs: wr 7, rd 0, flush 0, corrupt 0, gen 0 Dec 30 06:12:07 MediaTower kernel: BTRFS error (device sdi1): bdev /dev/sdi1 errs: wr 8, rd 0, flush 0, corrupt 0, gen 0 Dec 30 06:12:07 MediaTower kernel: BTRFS error (device sdi1): mediatower-diagnostics-20231230-0643.zip
  6. mediatower-diagnostics-20231227-0744.zip
  7. I upgraded to 6.12.6 yesterday. The process of starting the Docker Service is generating the error below on this device. It happened yesterday right after the upgrade and again today when I stopped & started the Docker Engine. I reviewed SysLogs from the last 2 weeks, there were no errors on this drive until I upgraded to 6.12.6 Dec 26 13:33:45 MediaTower kernel: nvme0n1: p1 Dec 26 13:33:45 MediaTower kernel: BTRFS: device label cache_nvme devid 1 transid 6847202 /dev/nvme0n1p1 scanned by udevd (1121) Dec 26 13:34:23 MediaTower emhttpd: Samsung_SSD_970_EVO_Plus_1TB_S6S1NG0R843160K (nvme0n1) 512 1953525168 Dec 26 13:34:23 MediaTower emhttpd: import 30 cache device: (nvme0n1) Samsung_SSD_970_EVO_Plus_1TB_S6S1NG0R843160K Dec 26 13:34:23 MediaTower emhttpd: read SMART /dev/nvme0n1 Dec 26 13:36:12 MediaTower emhttpd: shcmd (147): mount -t btrfs -o noatime,space_cache=v2 /dev/nvme0n1p1 /mnt/cache_nvme Dec 26 13:36:12 MediaTower kernel: BTRFS info (device nvme0n1p1): using crc32c (crc32c-intel) checksum algorithm Dec 26 13:36:12 MediaTower kernel: BTRFS info (device nvme0n1p1): using free space tree Dec 26 13:36:12 MediaTower kernel: BTRFS info (device nvme0n1p1): enabling ssd optimizations Dec 26 13:36:12 MediaTower kernel: BTRFS info (device nvme0n1p1: state M): turning on async discard Dec 26 14:53:55 MediaTower kernel: nvme0n1: I/O Cmd(0x2) @ LBA 294821792, 32 blocks, I/O Error (sct 0x2 / sc 0x81) MORE DNR Dec 26 14:53:55 MediaTower kernel: critical medium error, dev nvme0n1, sector 294821792 op 0x0:(READ) flags 0x1000 phys_seg 1 prio class 2 Dec 27 01:01:39 MediaTower root: /mnt/cache_nvme: 718.8 GiB (771819671552 bytes) trimmed on /dev/nvme0n1p1 Dec 27 06:48:35 MediaTower kernel: nvme0n1: I/O Cmd(0x2) @ LBA 294821792, 32 blocks, I/O Error (sct 0x2 / sc 0x81) MORE DNR Dec 27 06:48:35 MediaTower kernel: critical medium error, dev nvme0n1, sector 294821792 op 0x0:(READ) flags 0x1000 phys_seg 1 prio class 2
  8. I removed the drive from historical devices. Plugged it back in and set the Mount Share=Yes. It shows up correctly and I can access the drive.
  9. I just finished upgrading from 6.11 --> 6.12.6 and have UD 2023.12.15 Plugin. Everything is good with one exception. I have an unassigned device, it's a portable hard drive connected to the Server's USB Port. This is the volume before the upgrade: This is the volume after the upgrade: It will mount but I cannot access the share. I took the drive an plugged in into my laptop's USB Port, I am able to view the contents without issue. Is there anything I should be looking at? "New_Volume" is the name of share.
  10. I just finished upgrading from 6.11 --> 6.12.6 Everything is good with one exception. I have an unassigned device, it's a portable hard drive connected to the Server's USB Port. This is the volume before the upgrade: This is the volume after the upgrade: It will mount but I cannot access the share. I took the drive an plugged in into my laptop's USB Port, I am able to view the contents without issue. Is there anything I should be looking at? "New_Volume" is the name of share.
  11. Was using an SSD as a download drive(lots of write/read/delete cycles) a bad choice?
  12. I pulled the drive and replaced it with a spinning drive. All is well now. Interesting though that even after the drive was unmounted from UD that syslog filled up with this line(over & over) until I did a re-boot. SMARTCTL IS USING A DEPRECATED SCSI IOCTL, PLEASE CONVERT IT TO SG_IO
  13. This device(Lexar SSD), sdg, has failed 32 days after purchase. I have it installed as an unassigned device. Is there any diagnostic(chkdsk) tools to examine the drive within UnRaid? Here is an Excerpt from the System Log. When I un-mount & re-mount the drive there are no files or folders present. This drive just serves as a download location for Sonarr, then files are moved to cache and then to the array(overnight). The drive is a Lexar NQ100 SSD 1.92TB 2.5” SATA III Internal Solid State Drive, Up to 550MB/s Read (LNQ100X1920-RNNNU), did I pick the wrong SSD to serve as a scratch drive? I tried to do the "Check File System" in Unassigned Devices, but Unraid tells me that there are I/O Errors and it can't be read. 15:38:51 MediaTower kernel: I/O error, dev sdg, sector 357171856 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 Sep 6 15:38:51 MediaTower kernel: sd 5:0:0:0: [sdg] tag#7 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=DRIVER_OK cmd_age=0s Sep 6 15:38:51 MediaTower kernel: sd 5:0:0:0: [sdg] tag#7 CDB: opcode=0x2a 2a 00 38 53 c4 08 00 04 68 00 Sep 6 15:38:51 MediaTower kernel: I/O error, dev sdg, sector 945013768 op 0x1:(WRITE) flags 0x100000 phys_seg 88 prio class 0 Sep 6 15:38:51 MediaTower kernel: sd 5:0:0:0: [sdg] tag#8 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=DRIVER_OK cmd_age=0s Sep 6 15:38:51 MediaTower kernel: sd 5:0:0:0: [sdg] tag#8 CDB: opcode=0x2a 2a 00 38 53 c8 70 00 07 a8 00 Sep 6 15:38:51 MediaTower kernel: I/O error, dev sdg, sector 945014896 op 0x1:(WRITE) flags 0x104000 phys_seg 168 prio class 0 Sep 6 15:38:51 MediaTower kernel: sd 5:0:0:0: [sdg] tag#9 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=DRIVER_OK cmd_age=0s Sep 6 15:38:51 MediaTower kernel: sd 5:0:0:0: [sdg] tag#9 CDB: opcode=0x2a 2a 00 38 53 d0 18 00 04 08 00 Sep 6 15:38:51 MediaTower kernel: I/O error, dev sdg, sector 945016856 op 0x1:(WRITE) flags 0x100000 phys_seg 88 prio class 0 Sep 6 15:38:51 MediaTower kernel: sd 5:0:0:0: [sdg] tag#10 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=DRIVER_OK cmd_age=0s Sep 6 15:38:51 MediaTower kernel: sd 5:0:0:0: [sdg] tag#10 CDB: opcode=0x2a 2a 00 38 53 d4 20 00 08 18 00 Sep 6 15:38:51 MediaTower kernel: I/O error, dev sdg, sector 945017888 op 0x1:(WRITE) flags 0x104000 phys_seg 168 prio class 0 Sep 6 15:38:51 MediaTower kernel: sdg1: writeback error on inode 4609739, offset 0, sector 9922400 Sep 6 15:38:51 MediaTower kernel: XFS (sdg1): log I/O error -5 Sep 6 15:38:51 MediaTower kernel: XFS (sdg1): metadata I/O error in "xfs_buf_ioend+0x113/0x386 [xfs]" at daddr 0xa7abe630 len 32 error 5 Sep 6 15:38:51 MediaTower kernel: XFS (sdg1): Filesystem has been shut down due to log error (0x2).
  14. No I have not removed this disk. It is plugged in to one of the internal sata ports, inside the server.