Jump to content
XPEnology Community

syno406

Member
  • Posts

    108
  • Joined

  • Last visited

  • Days Won

    1

Posts posted by syno406

  1. @IG-88 do you see any way this will work with my hardware? Big shoutout to@gadreel for trying to assist but unfortunately when he spins it up in Virtualbox his isnt getting an ip either. 

     

    The two cards i have are:

    intel I219LM

    realtek 8110 and realtek 8168

     

    I have tried 3615,3617 and 918 with and without the lzma files. 

     

    Is the answer here to just purchase a different NIC?

  2. 9 minutes ago, gadreel said:

     

    I do not want to get too technical all I can say that the Happy Hacking Screen will display even if you have an issue even if you do not. It's a common message... If you want to see what actually is going behind the scenes you need a serial cable. I do not know how this is done virtually...

     

    So, NAT and Bridge mode did not work with the Intel 1000MT correct? Why you do not try also the 918+ loader (1.04b)?

     

    That is my next step.

     

    The reason i wanted 3615 is because i already have a barebone xpenolgy that is working fine on 3615. I wanted to take those drives over to my new machine and use RAW DISK in oracle to point to those drives. I dont know if that will work with 918 but regardless i have backups. So for right now im trying to just get it to boot (with a new blank RAW disk). Once i see that its stable, plan is to move the drives over to the new machine. 

     

    This issue has to be my NIC or Processor. I ran some test on a XPS13 laptop i5 with virtual box and i was able to get only 3617 to load up properly.

  3.  
    Again, not an expert. I am using Unraid as my hypervisor. When you select your Virtual Network you can select the model type. Sorry for the below XML, there is a GUI version but e1000 is not an option all you have to do is just write model type='e1000' you cannot do something similar with VirtualBox?
     type='bridge'>      address='52:54:00:47:15:dd'/>      bridge='br0'/>      type='e1000'/>      type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/>   

     


    Not that I know or know how
  4. To be honest neither do I. If you search the forum I believe you will find a guide how to do it. I am sure IG-88 or somebody else has a guide about it.
    I have a 4 X Intel I350-T4 chip. Never had a problem with it but my XPEnology is installed on a VM not Baremetal as yours.

    I’m trying to do a vm also. In Virtualbox
  5. The I219-LM is a fairly "new" chipset that other people had issues with it (even my self). On the other hand you said you also have a secondary NIC with Realtek's RTL8111G chipset. Look at this post it might help you out
     

    Thanks. We’re you referring me to try 1.03 and a 3617 box or the extra.lmza?
  6. Im running Virtualbox on a Dell Precision 5820 with a Intel W-2235 Xeon Processor. Using 1.03b loader to install on a 3615xs box. I get to the happy hacking screen but Synology Assistant cant find it. The built in nic is an Intel I219-LM.

     

    I also have a secondary NIC card also.

     

    How can i get the box to be visible?

     

    image.thumb.png.25d40b4663ec4a9389fbfb5f7fb20586.png

     

     

  7. after figuring out what i did wrong i cleared all partitions on the drive and reinstalled dsm. in storage manager i get an errror
    i also noticed in disk management that after dsm gets installed its creating 2 partitions. 2.38 and 2gb the rest of 9.86 is unallocated space. How do i resolve the dsm errors?

     

    2021-06-27_12-52-05.thumb.png.ffcf3451809eca42a47df6745b8068d3.png

  8.  

    3 hours ago, IG-88 said:

     

    just in case you wonder why no one answers, what you are doing here is called thread hijacking and you are stuffing any random/unrelated problem you have too

     

    Thank you and im Sorry. That was in no way my intention. I simply posted here bec it was a similar situation just on a VM level. As for me posting, ok yes maybe i over posted but it was done bec in the event someone else down the line has the same situation theyll be able to follow along with some of the errors ive seen along my journey.

     

    Did not mean to offend or hijack anything here. 

  9. I am getting this error. The drive is a 16gb flashdrive. 

     

    The I/O cache encountered an error while updating data in medium "ahci-0-1" (rc=VERR_ACCESS_DENIED). Make sure there is enough free space on the disk and that the disk is working properly. Operation can be resumed afterwards.

     

     

×
×
  • Create New...