Jump to content

ipreferpie

Members
  • Content Count

    46
  • Joined

  • Last visited

Community Reputation

0 Neutral

About ipreferpie

  • Rank
    Advanced Member

Recent Profile Visitors

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

  1. thanks for the heads up. And after the extended SMART, it does confirm my fear. That's unfortunate since I bought it in new condition from STH forums but it lacked warranty. Trying to work out something with the seller
  2. Hi there, I recently bought an OEM Seagate EXOS 14 a month ago and got the following errors: Reallocated sector count 1848 Reported uncorrect 493 Current pending sector 1840 Offline uncorrectable 1840 These were all highlighted in yellow and unRAID took this disk offline to be emulated in parity. I ran a SMART self test which completed w/o errors. Is it likely a disk problem or an issue w/ my SATA cables? Just want to see how I should proceed to be safe. Many thanks! edit: after conducting an extended test, it did come out with errors. I've attached the file for reference. hk-homelab-smart-20200701-1913.zip
  3. Yeah, it really started after upgrading to 6.8.0. The thing is that I rebuilt docker.img multiple times to no avail. I think it's too late to roll back to 6.7.x no that I upgraded twice. The likelihood and immediacy of unRAID hanging is dependent on which docker containers I'm running, I feel. Not proven yet, but I have to turn on one container at a time to run for 2-4 days to ensure it's really working and then add another one. I'm starting to do that now, but it's slow going and not really targetted. I hope someone here w/ more experience can look into the diagnostics and see what's happening.
  4. I've been using unRaid since 6.1 with no many issues and am running 6.8.1 now. But for the last 6 weeks, I've been encountering constant hanging. I noticed that this happens only when Docker is enabled. Without it enabled, there's no problem, but after having Docker running and some containers running (i.e. sabNZBD, Plex, Sonarr, influx, etc.) the system would start having a super high CPU utilization and then would start hanging. This usually takes anywhere from 2-36 hours of running the Docker containers. I would then try to stop processes that are on docker using "kill -9". After that, I'd try to "umount -l /mnt/cache" which would cause the shell to hang. If I skip these steps and try "poweroff" or "powerdown" the script would run, but get stuck at "Forcing shutdown..." after waiting 90 sec for the graceful shutdown option. I have to physically power off and start again. I run a parity check which usually shows 0 errors. But after startup up some containers, the problems persist. I tried checking the files on my /mnt/cache and try moving or syncing files on Krusader. It shows me a small number of /appdata files are corrupt (influx/wal etc which I wasn't even running). So I copied those that could be read and reformatted the cache drives and moved the files back and also deleting/rebuilding docker.img. But the problem still persists. I'm really frustrated at the problem and can't come close to any solution. I think likely it's something happening in the docker containers but don't know what. Can anyone help me on this please? I've attached my diagnostics FYI. Many thanks. hk-homelab-diagnostics-20200125-2100.zip
  5. Hi, I've been using unRAID stably for 5+ years and I've been encountering constant daily hangs over the past week. I can't tell if it's because I upgraded to 6.8 or something else. I was running a parity check overnight and in the morning, the web UI and all the docker containers would be unresponsive. I'm running it on ESXi, so I'd check to console to run "poweroff" to safely shutdown. It'd always get stuck so I would have to force the VM to shutdown. After booting up, I'd run a parity check to see if things are ok and the hanging cycle starts again. I can't tell what's causing this. I've attached the diagnostics. Many thanks in advance! hk-homelab-diagnostics-20200102-1418.zip
  6. got it, thanks! reformatted and all looks good again after a scrub
  7. so I gave it a try, but I got: BLKDISCARD ioctl failed: Remote I/O error should I take it offline and run BLKDISCARD again?
  8. thanks! so basically, can I 1) move my files on to the array, 2) take the pair of cache drives offline, 3) format, 4) then reintroduce it back as new cache drives, 5) move the data back from array to cache?
  9. Hi, after a kernel panic and a hard reset, I conducted a BTRFS scrub on my RAID1 cache pool. What I got were 4 uncorrectable errors. I deleted the docker.img and conducted SMART tests on both SSDs without issue. But upon running the scrub again, I still get the same 4 errors. I'm not sure if it's a hardware problem and how I should proceed to fix this. Below are the logs and attached is the diagnostics. Many thanks. Cache 1: Nov 10 16:13:09 HK-HomeLab kernel: BTRFS warning (device dm-10): checksum error at logical 530594066432 on dev /dev/mapper/sdn1, physical 458653364224, root 5, inode 118530799, offset 28672, length 4096, links 1 (path: appdata/binhex-plexpass/Plex Media Server/Metadata/TV Shows/2/902b34d01d1d00699de74ef41aa4a378087be30.bundle/Contents/com.plexapp.agents.thetvdb/seasons/5/episodes/13/thumbs/66948d605b6a303889512aaaad8668cb4b5d7106) Nov 10 16:13:09 HK-HomeLab kernel: BTRFS error (device dm-10): bdev /dev/mapper/sdn1 errs: wr 0, rd 0, flush 0, corrupt 3, gen 0 Nov 10 16:13:09 HK-HomeLab kernel: BTRFS error (device dm-10): unable to fixup (regular) error at logical 530594066432 on dev /dev/mapper/sdn1 Nov 10 16:13:09 HK-HomeLab kernel: BTRFS warning (device dm-10): checksum error at logical 530594070528 on dev /dev/mapper/sdn1, physical 458653368320, root 5, inode 118530799, offset 32768, length 4096, links 1 (path: appdata/binhex-plexpass/Plex Media Server/Metadata/TV Shows/2/902b34d01d1d00699de74ef41aa4a378087be30.bundle/Contents/com.plexapp.agents.thetvdb/seasons/5/episodes/13/thumbs/66948d605b6a303889512aaaad8668cb4b5d7106) Nov 10 16:13:09 HK-HomeLab kernel: BTRFS error (device dm-10): bdev /dev/mapper/sdn1 errs: wr 0, rd 0, flush 0, corrupt 4, gen 0 Nov 10 16:13:09 HK-HomeLab kernel: BTRFS error (device dm-10): unable to fixup (regular) error at logical 530594070528 on dev /dev/mapper/sdn1 Cache 2: Nov 10 15:59:58 HK-HomeLab kernel: BTRFS warning (device dm-10): checksum error at logical 530594066432 on dev /dev/mapper/sdd1, physical 36651855872, root 5, inode 118530799, offset 28672, length 4096, links 1 (path: appdata/binhex-plexpass/Plex Media Server/Metadata/TV Shows/2/902b34d01d1d00699de74ef41aa4a378087be30.bundle/Contents/com.plexapp.agents.thetvdb/seasons/5/episodes/13/thumbs/66948d605b6a303889512aaaad8668cb4b5d7106) Nov 10 15:59:58 HK-HomeLab kernel: BTRFS error (device dm-10): bdev /dev/mapper/sdd1 errs: wr 0, rd 0, flush 0, corrupt 7, gen 0 Nov 10 15:59:58 HK-HomeLab kernel: BTRFS error (device dm-10): unable to fixup (regular) error at logical 530594066432 on dev /dev/mapper/sdd1 Nov 10 15:59:58 HK-HomeLab kernel: BTRFS warning (device dm-10): checksum error at logical 530594070528 on dev /dev/mapper/sdd1, physical 36651859968, root 5, inode 118530799, offset 32768, length 4096, links 1 (path: appdata/binhex-plexpass/Plex Media Server/Metadata/TV Shows/2/902b34d01d1d00699de74ef41aa4a378087be30.bundle/Contents/com.plexapp.agents.thetvdb/seasons/5/episodes/13/thumbs/66948d605b6a303889512aaaad8668cb4b5d7106) Nov 10 15:59:58 HK-HomeLab kernel: BTRFS error (device dm-10): bdev /dev/mapper/sdd1 errs: wr 0, rd 0, flush 0, corrupt 8, gen 0 Nov 10 15:59:58 HK-HomeLab kernel: BTRFS error (device dm-10): unable to fixup (regular) error at logical 530594070528 on dev /dev/mapper/sdd1 hk-homelab-diagnostics-20191110-0837.zip
  10. Much appreciated on the advice. I'll go ahead and do this last bit and see if anything works, but am mentally prepared for a full loss. And to be doubly sure (which is a stupid question) -- there's no way to roll back the changes in parity after it was reflected in the format followed by an immediate shutdown, right? I haven't turned on my array yet since I'm scared of further changes in parity. But if I can't explore this option, I might as well just turn it on and see what important data I truly lost. Not knowing what is really killing me.
  11. Thanks everyone for the help so far. So the worst case scenario is real in that the format was reflected in parity. I guess there's absolutely no way to roll back the parity changes despite my taking it offline after the format. I've downloaded UFS Explorer Pro and did a lost file scan, but it all came back as wrong files (ZIPs, RARs, Apple icons) while they mostly should've been photo and video files. Is there something wrong that I'm not inputting correctly (LUKs decrypt or file name type) since this was a BTRFS encrypted format that was reformatted to BTRFS encrypted again. Many thanks -- I just trying to figure out options carefully before I do anything else. Decryption and scan elements were aes256-xts-plain64 and UTF-8 Unicode
  12. Thanks for all the responses so far. I was really wishing that I can find a solution to rebuild from parity, but it really looks like that as soon as I formatted while the array was online, it wiped the data off parity simultaneously. I've downloaded UFS Pro and it'll take 38hrs to scan of lost files. I really hope that I can manage to find all the ones I lost -- EUR600 is a lot, but for family photos, I'll have to bite the bullet and consider it as a very expensive lesson.
  13. Hi there, I did something really stupid. My unRAID system froze so I rebooted it. Upon restarting the array, I saw that on one of my 14TB disks, it showed unreadable file system and contents were emulated. Because I just flew back from a work trip and severely jetlagged, I did a cursory lookup of how to fix it but didn't follow instructions properly. Basically, I thought I was going to format the disk and unRAID will automatically rebuild it (instead of first taking the disk off the array first). Groggily, I checked the "reformat disk" option while unRAID was conducting a parity check after the reboot. After a minute, I felt something wasn't right. I went to take a look and it, and it showed that the 14TB drive now is all free space. unRAID total disk utilization went from 83% full to 69% full in my array, meaning I lost data. As well, that disk after formatting read it's 99% free space. When it was emulated before formatting, it read 3% free space. I panicked, stopped the parity check and immediately took the array offline. Is there anything I can do now to recover the 14TB I stupidly formatted? Any help would be great. Or is there anything I can do to rebuild from parity? I'd try that, but it it looks like somehow the format also wrote into parity. I've attached diagnostics just in case. My earlier thinking was that since the array was running, if I clicked format, it wouldn't have wiped 14TB from my array, but instead kept the contents emulated while formatting the unreadable drive. Would unRAID let me wipe 14TB of existing data while the array is running? I'm afraid to restart the array since I might overwrite even more data now. This is really disheartening and a lesson learned. There's around 10yrs plus of family photos that I might have lost in my stupidity. edit: forgot the mention that the formatted drive was an encrypted BTRFS format. I have the passkey, but not to sure how to recover the files if it comes to that. hk-homelab-diagnostics-20191103-0409.zip
  14. thanks! will do. Running preclear again now