Optiplex AIO 9020



  • I ordered about 40 of the optiplex 9010’s but dell notified me that they were discontinuing that model
    "The 9010 AIO is EOL…… please take a look at the 3011 AIO and the 9020 AIO" model so i choose the 9020 thinking it wouldn’t be to far off in the specs. The 9010’s took my image fine but the 9020’s give me a error upon registration “Hard Disk not found”

    Anyone have any ideas?


  • Banned

    This post is deleted!


  • Unlike above, I have two hard drives installed with the Intel Raid Controller Raid 1. Once I upgraded the server to 1.20 from .32 I was able to capture the image of the machiens. Problem now is I have an image on Disk 0 and Disk1 is OEM image, I have to break the raid in the OS and rebuild it to disk 1. Any ideas? It worked in .32 on the Dell Opti 9010’s setup with Raid 1.

    EDIT
    Forgot my image settings.
    Windows 7
    type: Multiple Partition Image - Single Disk (not resizable).



  • I’ve got some OptiPlex 9020 SFF desktop/towers here and they come shipped from Dell with the RAID controller enabled. This is kind of silly since there’s only room for one HDD in the box…

    Change it from RAID to AHCI in the BIOS and see if it works. That’s what it took to get mine to image.



  • I tested your kernel since i had to go back into the lab, your kernel does work also on the 9020AIO.



  • I downloaded your kernel and i was about to upload it to my fogserver & i noticed that i had a kernel in my directory that was about 12mb. I remembered that i downloaded that a few months back but never tried it, i tried that kernel and it worked. I think that zip file must have gotten corrupt at some point, i placed the kernel388core and my default bzImage file on the following location https://skydrive.live.com/?cid=7C7B033E0442FC0E&id=7C7B033E0442FC0E!110


  • Senior Developer

    It’d be better if I have the config file you’ve used for this kernel. It appears that the system can’t recognize the drive as it’s being listed in the inventory as SCSI, does your kernel have SCSI drivers built in?

    Have you tried my kernel already? Mine actually does have SCSI built in. It’s slightly larger than your’s appears to be, but it’s because it s built on core, but has none of the VGA requirements. It also has all possible network drivers built in.

    I can’t seem to open your bzImage file as it says that it’s an invalid zip file. Unless it’s just a zip for skydrive’s sake and all I’m supposed to do is rename it as bzImage.

    In the above case, I’d still need the config file you used.

    Please give mine a try. My config file is already posted at:

    https://mastacontrola.com/fogboot/kernel/TomElliott.config



  • https://skydrive.live.com/?cid=7C7B033E0442FC0E&id=7C7B033E0442FC0E!110 click on the bzImage zip to download. If you are able to create a kernel for this model would it be possible to merge your findings with the kernel i have?



  • This post is deleted!


  • https://mastacontrola.com/fogboot/kernel/bzImage is the one I’ve already built. If you get me the info I’ll build and give you the alternate link.9020AIO.zip



  • https://mastacontrola.com/fogboot/kernel/bzImage is the one I’ve already built. If you get me the info I’ll build and give you the alternate link.[/quote]

    I will gather that info tomorrow and post the results


  • Senior Developer

    My guess is it’s the drivers for the Hard-drive within the kernel. Do you know what kind of Hard drive (and/or) controller the device has?

    Have you tried other kernels?

    I have one, but it’s based on core which is more or less what the default kernel is built off to my knowledge.

    You can try mine, but I don’t think it will work. If you can give me the type of drive and controller for the drive I can try to build a kernel for you.

    https://mastacontrola.com/fogboot/kernel/bzImage is the one I’ve already built. If you get me the info I’ll build and give you the alternate link.


Log in to reply
 

449
Online

38716
Users

10544
Topics

99831
Posts

Looks like your connection to FOG Project was lost, please wait while we try to reconnect.