IceBoosteR

Members
  • Content Count

    29
  • Joined

  • Last visited

Community Reputation

1 Neutral

About IceBoosteR

  • Rank
    Junior Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. IceBoosteR

    DSM 6.2 Loader

    Do you have a link for me if it is well documented? Thanks
  2. IceBoosteR

    DSM 6.2 Loader

    It would be great if someone could share how to enable the log while booting @jun loader. Therefor we would be able to see if a kernel panic occurs, or if a network driver is missing.
  3. IceBoosteR

    DSM 6.2 Loader

    Interesting. My Xeon X3430 is running fine with 1.02b for the 3617xs According to the matrix wha is supported, this should be working for 1.03b and the 3617xs version for DSM 6.2 too ... But it isn't. Because I want to test it before I install DSM 6.2 on my other machine.
  4. IceBoosteR

    DSM 6.2 Loader

    Hi everyone, stupid question but I have not found an answer to the problem I currently have. I have only seen a few other people who have the same experience, but no solution. So I have tried Jun's loader V1.03b for the 3617xs and I have tried V1.04b for the 918+ on my ESXi host. But unfortunately no network connection shows up. I have used the "ESXi" option, tried the e1000 and e1000e but no success. I have changed the serial and matched the MAC with the one on the host with no luck. I guess the loader does no support that network card? How can I figure that out? Can I activate the dmesg log when the loader starts? If yes, how can I do that? I am running ESXi 6.5u2 on two Xeons L5630 on my test-host. Thanks in advance.
  5. Würde ich auch sagen. Eigentlich kann er für das Interface auch keine APIPA-Adresse erhalten, weil der Treiber ja nicht geladen wurde - dementsprechend wäre es ein ungelades device für den Kernel. Da es aber viele im Forum gibt, die ein Problem mit der 6.2er Version und dem Netzwerk haben (ich ebenso) würde ich dennoch auf das Treiber-Problem verweisen.
  6. Wanted to write the same, as it was running in IDE mode first. Thanks for sharing the information, I guess that will help some of use.
  7. Hi, I have the same issue. I am unable to get an IP for the following configuration, which is the same as yours: V1.03b ds3615 and ds3617 (Not Obtaining IP Address) V1.04b ds918 (Not Obtaining IP Address) I have other versions running fine. I do also not know if it is needed to generate a serial number fpr the ds918+ model, as there is no serial generator available. So I do not understand how you get this to work?
  8. Oh man. I like these machines. But there are far away from poweroff. I spend 1800€ for a 12 Bay model and I will get an Atmom processor. An ATOM with 4x1,4Ghz. My NUC, working as a docker host, has 4x1,5Ghz which can burst up to 2,8Ghz (Pentium® Silver J5005). I would hope they are looking at Ryzen options, like QNAP does, but put ECC inside. Still, I can understand that they want to avoid any damage to their brand. Nevertheless the market is really hard and has changed over the last years, so hopefully they make it avaialble to just "buy the software"
  9. Hi, this topic can be closed. A little bit of searching and trying I get it to work
  10. Hello hello, I am so happy with DSM for my backup, that I want to use some software on my FreeNAS host. I would like to add a VM and install DSM inside the VM But like using it with ESXi (which is also working great) I am a little bit out of ideas how to start/make it work. Just adding the .ISO doesn't really work and I guess I miss something. Can someone please advice what I miss. For interest, FreeNAS and FreeBSD is using BHYVE for virtualisation, but I think this does not matter, as the problem is somewhere else Cheers.
  11. Hi, try to use SSH and look what kind of hardware you can see inside DSM/Linux. With some linux/debian secific commands you can find out if your OS can see the HDDs, and DSM is not - or if even the OS cannot see the disks, and you need to dig somewhere else. I wondered a little bit about the fact, that 2 of thr 4 disks even show up - as it is supposed to have only SATA/SAS disks inside a normal DS.
  12. Hello IG-88, it worked!!! I have added the drives you have provided to /lib/firmware/bnx2 (/lib/modules/firmware/bnx2 did not exist) and changed the drivers to "755", rebooted and BOOM - it worked. Well I am so happy right now, you can't imagine how much. How could I thank you? Just a little last question: Do I have to load the drivers everytime I upgrade the DSM version? And I have to do this step also when a new loader is released, I am sure. Best regards IceBoosteR
  13. Hi IG-88, thanks a lot for your help here! I will try to load the firmware drivers first - if that would not work i'll use your extra.lzma. I'll come back to the post when I got a result. If you could add all the fw to your lzma that would be awesome. I think that would solve some peoples problems before they occur Have a nice day IceBoosteR
  14. Hi IG-88, I am an idiot and did not post the error messages, which you can find below: [ 28.772288] bnx2: Can't load firmware file "bnx2/bnx2-mips-09-6.2.1b.fw" [ 28.781604] bnx2: Can't load firmware file "bnx2/bnx2-mips-09-6.2.1b.fw" [ 28.790401] init: dhcp-client (eth1) pre-start process (7252) terminated with status 255 [ 28.803529] bnx2: Can't load firmware file "bnx2/bnx2-mips-09-6.2.1b.fw" [ 28.813547] bnx2: Can't load firmware file "bnx2/bnx2-mips-09-6.2.1b.fw" I think this hits the missing driver issue. No I did not use your extra.lzma becasue Polanski told me it was for a different loader version. Right now I am using the one which comes with 1.02b. Yes - right now I have access to the system. Where do I get the firmware files only or hte *.ko files? The official debian site does not allow me to download those. Thanks IceBoosteR