Jump to content

Rich

Members
  • Content Count

    246
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Rich

  • Rank
    Advanced Member
  • Birthday May 7

Converted

  • Gender
    Male
  • Location
    UK
  • Personal Text
    --

Recent Profile Visitors

530 profile views
  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 diagnostics-20180624-1740.zip
  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 LSI9211_P19.zip" and "EFI_Installer_P5.zip" 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 into the folder: \Toolset_PercH310 to LSI9211_P19\H310_to_LSI\5_LSI_P7 And copy the P16_sas2flash.efi to folders: \Toolset_PercH310 to LSI9211_P19\H310_to_LSI\5_DELL_IT \Toolset_PercH310 to LSI9211_P19\H310_to_LSI\5_LSI_P16 Reboot into dos that is on your USB stick. Navigate to \Toolset_PercH310 to LSI9211_P19\H310_to_LSI using "cd" command. Also to view contents you can use "dir /w" to see what you need to type. 1. Run 1.bat 2. Run 2.bat 3. Run 3.bat 4. Reboot 5. Boot into EFI shell. type "FSx" [enter] x= the drive letter of your USB drive. For me it was FS0. Now you can use "ls" to list the contents of your usb stick and "cd" to change directory. Also once you type about 3 characters you can auto fill with [Tab] which makes things like navigating long directory names easier. Go to the \Toolset_PercH310 to LSI9211_P19\H310_to_LSI\5_DELL_IT folder. Now run the following command: P16_sas2flash -o -f 6gbpsas.fw "I used a X10SLL which has the EFI shell in the BIOS image. If you don't you should be able to use EFI shell v1. I've added them to the zip I'm uploaded just in case. You have to use google on how to use EFI shell on a puter that requires the EFI files to be on the root of the drive." 6. reboot back into EFI shell and go to the folder \Toolset_PercH310 to LSI9211_P19\H310_to_LSI\5_LSI_P7 and run the following command: P5_sas2flash -o -f 2118it.bin You will be asked to confirm the flash and just choose Yes and it will flash from the dell IR FW to the LSI IT FW. 7. Now reboot again into EFI shell and go to \Toolset_PercH310 to LSI9211_P19\H310_to_LSI\5_LSI_P16 and run the following command: P16_sas2flash -o -f 2118it.bin -b mptsas2.rom (you can omit the "-b mptsas2.rom" if you don't want the boot BIOS. I recommend you install the BIOS as you can see your drives at boot to ensure your card is working properly) 8. Now enter: P16_sas2flsh -o -sasadd 500605bxxxxxxxxx where "500605bxxxxxxxxx" is the SAS address that you got in step 1. 9. Enjoy your new flashed LSI 2008 card. I've done this exact process on 3 different cards now. Even the M1015 just without installing the 6gbpsas.fw first. I'm not using UnRaid as I like FreeNAS and it is currently on P16 firmware so that is why I stopped there. If you want to install P19 then go to the LSI site that I linked above and download the Installer_P19_for_UEFI and use that sas2flash.efi file to flash the P19 FW. You don't want to use the wrong installer for your FW as it can do some strange things. I only used the P5 installer to be able to accept the cross flashing of IT FW over IR firmware. I uploaded to my dropbox. I just want to say a MASSIVE thank you to Fireball3 and Maglin for both of their walkthroughs Fireball3's got me to step 3, then i experienced the "failed to initialize PAL" error and Maglin got me through the rest. Thank you both very much If i may enter a little addition for other noobies like myslef, Maglin's step 5 says Which, for me wasn't quite that straight forward. First i had to run 'map' so i could see my USB stick and which 'fs' value it had (6), then i had to run 'map fs6', then 'fs6:' Now the USB stick was mounted and i could proceed. Thank you again, Rich
  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'm happy to stop it and preclear instead. is it ok to use this plugin? https://raw.githubusercontent.com/gfjardim/unRAID-plugins/master/plugins/preclear.disk.plg
  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. unraid-diagnostics-20170207-2037.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