Jump to content

GameKing505

Members
  • Content Count

    17
  • Joined

  • Last visited

Community Reputation

2 Neutral

About GameKing505

  • Rank
    Member

Recent Profile Visitors

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

  1. The best feature is definitely the amazing unraid community. As far as feature requests, I’d love VM snapshots, and also some way to edit VM hardware and resources without destroying any custom xml that may have been added.
  2. Ideally I'd like to be able to modify for example, how many cores I've assigned to my OSX Virtual Machine, without needing to re-add in all of the custom XML that is needed to make the osx VM run. If I make these changes with the unraid UI, then my understanding is that custom XML would be overwritten. I was hoping that using virt-manager would let me make those edits while preserving the custom XML, but it appears you can't assign individual logical cores to a VM using the virt-manager docker?
  3. So there's no way to achieve CPU pinning using the virt-manager docker? That's disappointing... I thought the whole idea was that you got /more/ control than the default unraid GUI for VMs.
  4. In Virt-Manager I don't see a way to modify which logical cores are assigned to a VM (like in the native unraid UI). I see a way to assign a "current allocation" and "maximum allocation" of logical cores, as well as manually setting CPU topology, but nowhere do I see where to actually just set which logical cores are assigned to the VM. Am I missing something? I've seen screenshots of virt-manager that include this functionality. What I see in the docker: What I've seen of Virt-Manager elsewhere:
  5. I managed to get it all working with a passed through GTX 1080 on High Sierra but then mistakenly allowed the Mac App Store to make updates (not a full OS update but some sort of security patch). Now my display is messed up again at boot, even though the correct Nvidia web drivers are installed. OSX VMs seem like a PITA... Thoughts on how to fix it?
  6. Thanks SpaceInvader! I started over, followed those^ instructions, and got a working 2-core VM with passthrough. The key issue was just installing the nvidia drivers remotely when the screen was garbled. THEN I went and tried to change the # of cores in the VM (and made all the right edits to the XML again) and somehow this resulted in the VM not outputting to the display. It boots with a black monitor at 1280x1024 resolution. I can Splashtop in and use the VM no problem, but it won't even show me the full 2560x1440 resolution option in osx preferences. Any thoughts? Here is what I see in display preferences:
  7. Unfortunately I have tried that and it hasn’t worked. The only difference is that my paths are for the High Sierra OVMF flies and not the Catalina ones- but I assume that is as it should be. I’m still getting the graphical glitches...
  8. Thanks for the help! I am new to OSX VMs, clover, etc. so some of what you suggested may have gone over my head (my apologies). What I did - I mashed escape upon booting the VM to get to the VM BIOS. Then I poked around looking for resolution settings and found this screen: It seems the "preferred resolution at next boot" is 1080p and I seemingly can't change that option in the bios, but the "change preferred resolution for next boot" is set to the correct 1440p resolution. Is this right? Next I booted the VM and installed Clover Configurator (which I found via googling). Then I mounted the EFI partition and opened up the config.plist file (is that right?) on there within clover configurator. Then I changed the screen resolution setting to 2560x1440, like so: After making these changes, I attempted to pass through the GPU but I got the same graphical error I described earlier. I can technically use the mouse and keyboard etc, but it's impossible to see what I'm doing, and the image is repeated 3x: Any other thoughts?
  9. I created a High Sierra VM and I am able to edit the # of cores in the VM Manager UI and then re-add all the changes to the XML, and the VM performs just fine (via VNC). However as soon as I add my GTX 1080 GPU for pass-through, I get a bizarre repeated and compressed image on the monitor. It's like the screen height is shrunk by 3x, and then the image repeats 3 times from left to right. Any thoughts on why this would be? I've seen others in this thread complain about the same issue, which they claimed was solved by adding the "<os>" section of the XML back in. I've done this but nothing has helped. Open to thoughts. ALSO: is there any way to modify the boot order in the clover boot menu? It seems to default to the installation rather than booting the actual already-installed OSX. Kind of annoying - I'm sure it's an easy fix but I can't for the life of me find it in the options.
  10. There's no sensitive or critical data on the disk, just some media I could reacquire if needed. I will try the preclear method and see if it works.
  11. Great thank you. So the course of actions I plan to take is: Add new disk to the array Copy all the data from the questionable disk onto the new one Remove the questionable disk from the array, run preclear 3 times If the reallocated sector count does not increase... add the disk back into the array?? If the count does increase... just trash the disk? Does that sound right?
  12. Diagnostics file attached. Let me know what you recommend; I'm frankly still a bit confused by what the SMART attributes all mean, and at what point you absolutely have to replace a disk. You are correct the disk is not new. I had used it in a windows build prior to unRAID for a number of years. Diagnostics.zip
  13. I only just installed unRAID recently, and now it's reporting that one of my 4TB array disks has a "current pending sector" value of 2. I can run the SMART short self test with no errors, but when I run the extended test it gives back "Errors occurred - check your SMART report" Unfortunately I hadn't yet set up my parity drive. I have the 8TB drive sitting on my desk but I didn't bother to install it yet. Didn't think I'd get a failure so soon after setting up unRAID... It seems I can still read data from the array, as far as I can tell. What is my best course of action? Is it too late to set up the parity drive? Should I just copy over data from the drive with the error onto the 8TB and then get a new drive as parity? Any help would be appreciated. Thanks! SMART report below: === START OF INFORMATION SECTION === Model Family: Western Digital Red Device Model: WDC WD40EFRX-68WT0N0 Serial Number: WD-WCC4EFUL6CVL LU WWN Device Id: 5 0014ee 26015376b Firmware Version: 82.00A82 User Capacity: 4,000,787,030,016 bytes [4.00 TB] Sector Sizes: 512 bytes logical, 4096 bytes physical Rotation Rate: 5400 rpm Device is: In smartctl database [for details use: -P show] ATA Version is: ACS-2 (minor revision not indicated) SATA Version is: SATA 3.0, 6.0 Gb/s (current: 6.0 Gb/s) Local Time is: Mon Oct 21 17:02:23 2019 EDT SMART support is: Available - device has SMART capability. SMART support is: Enabled AAM feature is: Unavailable APM feature is: Unavailable Rd look-ahead is: Enabled Write cache is: Enabled DSN feature is: Unavailable ATA Security is: Disabled, frozen [SEC2] Wt Cache Reorder: Enabled === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED General SMART Values: Offline data collection status: (0x00) Offline data collection activity was never started. Auto Offline Data Collection: Disabled. Self-test execution status: ( 121) The previous self-test completed having the read element of the test failed. Total time to complete Offline data collection: (54000) seconds. Offline data collection capabilities: (0x7b) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. Offline surface scan supported. Self-test supported. Conveyance Self-test supported. Selective Self-test supported. SMART capabilities: (0x0003) Saves SMART data before entering power-saving mode. Supports SMART auto save timer. Error logging capability: (0x01) Error logging supported. General Purpose Logging supported. Short self-test routine recommended polling time: ( 2) minutes. Extended self-test routine recommended polling time: ( 540) minutes. Conveyance self-test routine recommended polling time: ( 5) minutes. SCT capabilities: (0x703d) SCT Status supported. SCT Error Recovery Control supported. SCT Feature Control supported. SCT Data Table supported. SMART Attributes Data Structure revision number: 16 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTENAME FLAGS VALUE WORST THRESH FAIL RAW_VALUE 1 Raw_Read_Error_Rate POSR-K 200 200 051 - 6 3 Spin_Up_Time POS--K 241 178 021 - 4925 4 Start_Stop_Count -O--CK 073 073 000 - 27039 5 Reallocated_Sector_Ct PO--CK 200 200 140 - 0 7 Seek_Error_Rate -OSR-K 200 200 000 - 0 9 Power_On_Hours -O--CK 056 056 000 - 32704 10 Spin_Retry_Count -O--CK 100 100 000 - 0 11 Calibration_Retry_Count -O--CK 100 100 000 - 0 12 Power_Cycle_Count -O--CK 100 100 000 - 609 192 Power-Off_Retract_Count -O--CK 200 200 000 - 489 193 Load_Cycle_Count -O--CK 173 173 000 - 82313 194 Temperature_Celsius -O---K 115 100 000 - 37 196 Reallocated_Event_Count -O--CK 200 200 000 - 0 197 Current_Pending_Sector -O--CK 200 200 000 - 2 198 Offline_Uncorrectable ----CK 100 253 000 - 0 199 UDMA_CRC_Error_Count -O--CK 200 200 000 - 0 200 Multi_Zone_Error_Rate ---R-- 200 200 000 - 5 |||||| K auto-keep |||||__ C event count ||||___ R error rate |||____ S speed/performance ||_____ O updated online |______ P prefailure warning General Purpose Log Directory Version 1 SMART Log Directory Version 1 [multi-sector log support] Address Access R/W Size Description 0x00 GPL,SL R/O 1 Log Directory 0x01 SL R/O 1 Summary SMART error log 0x02 SL R/O 5 Comprehensive SMART error log 0x03 GPL R/O 6 Ext. Comprehensive SMART error log 0x06 SL R/O 1 SMART self-test log 0x07 GPL R/O 1 Extended self-test log 0x09 SL R/W 1 Selective self-test log 0x10 GPL R/O 1 NCQ Command Error log 0x11 GPL R/O 1 SATA Phy Event Counters log 0x21 GPL R/O 1 Write stream error log 0x22 GPL R/O 1 Read stream error log 0x80-0x9f GPL,SL R/W 16 Host vendor specific log 0xa0-0xa7 GPL,SL VS 16 Device vendor specific log 0xa8-0xb7 GPL,SL VS 1 Device vendor specific log 0xbd GPL,SL VS 1 Device vendor specific log 0xc0 GPL,SL VS 1 Device vendor specific log 0xc1 GPL VS 93 Device vendor specific log 0xe0 GPL,SL R/W 1 SCT Command/Status 0xe1 GPL,SL R/W 1 SCT Data Transfer SMART Extended Comprehensive Error Log Version: 1 (6 sectors) Device Error Count: 2 CR = Command Register FEATR = Features Register COUNT = Count (was: Sector Count) Register LBA_48 = Upper bytes of LBA High/Mid/Low Registers ] ATA-8 LH = LBA High (was: Cylinder High) Register ] LBA LM = LBA Mid (was: Cylinder Low) Register ] Register LL = LBA Low (was: Sector Number) Register ] DV = Device (was: Device/Head) Register DC = Device Control Register ER = Error register ST = Status register Powered_Up_Time is measured from power on, and printed as DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes, SS=sec, and sss=millisec. It "wraps" after 49.710 days. Error 2 [1] occurred at disk power-on lifetime: 32594 hours (1358 days + 2 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER -- ST COUNT LBA_48 LH LM LL DV DC -- -- -- == -- == == == -- -- -- -- -- 40 -- 51 00 40 00 00 07 f7 37 70 e7 00 Error: UNC 64 sectors at LBA = 0x07f73770 = 133642096 Commands leading to the command that caused the error were: CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name -- == -- == -- == == == -- -- -- -- -- --------------- -------------------- c8 00 00 00 40 00 00 07 f7 37 50 e7 08 2d+07:46:04.173 READ DMA c8 00 00 00 40 00 00 07 f7 37 90 e7 08 2d+07:46:04.161 READ DMA c8 00 00 00 80 00 00 07 f7 36 d0 e7 08 2d+07:46:04.161 READ DMA c8 00 00 00 80 00 00 07 f7 36 50 e7 08 2d+07:46:04.161 READ DMA c8 00 00 00 40 00 00 07 f7 36 10 e7 08 2d+07:46:04.161 READ DMA Error 1 [0] occurred at disk power-on lifetime: 32594 hours (1358 days + 2 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER -- ST COUNT LBA_48 LH LM LL DV DC -- -- -- == -- == == == -- -- -- -- -- 40 -- 51 00 00 00 00 07 f7 2a f0 e7 00 Error: UNC at LBA = 0x07f72af0 = 133638896 Commands leading to the command that caused the error were: CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name -- == -- == -- == == == -- -- -- -- -- --------------- -------------------- c8 00 00 00 00 00 00 07 f7 2a 10 e7 08 2d+07:46:00.287 READ DMA c8 00 00 00 00 00 00 07 f7 29 10 e7 08 2d+07:46:00.286 READ DMA c8 00 00 00 00 00 00 07 f7 28 10 e7 08 2d+07:46:00.285 READ DMA c8 00 00 00 00 00 00 07 f7 27 10 e7 08 2d+07:46:00.284 READ DMA c8 00 00 00 00 00 00 07 f7 26 10 e7 08 2d+07:46:00.284 READ DMA SMART Extended Self-test Log Version: 1 (1 sectors) Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error 1 Extended offline Completed: read failure 90% 32700 133638896 2 Short offline Completed without error 00% 32698 - 3 Extended offline Completed: read failure 90% 32697 133638896 4 Extended offline Completed: read failure 90% 32697 133638896 5 Extended offline Completed: read failure 10% 32636 133638896 6 Short offline Completed without error 00% 32629 - SMART Selective self-test log data structure revision number 1 SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS 1 0 0 Not_testing 2 0 0 Not_testing 3 0 0 Not_testing 4 0 0 Not_testing 5 0 0 Not_testing Selective self-test flags (0x0): After scanning selected spans, do NOT read-scan remainder of disk. If Selective self-test is pending on power-up, resume after 0 minute delay. SCT Status Version: 3 SCT Version (vendor specific): 258 (0x0102) Device State: Active (0) Current Temperature: 37 Celsius Power Cycle Min/Max Temperature: 31/41 Celsius Lifetime Min/Max Temperature: 12/52 Celsius Under/Over Temperature Limit Count: 0/0 Vendor specific: 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 SCT Temperature History Version: 2 Temperature Sampling Period: 1 minute Temperature Logging Interval: 1 minute Min/Max recommended Temperature: 0/60 Celsius Min/Max Temperature Limit: -41/85 Celsius Temperature History Size (Index): 478 (431) Index Estimated Time Temperature Celsius 432 2019-10-21 09:05 37 ****************** ... ..( 64 skipped). .. ****************** 19 2019-10-21 10:10 37 ****************** 20 2019-10-21 10:11 35 **************** 21 2019-10-21 10:12 36 ***************** ... ..( 2 skipped). .. ***************** 24 2019-10-21 10:15 36 ***************** 25 2019-10-21 10:16 37 ****************** ... ..( 69 skipped). .. ****************** 95 2019-10-21 11:26 37 ****************** 96 2019-10-21 11:27 38 ******************* ... ..( 15 skipped). .. ******************* 112 2019-10-21 11:43 38 ******************* 113 2019-10-21 11:44 37 ****************** ... ..( 14 skipped). .. ****************** 128 2019-10-21 11:59 37 ****************** 129 2019-10-21 12:00 36 ***************** ... ..( 38 skipped). .. ***************** 168 2019-10-21 12:39 36 ***************** 169 2019-10-21 12:40 37 ****************** ... ..( 17 skipped). .. ****************** 187 2019-10-21 12:58 37 ****************** 188 2019-10-21 12:59 38 ******************* ... ..( 43 skipped). .. ******************* 232 2019-10-21 13:43 38 ******************* 233 2019-10-21 13:44 37 ****************** ... ..(197 skipped). .. ****************** 431 2019-10-21 17:02 37 ****************** SCT Error Recovery Control: Read: 70 (7.0 seconds) Write: 70 (7.0 seconds) Device Statistics (GP/SMART Log 0x04) not supported Pending Defects log (GP Log 0x0c) not supported SATA Phy Event Counters (GP Log 0x11) ID Size Value Description 0x0001 2 0 Command failed due to ICRC error 0x0002 2 0 R_ERR response for data FIS 0x0003 2 0 R_ERR response for device-to-host data FIS 0x0004 2 0 R_ERR response for host-to-device data FIS 0x0005 2 0 R_ERR response for non-data FIS 0x0006 2 0 R_ERR response for device-to-host non-data FIS 0x0007 2 0 R_ERR response for host-to-device non-data FIS 0x0008 2 0 Device-to-host non-data FIS retries 0x0009 2 4 Transition from drive PhyRdy to drive PhyNRdy 0x000a 2 4 Device-to-host register FISes sent due to a COMRESET 0x000b 2 0 CRC errors within host-to-device FIS 0x000f 2 0 R_ERR response for host-to-device data FIS, CRC 0x0012 2 0 R_ERR response for host-to-device non-data FIS, CRC 0x8000 4 598776 Vendor specific
  14. That's a great point. I'm sure support /will/ come, if a little late. FYI- I ended up ordering the Asus X570 TUF Gaming plus and 32GB of G.SKILL Trident Z Neo, just based off the QVL list for the board. I'm hugely excited for the new build, as my last CPU was an i5 4670k. It served me well but this new beast is 4x the compute. Can't wait to get to my build and dive into the world of unRAID.
  15. Thanks for the reply! I think I'm pretty set on the 3900x. If this whole experiment doesn't work then I'll just rock windows and their semi-shitty implementation of Raid, with plex and all the relevant dockers, etc. I don't want to do that but it's a decent fallback if I surrender. I'm a decent tinkerer, and do derive some joy out of it, so I think I'm OK to run with trickier hardware. Any reason you went with x470 instead of x570? I hadn't considered that as an option but I do like the idea of a motherboard without a fan, which all the x570 boards seem to have. Not sure if PCIe4 is really worth it either.