Neldonado

Calling this closed for now, I swapped the drives around and haven't noticed anything

These diagnostics should include logs from the mover scheduled a couple hours ago. If it would help I could reboot, run the mover, and get new diagnostics? skynet-diagnostics-20230528-1945.zip

I removed the plug-in, hit the mover and still got a bunch of no space errors.

I am having trouble with files not moving from the cache drive to my TV media share. There is plenty of space on my array, so I can't figure out why it won't move. For what it's worth I am using mover tuner plugin. Here are those settings below. My Movies share gives me the same error for moving movies... no other shares have this issue with the cache drive.. here are my share settings skynet-diagnostics-20230527-1732.zip

So I rebooted, tried several cables, data and power, tried different data ports and the reallocated sector count just kept climbing, and then a udma error started popping up. I swapped this with another ssd in the machine, and it still had issues while the other ssd was fine, so I think it’s safe to assume it’s the drive failing. I pulled the drive from the pool and am running the pool with one drive. If I stop and add a new ssd (240gb vs the current 256gb) can I just start it and do a scrub?

Yeah, the reboot didn't work, now the drive won't even show up to mount.

I rebooted the server and the drive is completely missing from the gui now. How do I proceed?

I’ll check the cables but they are relatively new, I was dealing with this months ago and replaced all the cables. Could my power supply be giving up ever so slightly?

So this morning I got this error: Unraid Skynetcache disk SMART health [5] Warning [SKYNET] - reallocated sector ct is 24. Fast forward a couple hours and I get this: fstrim: /mnt/skynetcache: FITRIM ioctl failed: Input/output error. I logged in and noticed my drive dropped offline, but I can’t figure out why. I’ve uploaded my diagnostics too. it’s worth mentioning I’ve also been having intermittent issues with my /mnt/mediacache drive falling offline too. skynet-diagnostics-20230525-0813.zip

These cables are relatively new, is there any way to see if it’s just a bad disk or a power issue?

OK, it's been almost 4 days and I started getting errors again. diagnostics attached. skynet-diagnostics-20230515-0334.zip

Finished scrubbing and including diagnostics after finishing. also noticed my log is full, what should next steps be? skynet-diagnostics-20230510-1535.zip

Tons of errors being corrected… this is all good I hope? Looks like I’ve got some downtime before it’s finished.

New diagnostics skynet-diagnostics-20230508-0655.zip

So I do that and it refreshes and says aborted? UUID: xxxx Scrub started: Mon May 8 05:57:58 2023 Status: aborted Duration: 0:00:00 Total to scrub: 3.04TiB Rate: 0.00B/s Error summary: no errors found

So is this what I want to do? btrfs scrub start -B -d -r /dev/sdaa1 and btrfs scrub start -B -d -r /dev/sdx1

Are these the same errors (see picture) sdx is the other drive in this cache pool. BTFS error (device sdl: state EA): parent transid verify failed on 316334 9286912 wanted 36459 found 36425 uploading diagnostics again. Somethings weird going on, I replaced all my cables a month or two ago and I just started noticing these errors out of nowhere. skynet-diagnostics-20230508-0436.zip

looks like the drive is throwing the same errors, I imagine it'll drop offline any minute.

new diagnostics skynet-diagnostics-20230507-0831.zip

I’ve got roughly 1.2TB of data on this cache pool, would it be safe to run the mover and get the data off?

I started getting these notifications a few weeks ago, "fstrim: /mnt/mediacache: the discard operation is not supported". I went to poke around and checked my logs to find a wall of this: BTRFS error (device sdaa1): bdev /dev/sdaa1 errs: wr 106017132, rd 82906, flush 0, corrupt 0, gen 0 what causes this, and what should I do to remedy the situation? Shut down, reseat cables, start back up? I've uploaded my diagnostics skynet-diagnostics-20230506-0817.zip

Anyway to know what caused the crash? I use NFS to mount shares back and forth between this unraid server and another unraid server.

Hi all, Last night I updated a few dockers and hit "invoke mover" and went to bed. When I woke up I noticed none of my shares were present. This is what my logs show. I have attached my diagnostics as well. t1000-diagnostics-20230412-0339.zip

Hey all, I am trying to figure out how to safely increase my vdisk. I am using a 1tb m.2 drive almost entirely for this vdisk so I want to increase it from 300 to like 800 or so. Is it as easy as clicking on the 300G and changing it from there?