• Content Count

  • Joined

  • Last visited

Everything posted by Rich

  1. Thanks for the heads up ryoko. I gave the three commands a shot and it did sort out the syslog flooding, but sadly didn't solve the single thread at 100% or allow the VM to boot, so looks like i'll be continuing with UEFI disabled for the moment.
  2. I'm seeing this as well now. With UEFI boot enabled, a VM with iGPU passthrough doesn't boot, maxes out a CPU thread and totally fills the syslog with, kernel: vfio-pci 0000:00:02.0: BAR 2: can't reserve [mem 0xc0000000-0xcfffffff 64bit pref] Disabling UEFI boot stops the problem and allows the VM and passthrough to return to working as expected. Rich
  3. Ah, thank you. Good to know. Do you know if it's normal for it to be taking this long, its been reading disk2 for nearly 12 hours now?
  4. Hi all, I'm currently seeing constant reads on disk2 of roughly 500KB/s-1.5MB/s. Having checked with the 'Open Files' plugin to see what is being read and what program is reading, i can see that random files are being read across multiple shares (some of which no plugins or dockers have access too) on the disk are they are being read by a program called 'find'. Can anyone tell me if this is a Linux / unRAID process doing something, or do i need to start shutting things down to try and pinpoint what it is? Thank you, Rich
  5. After a bit of messing about it looks like those errors may have been due to a dodgy sas cable. Thanks to those that helped.
  6. Been a little while so I'm going to try and outline this a little clearer. You only need to download one more file to make this all work using the EFI shell for steps 5-7. So I downloaded "Toolset_PercH310 to" and "" from here. For steps 1-4 you can use MegaRec on every PC I've tried it on and so I used the .bat files from the toolset to accomplish those. I also put all these files on a bootable DOS USBstick. Unzip the toolset into it's own folder and the SAS2FLASH zip into it's own folder. Copy the P5_sas2flash.efi from the P5 folder and paste it
  7. Yeah, I'll post back when its done.
  8. Yeah I have, it's unassigned and preclearing as I type. The array displays and functions just as it did before I installed the drive
  9. I had to unassign it so that preclear could see it, so although it wasn't actively part of the array yet, it seems like it provisionally was until the clear had completed. Unassignning it had no effect on the array though, so it didnt cause any issues.
  10. Downloaded the preclear plugin and have just kicked it off
  11. This is after a reboot with autostart disabled,
  12. I genuinely can't remember what happens after the clear and how the drive gets added, sorry. It's been a long time since I've added a drive and last time it required the array to be offline the entire time. The percentage counter is moving in the corner of the GUI, so it doesn't look like its stuck? Yeah all plugins are up to date. I haven't done anything with them, regarding the errors, as they are all working and i wanted to give it a bit of time for them to be updated to support the unRAID change, before considering deleting them. Sure, I'll have to search on how to do it, but i
  13. I was cycling the system to test something in the bios and on the controllers, so not unexpected (after installing the drive but pre booting into unraid). Here's the diagnostics zip.
  14. Here's a smart report for the disk. I'm afraid I'm not sure what other diagnostics there are, other than this? WDC_WD60EZRZ-00GZ5B1_WD-WX21D36PPPEF-20170207-2011.txt
  15. I would agree. The parity disks are spun down though, so clearing is obviously not affecting them. If these errors do indicate a fault with the disk, it would be a bit inconvenient if its already part of the array.
  16. Now I know the difference, thanks and sorry for my naivety. I have never precleared a drive with a script, I have always let unRaid clear it itself, even when that meant keeping the array offline for a while. Yeah I've got notifications set up to email me when errors occur, although no errors are showing on the GUI for Disk14, so no notifications. The only errors are the ones in the syslog (which are still occurring every minute and on the same block).
  17. I cant remember exactly what it said, I'm afraid and I wrote 'preclear' instinctively, not because that's what I definitely saw. Sorry if I've caused some confusion. If it helps clear it up, it says 'Clearing' at the bottom of the screen (attached).
  18. I installed the new drive, booted up, selected the new drive in the drop down for Disk 14 and started the array, agreeing that doing so would start a preclear. Thats the right way to add a drive isn't it? Or are 'preclear' and 'clear' different things? It has a little blue square next to it in the GUI for 'New Device'
  19. Thanks for the reply. Ok, i'll wait and see what the error count reads after the preclear has finished.
  20. Hi All, I've just added another drive to my Array and during the preclear i noticed the below from the syslog (this is just a section). Disk14 is the pre-clearing drive. Normally i would have just thought i received a dodgy drive and would RMA, but each error is on the same block and is a minute apart. Is it just me or is that a bit odd? I would have thought they would be at random times and on random blocks? Is this likely to mean anything, or shall i just ignore it and RMA? Thank you, Rich Feb 7 17:31:01 unRAID kernel: Buffer I/O error on dev md14, logic
  21. Hey, does anyone know of an nginx equivalent to this?
  22. Thanks for the post and your feedback Limetech, very much appreciated I have swapped the cards over already and the errors followed the card. That was an RMA'd card though which generated exactly the same errors as the card it replaced and I find it hard to believe I received two faulty controllers in a row For the moment I've disabled vt-d on the motherboard and everything appears to be running smoothly. The only thing i was concerned about was not being able to pass though my Belkin UPS to my Windows VM for auto shutdown, but the 'Network UPS Tools (NUT)' plugin has solved that
  23. Ok, I guess I'll have to admit defeat and start looking Thanks for all your help
  24. I ran lspi again after re-enabling vt-d and got the same result as my second previous lspci, 01:00.0 RAID bus controller: Marvell Technology Group Ltd. 88SE9485 SAS/SATA 6Gb/s controller (rev c3) 06:00.0 RAID bus controller: Marvell Technology Group Ltd. 88SE9485 SAS/SATA 6Gb/s controller (rev c3) So they're still identiacal. Its really weird that it changed at all, but even stranger that it changed without me makng any modification to the card (it was pre reflashing the bios). I'm not sure what else I can to do investigate? Yeah I have swapped the cards over, when the second / ne