• Content Count

  • Joined

  • Last visited

Community Reputation

4 Neutral

1 Follower

About emuhack

  • Rank

Recent Profile Visitors

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

  1. BOOM -- thanks for this... Works like a charm
  2. Yeah I'm going to switch to a nvme this weekend, I have a backup of my appdata folder and will restore the dockers when I install the nvme. I appreciate the help and the time spend on looking at the diags.
  3. I ran a scrub on the pool and it seems to be stable, but when I try to delete a certain folder in appdata, it freaks out and gives these error. I have ordered a 1tb NVME drive for use with my cache to get the sata ssd's out of the system, but would be interested on if i can delete the folder before i migrate to the NVME also I know disk 5 in the array is bad, waiting until the nvme is here to take out and rebuild the array as asked diags attached emu-unraid-diagnostics-20200330-2123.zip
  4. also to add [1/7] checking root items [2/7] checking extents ref mismatch on [194688524288 65536] extent item 0, found 1 data backref 194688524288 root 5 owner 11000 offset 24625152 num_refs 0 not found in extent tree incorrect local backref count on 194688524288 root 5 owner 11000 offset 24625152 found 1 wanted 0 back 0x1062f950 backpointer mismatch on [194688524288 65536] ref mismatch on [194688557056 65536] extent item 1, found 0 incorrect local backref count on 194688557056 root 5 owner 11000 offset 24625152 found 0 wanted 1 back 0x9344620 backref disk byten
  5. Slowly this has been getting worse, and it seems like I may have to scrub my cache pool. Can anybody help me with the follow errors. I can seem to do anything in relation to my dockers and they are not responding? Mar 30 14:06:53 eMu-Unraid kernel: loop: Write error at byte offset 844144640, length 4096. Mar 30 14:06:53 eMu-Unraid kernel: print_req_error: I/O error, dev loop2, sector 1648720 Mar 30 14:06:53 eMu-Unraid kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 152, rd 0, flush 0, corrupt 0, gen 0 Mar 30 14:07:21 eMu-Unraid kernel: resource sanity check: requesting
  6. I have dug up an older T5500 from my "stash" and I am building a buddy his first plex server I have a 3900x and another XEON based system and all the CPU stats have shown up. This new system though I have this issue where the cpu is Not Specified. I have the latest BIOS update for this machine. This is the System Device Page System Devices PCI Devices and IOMMU Groups IOMMU group 0: [8086:3406] 00:00.0 Host bridge: Intel Corporation 5520 I/O Hub to ESI Port (rev 22) IOMMU group 1: [8086:3408] 00:01.0 PCI bridge: Intel Corpor
  7. I have a Poweredge Blade Server and want to make it my VM and Docker Unraid Machine, currently windows server 2012 with hyper-V (my other machine is in my signature) - The machine in my signature is going to be PLEX and storage machine. I don't really need storage in the new machine. I read that a SSD array is not "recommended" or "supported" - has anybody had an experience with that or tested? I was thinking of keeping 2x of the 512gb 10k drives for data array with parity, and 2-3 SSD drives for a cache pool for VM storage and Docker Storage. I would do 4-5 SSD's if it was OK to d
  8. For what its worth I have Samsung SSD's working... No Issues
  9. Anybody help with why these temps are so wonky... 262F and why nct6797 is so different from k10temp ?
  10. Updated from 6.8.2 -- Took 3:27 to get the gui back No issues as of yet... My temp sensors are showing up now for my ryzen 3900x I updated my UD plugin before my upgrade and no issues ---------------------------- Anybody know why the temps are so different for the CPU Also if needed i can start a new thread.
  11. @limetech - any rough eta. Also waiting for 5.x kernel for amd 3000 temp monitoring
  12. I know there is a lot on this, and from what I have read this will be fixed in the next iteration of unraid, but im seeing that sensors-detect is picking up the sensors but still no temps, can someone explain why that is? Also how would i make this work? Do you want to generate /etc/sysconfig/lm_sensors? (yes/NO): yes Copy prog/init/lm_sensors.init to /etc/init.d/lm_sensors for initialization at boot time. You should now start the lm_sensors service to load the required kernel modules. root@eMu-Unraid:~# sensors-detect # sensors-detect version 3.6.0 # System: M
  13. updated 6.8.0 ----> 6.8.2 Upgrade went fine, server rebooted normally. Will check in later to see how it runs. EDIT: 30hr in no issues