Jump to content

gnollo

Members
  • Posts

    687
  • Joined

  • Last visited

Posts posted by gnollo

  1. It's the Norco SS-500 hard drive cage...https://www.newegg.com/norco-ss-500-hot-swap-rack-module/p/N82E16816133030
     
    **Mind you, I would never buy anything from Norco. Their customer service has gone from awful to non-existent. If you have issues with these, good luck ever getting in contact with them (they don't have an answering machine setup, they don't answer the phone, and they don't respond to emails). I ordered a part from their online store and they never delivered the item that was said to be in-stock. PayPal reimbursed me because they couldn't even get in contact with Norco. I'm about 98% sure they've actually gone out of business.
     
    ****If you want decent hard drive cages, go with Supermicro CSE-M35T-1B's. If those are too expensive get either the iStarUSA BPU-350SATA (BPU-350HD) or BPN-DE350SS (BPN-DE350HD). The iStarUSA cages are a little less solid than the Supermicro ones but they seem to have an active customer service and they come in trayless varieties.
    I am not happy with the temps in my Norco ss-500, really considering selling the four of them and buying these instead

    Current temps during heavy usage almost reach 50 and its winter over here...

    Sent from my SM-A520F using Tapatalk

  2. I'm running a single docker, Emby. As previously running 6.6.6 for a long time.

    Have also upgraded the Emby docker, so I was looking at reverting to 6.6.6 first to see if it makes any difference in terms of playback performance.

    Just copy the old .bz files over I guess?

    Will it affect the Emby docker?

    One thing I noticed is much higher cpu usage at idle. Even with the Emby docker stopped, there would be one CPU at 100% all the time, and some usage on the other three, for a 30/40% aggregated average. On 6.6.6 it was under 10% I think.

     

    Sent from my SM-A520F using Tapatalk

     

     

  3. Rufus worked for one of the flash drives I have been working on.

     

    I created a syslinux 6.03 bootable flash with it, making sure I ticked compatibility with old motherboards.

    Then I copied all the unraid files off the old flash, and we have liftoff.

     

    Very kindly limetech support is helping me out with another key.

     

    Let's hope 4GB will last me as long as the old flash did!

     

    /saga over

     

    Sent from my SM-A520F using Tapatalk

     

     

     

     

  4. On 12/16/2019 at 9:58 AM, gnollo said:

    More testing tonight, including uninstalling antivirus, a bigger Cruzer, using Rufus to prepare the flash drive and using a cdrom bootloader

    Sent from my SM-A520F using Tapatalk
     

    Rebuild the second flash key with antivirus off, UEFI Boot mode NO, no change. Also tried the same with a new Sandisk Cruzer FIT 16 GB USB 2.0 Flash drive. Same difference. It is seen in the bootup but not available in the bios as hard disk.

    When I reboot the machine, before it scans to list the disks available, this message appears

    ** This version supports only Hard Disk and CDROM drives **

    I am stumped. I will try next to setup the key to look like a CD ROM, using a cdrom bootloader

  5. It might be worth changing the label on the 'old' key to be something other than 'UNRAID' and checking that the 'new' one is labelled as 'UNRAID' and see if the system then still boots OK.  If it does then that would confirm that the problem must lie with how the 'new' one is being made bootable as it would confirm that the initial stage of the boot ran from the 'old' key ant the later stages from the 'new' one.  
     
    There have been reports of security software silently interfering with attempts to modify the MBR on a flash drive to make it bootable so I am wondering if there is a possibility of that being your problem.
    More testing tonight, including uninstalling antivirus, a bigger Cruzer, using Rufus to prepare the flash drive and using a cdrom bootloader

    Sent from my SM-A520F using Tapatalk

  6. I restored the backup of the old key to the new key. Cleared the /previous folder on the old key.

    Copied the bz* files across to both keys.

    Rebooted the server. Now I am running 6.8. 

    Both keys are in synch but the one recognised as the boot device is the one that is not booting on its own.
    Not ideal, and I wonder what will happen once the other key blacklisting comes into effect.

  7. followed the instruction below. 

    Run the CMD app as admin, and then

     

    J:\>make_bootable.bat
    Make Bootable v1.5
     Volume in drive J is UNRAID
     Volume Serial Number is AECA-3701

    Permit UEFI boot mode [Y/N]: y
    Ready to make disk bootable!
    Press any key to continue . . .
    J:\syslinux\syslinux.exe -maf J:
    Completed

    Press any key to continue . . .

    J:\>

     

    No difference

  8. 1 minute ago, limetech said:

    We cannot unblacklist keys.

    😱 What do you suggest I do next?

    Can you recommend any USB key that I can use with this motherboard?

    I will test that it can boot on its own this time, before I try to switch the permissioning.
    I could also try to update the OS on both keys, and see if they boot in unison, like they are doing on 6.6.6

×
×
  • Create New...