daan_SVK

Members
  • Posts

    141
  • Joined

  • Last visited

Everything posted by daan_SVK

  1. thanks for the reply, I have updated the config file as you suggested, then I just get: VFS: Cannot open root device "sda" or unknown-block (0,0): error -6 Please append a correct "root=" boot option: here are the available aprtitions: 0800 3052392 sda driver: sd 0801 30523375 sda1 c307e18-01 memtest ran twice without reporting an error. It fails on the same spot when booting so I'm really not suspecting the RAM to be the culprit here. thanks again for any feedback
  2. hey there, I was hoping to get some direction on what to try next. My server won't boot after I gracefully powered it down last night. This is the error: Kernel Panic - not syncing: VFS: Unable to mount root fs on unknown -block (0,0) what I tried after reading some of the other threads: - chkdsk on the flash drive - comes out clean - re-formated and re-initiated the USB stick with backed up config folder - still crashes with the same error I'm currently running Memtest and will leave it on overnight, but I somehow don't think a bad memory will be the culprit here. Is there anything else I can try? What are my options after the Memtest comes out clean? thanks in advance
  3. thanks again for your input. It appears I got shipped a 4TB instead of 3TB and my parity drive is 3TB only. any idea if this is still valid? https://lime-technology.com/wiki/The_parity_swap_procedure that would allow me to upgrade to a new parity drive and use the old one to replace my failing data drive.
  4. sorry for the misunderstanding and thanks for taking the time to review the logs, I really appreciate it. my daily health checks are failing due to what's happening with this disc. Should I be just ignoring the error?
  5. I didn't put in anything yet. I have a new RED in the mail that will be replacing the flagged GREEN. Based on the previous comment I was considering preclearing the GREEN once the array has been rebuild successfully with the new RED. My understanding after reading the comments was that since the SMART report was clean, the GREEN might be reused if preclear comes back as successful. Please correct me if I'm under wrong assumptions here Sent from my ONEPLUS A3000 using Tapatalk
  6. Ok, thanks. I think I'll replace the flagged WD Green with the RED I ordered. Once rebuild, I'll preclear the Green and if successful and SMRT comes back clean, I'll pop it back into the array. Sent from my ONEPLUS A3000 using Tapatalk
  7. ok, thanks. I have already ordered a new WD RED to replace the old Green. what do you mean by giving it a second chance, you mean to put it back into the array after successfull pre-clearing? when it comes to replacing the failing drive, do i need to pre-clear the new disc? thanks again for your feedback
  8. hi there, Fix Common Issues is telling me my Disk1 has read errors, I ran the extended SMART diagnostics and it came back clear, however the disk does show 200 relocated sectors. Server diagnostics is attached, how bad is it? I have already ordered a replacement drive, just want to make sure the other drives are not having issues and I can rebuild from parity. thanks a lot tower-diagnostics-20180504-1302.zip
  9. Hmm, anyone? Do the SSD speeds look reasonable atleast? Iam really not sure where to start troubleshooting this. Sent from my ONEPLUS A3000 using Tapatalk
  10. hi there, just struggling here with a very poor VM performance. I have an older i7 with 4 cores and 8GB of RAM dedicated to a VM running on a dedicated unnasigned SSD. The issue is the performance of the VM is totally underwhelming. I was hoping to casually stream games to my Nvidia Shield over the LAN but even with the GPU passed through, which it appears it is successfully doing, I can't even get lag free windows performance over RDP. the most obvious thing i noticed is the high utilization of the SSD. Also, the SSD shows as QEMU, so I wonder whether there is still something being emulated as since the whole SSD has been passed through I was expecting to see it reported as a physical drive, but that might be just due to my ignorance. is there something obviously wrong with my setup? thanks VM.xml
  11. thanks Johnie, is there an easy way to find out what it is that's mapped to that IRQ? what about the rest of the errors, are they all related to the IRQ16 one or are they standalone and to be dealt with separately? thanks again
  12. hey there, after moving to the latest stable I'm getting a whole bunch of these: Jun 27 09:35:45 Tower kernel: irq 16: nobody cared (try booting with the "irqpoll" option) Jun 27 09:35:45 Tower kernel: CPU: 4 PID: 0 Comm: swapper/4 Not tainted 4.9.30-unRAID #1 Jun 27 09:35:45 Tower kernel: Call Trace: Jun 27 12:50:59 Tower root: Fix Common Problems: Error: Call Traces found on your server Jun 27 12:51:00 Tower root: Fix Common Problems: Warning: irq 16: nobody cared found on your server My first guess would be they'd be VM related since that's what I've been trying to get working since the update but I'm not sure. Would someone be able to provide some insight into the nature and severity of these errors? thanks in advance. tower-syslog-20170629-1328.zip
  13. I have upgraded the VM to Win10 and RDP is now working. This is a good enough of a solution, I suppose I'll stick with win10.
  14. thanks for the tip, but this is not the case.
  15. it's one of the things i want to try as well as using HP RGS and upgrading the VM to win10 but so far I'm puzzled, never had this issue before
  16. thanks for the tip, I have the same problem after disabling the firewall on the host.
  17. thanks for the tip but this is a fresh win7 image, none of these should need to be modified for a default install. I double checked and all of the settings are in place including local policies.
  18. it's a Win7 Pro, not activated... not sure if that makes a difference
  19. the VM is on 192.168.1.20 Unraid is on 192.168.1.24 I'm using the VM's IP for RDP. Host name or IP, it behaves the same.
  20. hi there, I'm unable to RDP into my VM. I have RDP enabled on the VM and local admin account password protected. I'm using br0, I can ping it, I can access it by the built-in VNC viewer. however, after the RDP client authenticates me, it just flashes "initiating RDP session" and disappears. No errors. I have tried two different clients and both behave the same way. thanks
  21. sweet thanks... kinda makes sense i guess but I wouldn't have found it without your help
  22. does the trim plug in needs to be configured in any way or executed manually?
  23. hello there, I'm sure this is just a dumb question, but I can't seem to be able to figure it out. I have a precleared ssd that I want to use to hold my VM or two but I can't seem to format it. What is it that I'm missing. thanks in advance