EArroyo

Members
  • Posts

    40
  • Joined

  • Last visited

Recent Profile Visitors

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

EArroyo's Achievements

Rookie

Rookie (2/14)

0

Reputation

  1. I think a 2FA on the Web login would be a VERY useful and wise addition to unRAID. Right now username/password is limiting me to have to connect to my VPN in order to peek at my server and see how it's doing...
  2. SUCCESS! Cloned image booted perfect, created smaller image (90% size) and no more CSUM errors on scrub after deleting file. Hopefully this helps anybody with scrub issues and VM images.
  3. Well, just an update.... This looks very promising. Downloaded AOMEI Backupper Standard (free) and it's cloning from one image to the other. Hopefully the result boots when I set it as main drive and possibly smaller in size?
  4. Well, let's say the corruption are in sections of the image file that has no "data" the VM uses. Would it be safe to do then? Is there any qcow2 utility to repair a corrupted image and not mark it unusable (if that's the case?) EDIT: I'm about to try to add a 2nd image drive to my VM and try to clone it to the new image file, maybe that will save my VM (because even though it works, I don't want to hit a wall) I'm also very disappointed that btrfs cache pool raid1 is not as safe and I feel it might just be a waste of time and money if same scenario that corrupted it will corrupt a non btrfs cache pool raid1 the same way, I may as well just spend the money and get twice as much space... 🤔
  5. No errors on parity check, only these 3 checksum errors and all 3 on both SSDs. I did have some power spikes during this stupid storm that just passed (live @ Florida) and also found out my UPS needs battery replacement (go figure, everything going to crap all at once) so I ran a drive check on Windows 10 (VM) and found no errors and VM works fine. Is there any way I can copy without getting the input/output error but not messing up image integrity so I can reformat the cache pool? As last resort, can I mount a new image on VM and clone the main drive to the new image?
  6. My questions are how? or why? I forked $130 for an extra 1TB ssd to create a cache pool (raid1) so I could have redundancy and not worry about data corruption on my cache (where I have my VM images,) but seems like I wasted my money? I never had issues with my cache drives (ssd) until I went cache pool. I checked it with scrub and I got this: Jul 10 01:13:38 MMPC1 ool www[25457]: /usr/local/emhttp/plugins/dynamix/scripts/btrfs_scrub 'start' '/mnt/cache' '' Jul 10 01:13:38 MMPC1 kernel: BTRFS info (device sdl1): scrub: started on devid 1 Jul 10 01:13:38 MMPC1 kernel: BTRFS info (device sdl1): scrub: started on devid 2 Jul 10 01:28:38 MMPC1 kernel: BTRFS warning (device sdl1): checksum error at logical 5525486284800 on dev /dev/sdm1, physical 197491273728, root 5, inode 279, offset 31180976128, length 4096, links 1 (path: custom/unraid/Windows10.img) Jul 10 01:28:38 MMPC1 kernel: BTRFS error (device sdl1): bdev /dev/sdm1 errs: wr 0, rd 0, flush 0, corrupt 22, gen 0 Jul 10 01:28:38 MMPC1 kernel: BTRFS error (device sdl1): unable to fixup (regular) error at logical 5525486284800 on dev /dev/sdm1 Jul 10 01:28:41 MMPC1 kernel: BTRFS warning (device sdl1): checksum error at logical 5523090034688 on dev /dev/sdm1, physical 198316249088, root 5, inode 279, offset 63094951936, length 4096, links 1 (path: custom/unraid/Windows10.img) Jul 10 01:28:41 MMPC1 kernel: BTRFS error (device sdl1): bdev /dev/sdm1 errs: wr 0, rd 0, flush 0, corrupt 23, gen 0 Jul 10 01:28:41 MMPC1 kernel: BTRFS error (device sdl1): unable to fixup (regular) error at logical 5523090034688 on dev /dev/sdm1 Jul 10 01:28:53 MMPC1 kernel: BTRFS warning (device sdl1): checksum error at logical 5525486284800 on dev /dev/sdl1, physical 197512245248, root 5, inode 279, offset 31180976128, length 4096, links 1 (path: custom/unraid/Windows10.img) Jul 10 01:28:53 MMPC1 kernel: BTRFS error (device sdl1): bdev /dev/sdl1 errs: wr 0, rd 0, flush 0, corrupt 32, gen 0 Jul 10 01:28:53 MMPC1 kernel: BTRFS error (device sdl1): unable to fixup (regular) error at logical 5525486284800 on dev /dev/sdl1 Jul 10 01:28:57 MMPC1 kernel: BTRFS warning (device sdl1): checksum error at logical 5523090034688 on dev /dev/sdl1, physical 198337220608, root 5, inode 279, offset 63094951936, length 4096, links 1 (path: custom/unraid/Windows10.img) Jul 10 01:28:57 MMPC1 kernel: BTRFS error (device sdl1): bdev /dev/sdl1 errs: wr 0, rd 0, flush 0, corrupt 33, gen 0 Jul 10 01:28:57 MMPC1 kernel: BTRFS error (device sdl1): unable to fixup (regular) error at logical 5523090034688 on dev /dev/sdl1 Jul 10 01:35:10 MMPC1 kernel: BTRFS warning (device sdl1): checksum error at logical 5690545643520 on dev /dev/sdm1, physical 280946253824, root 5, inode 279, offset 37611438080, length 4096, links 1 (path: custom/unraid/Windows10.img) Jul 10 01:35:10 MMPC1 kernel: BTRFS error (device sdl1): bdev /dev/sdm1 errs: wr 0, rd 0, flush 0, corrupt 24, gen 0 Jul 10 01:35:11 MMPC1 kernel: BTRFS error (device sdl1): unable to fixup (regular) error at logical 5690545643520 on dev /dev/sdm1 Jul 10 01:35:20 MMPC1 kernel: BTRFS warning (device sdl1): checksum error at logical 5690545643520 on dev /dev/sdl1, physical 280967225344, root 5, inode 279, offset 37611438080, length 4096, links 1 (path: custom/unraid/Windows10.img) Jul 10 01:35:20 MMPC1 kernel: BTRFS error (device sdl1): bdev /dev/sdl1 errs: wr 0, rd 0, flush 0, corrupt 34, gen 0 Jul 10 01:35:20 MMPC1 kernel: BTRFS error (device sdl1): unable to fixup (regular) error at logical 5690545643520 on dev /dev/sdl1 Jul 10 01:40:21 MMPC1 kernel: BTRFS info (device sdl1): scrub: finished on devid 2 with status: 0 Jul 10 01:40:32 MMPC1 kernel: BTRFS info (device sdl1): scrub: finished on devid 1 with status: 0 GRRR! This is soooo annoying!!!! Looks like errors are on BOTH drives, shows as 6 errors, but 3 on sdl1 and same 3 on sdm1. Is there ANYTHING I can do or can I run another setup that's more bullet proof???
  7. I ended up removing the docker, deleting data from cache drive and reinstalling. Solved my problem. Just odd that I had to do all of that to get it working. Had to do the same on my backup server as well because it was having issues as well. Now they seem to work fine and even faster with the new version of Syncthing.
  8. Is it just me or is everybody having issues with unRAID v6.9.2 and VM? I am running Windows 10 and Server 2019 and have been updating them to the latest versions. They have gotten slower and on my backup server sometimes they respond so slow, it's unusable. This was not happening before. Not sure if it's the new Windows versions or VM in unRAID...but I would like to know if I'm not the only one noticing this... EDIT: I am suspecting my cache drive on my backup unRAID server, even though it has no errors, I already had a drive fail and replaced it. After replacing it, it reconstructed (had it set to RAID-1) but ever since it's been slow. On my main unRAID server I moved all my data from 21 x 2TB drives ton 6 x 8TB drives, not sure if that had any impact on my cache drive or not, but I am out of ideas what to do in order to fix cache drive or unRAID data/config? Server 2019 constantly crashes on main server. About to roll back to 6.9.1 to see if it fixes this issue. EDIT2: 1. backup server crashed cache partition when restored to 6.9.1 2. it's been over a day and my VM's are rock solid on *BOTH* servers with ver. 6.9.1 EDIT3: Upgraded to 6.9.2 and it's working fine. I must have some docker memory leak.
  9. I can't create new topic on application forum. After upgrading to unRAID 6.9.0 my syncthing stopped working. I saw an upgrade to 6.9.1 a few days later and applied it, but it's still not working. Any advise?
  10. I would like to see this as well.
  11. Late for the party but.... What I wanted to do was share an "unassigned devices" share as a samba share, so I created a symbolic link and called it a day... On unRAID: ln -s /mnt/disks/500GB /mnt/user/500GB On Windows: \\Tower\500GB
  12. I've always had issues with RX460 (ended up running an old driver and now with 20H2 it's not working but I don't get black screen, I just get disabled video adapter due to problems), can you explain exactly what you did to get it working? Thanks.
  13. Is this still the correct way of doing this? I just tried to increase the size and I got an error that Docker service could not start, lost my docker image, had to delete image and setup all my dockers again.
  14. So I have 2 different routes: 1. ecloud-selfhosting https://gitlab.e.foundation/e/infra/ecloud-selfhosting 2. YunoHost https://yunohost.org/#/docker Can someone help me with this? Maybe add it on the APPS section for future users as well. Thanks!
  15. Should I be worried about a UDMA Error Count of 1? Or can I acknowledge it and continue with my life? LOL