Jump to content

fmp4m

Members
  • Content count

    175
  • Joined

  • Last visited

  • Days Won

    1

fmp4m last won the day on April 22

fmp4m had the most liked content!

Community Reputation

8 Neutral

About fmp4m

  • Rank
    Advanced Member
  • Birthday September 26

Converted

  • Gender
    Male
  • Personal Text
    unRAID: 6.5.1 Pro License | CPU: AMD Ryzen Threadripper 1950x | MB: Asus Prime X399-A | Memory: 128GB DDR4 | 48TB | 2TB Cache
    Case: Norco RPC-4116 w/ 6x 2.5" hotswap in 5.25 tray | GPU: TBD | Network: 1GbE x2 Balance-RR
    Donation: https://cash.me/$fmp4m

Recent Profile Visitors

353 profile views
  1. fmp4m

    6.6.0-rc1 Gui Boot - locked at low resolution

    I'm ok with that. I may have to keep my production. Server on 6.5 until fixed. alternatively I can allow remote connection or even overnight a card with a return label to assist. Last resort, just tell me a known 100% working and I'll buy it.
  2. fmp4m

    6.6.0-rc1 Gui Boot - locked at low resolution

    This still exists in RC4. Is there a Current List of supported GPU's? Perhaps I need to just buy another GPU. I have to have functioning and usable GUI in my environment.
  3. This still occurred for both dockers and vm when in safe mode. This has not occurred in RC4. VM - Did emulatorpin retention fix this? Docker -Seemed to Stop - Removed - Re-added and showed with pinned cpus
  4. I can not post screen shots. I use the built in gui boot. I went to: Settings -> CPU Pinning -> Had 2 VMs, Selected CPU 14,15 HT: 30, 31 for VM1 Selected CPU 12,13 HT 28, 29 for VM2 -> Clicked Apply, error populated and VM's disappeared. Took diagnostics and then rebooted. Isolated CPU 0,1 HT 16,17 Rebooted CPU Pinning Docker: Chose sets for each docker and clicked apply I lost 5 Dockers - Radarr, Sonarr, PiHole, Unifi, OpenVPN-AS Used CA - Previously installed to restore these and they now have correct pinnage.
  5. fmp4m

    6.6.0-rc1 Gui Boot - locked at low resolution

    Hello LT, I unfortunately do not have on-board graphics. It is the same on both of my pci cards. Radeon RX 560 Radeon HD 6450
  6. Execution error invalid argument: could not find capabilities for arch=x86_64 domaintype=kvm The above error was encountered immediately after clicking apply from changing pinned CPU's to previously created VMs. Before changes it showed all VMs. After applying all VMs disappeared from the VM pin list and the VM tab. nas-diagnostics-20180911-0808.zip
  7. fmp4m

    6.6.0-rc1 Gui Boot - locked at low resolution

    6.6.0-RC2 still has this issue.
  8. Changed Status to Closed
  9. Close this, I will remain on 6.5.3 where there are no issues with any of the disks or controllers. I can see you would rather belittle me than help here. By downgraded drive, I meant UNRAID 6.5.3 boot drive. 6.6.0-rc1 is the only one that has the issues and is ISOLATED to this build.
  10. TRURL: I disagree and do not like the attitude, I understand I may deserve it by being slightly vague but I also have 9,000 other things I am working with at the same time. I reported this as a bug in the PR due to it ONLY occurring on the 6.6.0-RC1. My downgraded drive has zero issues. Now I am attaching my diagnostics as I believe it is a driver that is not playing nice, as just moments ago ALL drives reported the exact same error. with over 22,000 errors on all drives and the cache pool disappearing. nas-diagnostics-20180904-2246.zip
  11. Sep 2 16:43:19 NAS kernel: mdcmd (7): import 6 sdl 64 3907018532 0 MB4000GCWDC_Z1Z963EC Sep 2 16:43:19 NAS kernel: md: import disk6: (sdl) MB4000GCWDC_Z1Z963EC size: 3907018532 Sep 2 16:43:20 NAS emhttpd: shcmd (39): /usr/local/sbin/set_ncq sdl 1 Sep 2 16:43:20 NAS root: set_ncq: setting sdl queue_depth to 1 Sep 2 16:43:20 NAS emhttpd: shcmd (40): echo 128 > /sys/block/sdl/queue/nr_requests Sep 3 16:07:58 NAS kernel: sd 15:0:6:0: [sdl] tag#2 CDB: opcode=0x85 85 06 20 00 00 00 00 00 00 00 00 00 00 40 e5 00 Sep 3 16:08:01 NAS kernel: sd 15:0:6:0: [sdl] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 Sep 3 16:08:01 NAS kernel: sd 15:0:6:0: [sdl] tag#0 Sense Key : 0x2 [current] Sep 3 16:08:01 NAS kernel: sd 15:0:6:0: [sdl] tag#0 ASC=0x4 ASCQ=0x0 Sep 3 16:08:01 NAS kernel: sd 15:0:6:0: [sdl] tag#0 CDB: opcode=0x8a 8a 00 00 00 00 00 b7 15 60 88 00 00 04 00 00 00 Sep 3 16:08:01 NAS kernel: print_req_error: I/O error, dev sdl, sector 3071631496 Sep 3 16:08:01 NAS kernel: sd 15:0:6:0: [sdl] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 Sep 3 16:08:01 NAS kernel: sd 15:0:6:0: [sdl] tag#0 Sense Key : 0x2 [current] Sep 3 16:08:01 NAS kernel: sd 15:0:6:0: [sdl] tag#0 ASC=0x4 ASCQ=0x0 Sep 3 16:08:01 NAS kernel: sd 15:0:6:0: [sdl] tag#0 CDB: opcode=0x8a 8a 00 00 00 00 00 b7 15 64 88 00 00 04 00 00 00 Sep 3 16:08:01 NAS kernel: print_req_error: I/O error, dev sdl, sector 3071632520 Sep 3 16:08:01 NAS kernel: sd 15:0:6:0: [sdl] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 Sep 3 16:08:01 NAS kernel: sd 15:0:6:0: [sdl] tag#0 Sense Key : 0x2 [current] Sep 3 16:08:01 NAS kernel: sd 15:0:6:0: [sdl] tag#0 ASC=0x4 ASCQ=0x0 Sep 3 16:08:01 NAS kernel: sd 15:0:6:0: [sdl] tag#0 CDB: opcode=0x8a 8a 00 00 00 00 00 b7 15 68 88 00 00 04 00 00 00 Sep 3 16:08:01 NAS kernel: print_req_error: I/O error, dev sdl, sector 3071633544 Sep 3 16:08:01 NAS kernel: sd 15:0:6:0: [sdl] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 Sep 3 16:08:01 NAS kernel: sd 15:0:6:0: [sdl] tag#0 Sense Key : 0x2 [current] Sep 3 16:08:01 NAS kernel: sd 15:0:6:0: [sdl] tag#0 ASC=0x4 ASCQ=0x0 Sep 3 16:08:01 NAS kernel: sd 15:0:6:0: [sdl] tag#0 CDB: opcode=0x8a 8a 00 00 00 00 00 b7 15 6c 88 00 00 04 00 00 00 Sep 3 16:08:01 NAS kernel: print_req_error: I/O error, dev sdl, sector 3071634568 Sep 3 16:08:01 NAS kernel: sd 15:0:6:0: [sdl] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 Sep 3 16:08:01 NAS kernel: sd 15:0:6:0: [sdl] tag#0 Sense Key : 0x2 [current] Sep 3 16:08:01 NAS kernel: sd 15:0:6:0: [sdl] tag#0 ASC=0x4 ASCQ=0x0 Sep 3 16:08:01 NAS kernel: sd 15:0:6:0: [sdl] tag#0 CDB: opcode=0x8a 8a 00 00 00 00 00 b7 15 70 88 00 00 04 00 00 00 Sep 3 16:08:01 NAS kernel: print_req_error: I/O error, dev sdl, sector 3071635592 Sep 3 16:08:01 NAS kernel: sd 15:0:6:0: [sdl] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 Sep 3 16:08:01 NAS kernel: sd 15:0:6:0: [sdl] tag#0 Sense Key : 0x2 [current] Sep 3 16:08:01 NAS kernel: sd 15:0:6:0: [sdl] tag#0 ASC=0x4 ASCQ=0x0 Sep 3 16:08:01 NAS kernel: sd 15:0:6:0: [sdl] tag#0 CDB: opcode=0x8a 8a 00 00 00 00 00 b7 15 74 88 00 00 04 00 00 00 Sep 3 16:08:01 NAS kernel: print_req_error: I/O error, dev sdl, sector 3071636616 Sep 3 16:08:01 NAS kernel: sd 15:0:6:0: [sdl] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 Sep 3 16:08:01 NAS kernel: sd 15:0:6:0: [sdl] tag#0 Sense Key : 0x2 [current] Sep 3 16:08:01 NAS kernel: sd 15:0:6:0: [sdl] tag#0 ASC=0x4 ASCQ=0x0 Sep 3 16:08:01 NAS kernel: sd 15:0:6:0: [sdl] tag#0 CDB: opcode=0x8a 8a 00 00 00 00 00 b7 15 78 88 00 00 04 00 00 00 Sep 3 16:08:01 NAS kernel: print_req_error: I/O error, dev sdl, sector 3071637640 Sep 3 16:08:01 NAS kernel: sd 15:0:6:0: [sdl] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 Sep 3 16:08:01 NAS kernel: sd 15:0:6:0: [sdl] tag#0 Sense Key : 0x2 [current] Sep 3 16:08:01 NAS kernel: sd 15:0:6:0: [sdl] tag#0 ASC=0x4 ASCQ=0x0 Sep 3 16:08:01 NAS kernel: sd 15:0:6:0: [sdl] tag#0 CDB: opcode=0x8a 8a 00 00 00 00 00 b7 15 7c 88 00 00 04 00 00 00 Sep 3 16:08:01 NAS kernel: print_req_error: I/O error, dev sdl, sector 3071638664 Sep 3 16:08:01 NAS kernel: sd 15:0:6:0: [sdl] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 Sep 3 16:08:01 NAS kernel: sd 15:0:6:0: [sdl] tag#0 Sense Key : 0x2 [current] Sep 3 16:08:01 NAS kernel: sd 15:0:6:0: [sdl] tag#0 ASC=0x4 ASCQ=0x0 Sep 3 16:08:01 NAS kernel: sd 15:0:6:0: [sdl] tag#0 CDB: opcode=0x8a 8a 00 00 00 00 00 b7 15 80 88 00 00 04 00 00 00 Sep 3 16:08:01 NAS kernel: print_req_error: I/O error, dev sdl, sector 3071639688 Sep 3 16:08:01 NAS kernel: sd 15:0:6:0: [sdl] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 Sep 3 16:08:01 NAS kernel: sd 15:0:6:0: [sdl] tag#0 Sense Key : 0x2 [current] Sep 3 16:08:01 NAS kernel: sd 15:0:6:0: [sdl] tag#0 ASC=0x4 ASCQ=0x0 Sep 3 16:08:01 NAS kernel: sd 15:0:6:0: [sdl] tag#0 CDB: opcode=0x8a 8a 00 00 00 00 00 b7 15 84 88 00 00 04 00 00 00 Sep 3 16:08:01 NAS kernel: print_req_error: I/O error, dev sdl, sector 3071640712 Sep 3 22:50:04 NAS emhttpd: shcmd (360): /usr/local/sbin/set_ncq sdl 1 Sep 3 22:50:04 NAS emhttpd: shcmd (361): echo 128 > /sys/block/sdl/queue/nr_requests Sep 3 22:52:02 NAS emhttpd: shcmd (388): /usr/local/sbin/set_ncq sdl 1 Sep 3 22:52:02 NAS emhttpd: shcmd (389): echo 128 > /sys/block/sdl/queue/nr_requests Sep 3 22:52:44 NAS emhttpd: shcmd (416): /usr/local/sbin/set_ncq sdl 1 Sep 3 22:52:44 NAS emhttpd: shcmd (417): echo 128 > /sys/block/sdl/queue/nr_requests
  12. disk6 (MB4000GCWDC_Z1Z963EC) is disabled disk6 (MB4000GCWDC_Z1Z963EC) has read errors The problem is, smart short and smart extended shows no errors. This drive also has less than 30 days power-on. 1 Raw read error rate 0x000f 074 063 044 Pre-fail Always Never 27582192 3 Spin up time 0x0003 092 092 070 Pre-fail Always Never 0 5 Reallocated sector count 0x0033 100 100 010 Pre-fail Always Never 0 7 Seek error rate 0x000f 076 060 030 Pre-fail Always Never 4340119908 9 Power on hours 0x0032 100 100 000 Old age Always Never 659 (27d, 11h) 10 Spin retry count 0x0013 100 100 097 Pre-fail Always Never 0 180 Unknown HDD attribute 0x003b 100 100 030 Pre-fail Always Never 1559174187 194 Temperature celsius 0x0022 042 049 000 Old age Always Never 42 (0 24 0 0 0) 196 Reallocated event count 0x0033 100 100 010 Pre-fail Always Never 0
  13. fmp4m

    6.6.0-rc1 Gui Boot - locked at low resolution

    I am saying I want to use the 1920x1080 but 1024x768 would work if thats all that is possible. With the new RC it is limited to a maximum of 800x600 which is less than usable.
  14. Throughout all of the releases, I have grown used to the low 1024x768 limit of gui, and not the desired 1920x1080. However this new release has gone back in time to 800x600 and I can't use it at all. Through previous troubleshooting I have 1920x1080 dummy plugs in all ports not in use. This is limited to this release and no others so far have limited to less than 1024x768. Can this be corrected easily/rapidly? I would love to test the new RC but can't without gui boot. nas-diagnostics-20180902-1650.zip
  15. fmp4m

    X399 motherboard it87 driver for temps

    This needs to be implemented for us TR users :)