daan_SVK
-
Posts
141 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by daan_SVK
-
-
1 hour ago, Frank1940 said:
No, do not ignore the disk. Replace that disk with the new one, allowing it to rebuilt, should fix the problem.
Once you do that unRAID will 'forget' the problems that has had with that disk. But run the preclear checks on it. (I, personally, would run three full preclear cycles but then I am risk adverse and would rather be safe than sorry.)
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.
-
12 minutes ago, Frank1940 said:
We seem to have a problem in communication. My comment about the Green Drive was not to say not to use it. That is your choice. Putting the new Red Drive into the array and that should restore the array to normal operation. You can then preclear the Green drive and if you find that there are no errors in the preclear and the SMART report, you can, at that point, decide if you want to continue to use it.
The point I was trying to make was that you should not simply remove a working drive from the array to simply replace it with that Green Drive. Wait until you have another issue. If you decide to add another disk to the array, you are free to use that Green Drive. NEVER do a disk rebuilt unless you have a valid reason for doing it. When I read this comment:
I assumed that you were going to immediately (and with any thought or reason) use it to replace one of the other current drives in the array.
PS-- I downloaded your diagnostics file and looked at disk1. (I found it hard to believe that @johnnie.black would say that a disk with 200 reallocated sectors "looks fine".) The SMART report on that disk look clean to my eyes. You do not have Reallocated_Sectors_Ct of 200. You have zero! (You should be looking at the RAW_VALUE for the attributes (5, 187, 188, 197, 198, and 199) that most folks check when evaluating disk health.) From the attributes table, you have an absolutely good disk.
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?
-
I didn't put in anything yet. I have a new RED in the mail that will be replacing the flagged GREEN.
I hope you are not proposing to swap out that 'Red' that you just put in. If you need more space now, I could see adding it as a 'new' data disk. Otherwise, keep it around as a spare until you have reason to replace another disk. (Rebuilding a disk always has a potential for something going wrong. The best advice has always been-- don't screw with a working system just because you can.)
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
-
Ok, thanks.Don't need to but it's good to test the new disk before using it, with preclear or any other disk test util.
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
-
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
-
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
-
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 -
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
-
13 hours ago, johnnie.black said:
IRQ 16 is being disabled, look for a bios update or try v6.4, kernel change may also get rid of the issue, but if everything is working normally you can ignore it.
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
-
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.
-
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 hours ago, GHunter said:
In your Windows 7 VM, check your network type and make sure you're not on a public network. Should be home or private network. RDP won't work over a public network.
Gary
thanks for the tip, but this is not the case.
-
3 hours ago, jonathanm said:
It's got to be a windows issue, have you looked in the system log after making the connection attempt to see if there is something listed there?
no, which log would that be?
-
1 minute ago, jonathanm said:
Just for giggles, try installing a VNC server in the VM and see if you can connect to that.
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
-
3 hours ago, SFyffe said:
May want to check inbound firewall rules as well.
thanks for the tip, I have the same problem after disabling the firewall on the host.
-
3 hours ago, SFyffe said:
You may want to look at the Local Security Policy of the machine.
Start >>RUN>>Local Security Policy
Expand Local Policies and then User Rights Assignments. Something could be missing in the "Allow log on through Remote Desktop Services."
There is also a "Deny log on through Remote Desktop Services" that can lead to problems as well.
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.
-
1 minute ago, jonathanm said:
Pro or better?
it's a Win7 Pro, not activated... not sure if that makes a difference
-
3 minutes ago, jonathanm said:
What IP is your VM assigned?
What IP is your unraid machine?
Which IP are you RDP'ing to?
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.
-
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
-
15 hours ago, aptalca said:
Unraid gui under settings / scheduler
I couldn't find it either and someone told me
sweet thanks... kinda makes sense i guess but I wouldn't have found it without your help
-
does the trim plug in needs to be configured in any way or executed manually?
-
thank you, that was exactly it.
-
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
-
not sure what to say, I'd swear the format button wasn't there first time I started the array, I was specifically looking for it. I just managed to format it and operates properly now, thanks again...
[SOLVED] won't boot after graceful power down
in General Support
Posted · Edited by daan_SVK
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