jonp

Administrators
  • Content count

    5481
  • Joined

  • Last visited

  • Days Won

    2

jonp last won the day on February 23

jonp had the most liked content!

Community Reputation

74 Good

About jonp

  • Rank
    Advanced Member

Converted

  • Gender
    Male
  • URL
    http://lime-technology.com
  • Location
    Chicago, IL
  1. I'll have an update in the next 48 hours. IPS is actively looking into it.
  2. Hey Chris, I can appreciate your frustration. Getting the hardware right is challenging. Will look into this further for you... I promise.
  3. We are honestly not sure. Efi booting is a new feature in 6.4 and figuring out a way to support that method with GPU pass through just isn't a priority right now. Too many other bigger fish to fry. Other than this issue with GPU pass through, I am not aware of any other problems specific to EFI booting. Sent from my SM-G930P using Tapatalk
  4. Share Configuration Issue

    Thank you for confirming!! Sent from my SM-G930P using Tapatalk
  5. Thanks Mark!!! Sent from my SM-G930P using Tapatalk
  6. Share Configuration Issue

    So I tested this on a rc9g release. Here was my experience: I created a new share and set it to Secure via SMB. I gave read/write user access to a user I created called "test" I opened a connection to the server via Windows File Explorer I saw the share I created and double-clicked it. Once in the share, I tried to create a file and Windows just straight up denied me access (like it should). I was NOT prompted to authenticate to the server. I then went back to browsing the shares in File explorer and right-clicked on the share I created and selected Map Network Drive. When given the option, I opted to provide alternate login credentials for connecting to the share. I entered the username / password for the user I created in unRAID. I completed the mapping. I then had file explorer open to my new Z:\ drive which was mapped to my secure share. I was able to create new files / folders and write files. I then renavigated my file explorer to the server address (to browse all the shares again OUTSIDE of the mapped network drive). I opened my secure share and created new files without issue. I then when back to my other file explorer window and disconnected the mapped network drive. I was still able to create new files in the secure share after doing this (figuring that Windows still has the credentials cached on the machine from the mapped network drive).
  7. Possibly. Tom and I had a long conversation about proper trim support at one point. The real trick is when you have an SSD assigned to the array. Depending on the method of discard/trim that the SSD supports, it could potentially violate the integrity of parity (changing values on the device without updating the corresponding blocks on the parity disk). I realize the context of this thread is with relation to the cache, but if we are implementing proper support for trim, we will want to address this at the same time. Sent from my SM-G930P using Tapatalk
  8. Just had to chime in and thank @johnnie.black for all his work on this topic. I am marking this thread for future review so we can see if there are further ways using the knowledge in here to make things better for everyone.
  9. Ubuntu VM unbootable .img after reboot

    Answers to my other questions?
  10. Ubuntu VM unbootable .img after reboot

    Another issue I see in the logs is a call trace relating to IRQs: Sep 27 10:49:36 tower kernel: Call Trace: Sep 27 10:49:36 tower kernel: <IRQ> Sep 27 10:49:36 tower kernel: [<ffffffff813a4a1b>] dump_stack+0x61/0x7e Sep 27 10:49:36 tower kernel: [<ffffffff810864d1>] __report_bad_irq+0x2b/0xb4 Sep 27 10:49:36 tower kernel: [<ffffffff8108679a>] note_interrupt+0x1a0/0x22e Sep 27 10:49:36 tower kernel: [<ffffffff81084384>] handle_irq_event_percpu+0x3d/0x46 Sep 27 10:49:36 tower kernel: [<ffffffff810843c3>] handle_irq_event+0x36/0x54 Sep 27 10:49:36 tower kernel: [<ffffffff810872e6>] handle_fasteoi_irq+0x90/0xf8 Sep 27 10:49:36 tower kernel: [<ffffffff81020585>] handle_irq+0x17/0x1b Sep 27 10:49:36 tower kernel: [<ffffffff8101ffda>] do_IRQ+0x46/0xc2 Sep 27 10:49:36 tower kernel: [<ffffffff8167fec2>] common_interrupt+0x82/0x82 Sep 27 10:49:36 tower kernel: <EOI> Sep 27 10:49:36 tower kernel: handlers: Sep 27 10:49:36 tower kernel: [<ffffffff814fa942>] usb_hcd_irq Seems like you might have some bad hardware on your hands or something else. What's not ringing any bells for me is the fact that you state nothing really changed before the VM stopped booting. Also, did originally set this system up with or without a cache pool? Did you add a cache pool later? Anything at all you can think of that was changed close to the time the VM stopped working? All the best, Jon
  11. Ubuntu VM unbootable .img after reboot

    Did you make any custom edits to the XML for your VM? From your logs, I did see one particular line that stuck out: 2017-09-27 17:22:22.112+0000: 3531: error : virDomainDiskDefCheckDuplicateInfo:25575 : XML error: target 'hdc' duplicated for disk sources '/mnt/user/domains/Ubuntu/vdisk1.img' and '<null>' I'm curious why you're using IDE as the bus type for the virtual storage on this VM as well (instead of VirtIO).
  12. Ubuntu VM unbootable .img after reboot

    Without more information, we won't be able to help. First we need your system diagnostics which can be obtained from the Tools > Diagnostics page. Second, please take and post a screenshot of the exact error message(s) you are receiving. All the best, Jon
  13. Also, can you confirm this issue doesn't appear on 6.3.5?
  14. Why are you enabling Hyper-V inside Windows 10? Are trying to utilize nested virtualization?
  15. Question regarding the bolded statement. Are you stating that in the VM configuration (XML) that if you enable Hyper-V, this causes boot looping, or are you talking about enabling something from within the Windows 10 VM itself? I have not been able to recreate this issue on our own test systems.
Copyright © 2005-2017 Lime Technology, Inc. unRAIDĀ® is a registered trademark of Lime Technology, Inc.