Jump to content
XPEnology Community

fma965

Member
 View Profile  See their activity

  • Posts

    68

  • Joined

  • Last visited

 Content Type 

Posts posted by fma965

    gnoboot & DSM 5.0-4482 - Experiences?

    in AMD

    Posted

    First of all want to thank everyone for this awesome project!

    I do not use any virtual machine so all I did was on my homemade nas

     

    My setup:

    Disk 1 (very small in size) I keep the main DiskStation software and also it becomes volume 1 for my apps in use

    Any other Disks will become Volume 2 for data …anyways frustrated because the 4482 update.

     

    This is what I did:

    Made me a gnoboot-alpha10.5 boot drive and install DSM_DS211_4458 once finish I turn it off and replaced the usb boot drive with the NanoBoot-5.0.2.2-fat usb drive and installed the famous DSM_DS3612xs_4482 as explained by fma965. Everything working great so far and I even switch usb boot drives and works great with either one!

     

    Thank you so much guys.

     

    Thanks, Glad it helped :smile:

    Trial of Nanoboot (4493) - 5.0.3.1

    in DSM 5.2 and earlier (Legacy)

    Posted

    Short question.

     

    Background: I did an update with Nanoboot 5.0.2.2 yesterday directly from Trantors beta 5, very easy. Web-GUI said its migrateable and I chose Migration (keep files and most of the settings). I assume clean installation (keep your files) would have led to a swipe of the hard drives.

    Uploaded original pat file and it works without additional adjustments. Maybe that helps some people.

     

    Question: In the pic you'll see that the little one as a reminder of an update did not disappear. Upon checking, it says, latest version installed. Why doesnt the red 1 disappear?

    a0c24e

    i don't have that issue

    Trial of Nanoboot (4493) - 5.0.3.1

    in DSM 5.2 and earlier (Legacy)

    Posted

    Does anybody have a guide of how to install nanoboot with 4482 from scratch, on a clean new physical machine?

     

    fma965 made a very useful tutorial (thank you fma965!) http://cyanlabs.co.uk/tutorials/synolog ... o-nanoboot but it's talking about migration from gnoboot. Unfortunately it's a bit confusing, also because there's a lot of virtualization stuff all over the place.

     

    Ok so people seem to want a guide specific to not using ESXi, i will see what i can do, as for fresh installs... well i can't seem to get that working, my best answer is just install gnoboot, once its booted to synology "desktop" shut it downa dn replace gnoboot with nanoboot then select upgrade/downgrade etc. etc.

    ESXi Updating from Gnoboot to Nanoboot - Guide!

    in Archives

    Posted

    *waiting patiently for the HP Microserver guide* :wink:

     

    EDIT: so what's the difference between the modified and unmodified PAT file?

     

    EDIT2: when we moved from trantor -> gnoboot, we used "install" from syno assistant instead of the website. Does the website method retain user data?

     

    *waiting patiently for the HP Microserver guide* :wink: --- it's essentially the same just don't use the vmdk and instead write the img to usb with win32diskimager. :smile:

     

    not sure on whats different but at a guess i would say it's patched to work with non synology hardware, but with later versions of nanoboot the patching is done on the fly and stock pat file is used... for neive people who think using official file is more secure... well it's not, the file can be modified at run time and a averge user wouldn't know, not saying it is done or that it's done with malicious intent just saying.

     

    AFAIK they are the same, i don't get all the complaining about me using the install option before as it worked fine for me yet people carried on complaining.

    Trial of Nanoboot (4493) - 5.0.3.1

    in DSM 5.2 and earlier (Legacy)

    Posted

    I'm running into an issue where it looks Nanoboot is not pulling IPs for the NICs. For hardware, i'm using the c2750d4i with marvel NICS coming from DSM5 with gnoboot 10.5a.

     

    I get the error below on boot:

     

    Running /usr/syno/etc/rc.d/J)3ssdps.sh...

    /usr/syno/sbin/minissdpd

    Usage: /usr/syno/sbin/minissdpd [-d] [-6] [-s socket] -[p pidfile] -i [-i ] ...

     

    < interface> is eitehr an IPv4 address such as 192.168.1.42, or an

    interface name such as eth0.

     

    By defaulth, socket will be open as /var/run/minissdpd.sock

    and pid written to file /var/run/minissdpd.pid

    start SSDPD failed.

     

    From the guide off cyanlabs, the execution line should be:

    /usr/syno/sbin/minissdpd -i eth0 -i eth1

     

    Any insight would be appreciated. Thanks in advanced.

    it probably doesn't have drivers for that NIC, also what do you mean by "From the guide off cyanlabs, the execution line should be: /usr/syno/sbin/minissdpd -i eth0 -i eth1"?

    Trial of Nanoboot (4493) - 5.0.3.1

    in DSM 5.2 and earlier (Legacy)

    Posted

    Ahh oke!

    I understand.

     

    I do have another question though.

    I now have a 1GB disk that is not initialised.

    See screenshot:

    https://www.dropbox.com/s/fvl3h92dqbf5w ... .57.20.png

     

    Is that correct? Can it be removed?

    read the bottom part of my tutorial :smile: it's the VMDK file once again, best bet would be to convert to a read only format but i haven't the time currently.

     

    if you set the vdmk at IDE, and then rmmod=ata_piix it would solve it most likely. Right now removing ata_piix is broken, since it's compiled into the kernel rather than a kernel mod. The creator will fix it next release.

     

    Yeah i know thanks though, Obviously since it's broke in this realease it seems pointless mentioning that :smile:

    Trial of Nanoboot (4493) - 5.0.3.1

    in DSM 5.2 and earlier (Legacy)

    Posted

    Thanks to your guide I have installed a new VM with Nanoboot and original 4482 pat file. :grin: :D

    Your tip to delete the vmdk and re-upload when the install does not reboot, did the trick for me!!

     

    Thanks mate!

    Great, From what i can tell thats due DSM installing it self over the VMDK file. So close to beating my visitor count on my website :smile:

    Trial of Nanoboot (4493) - 5.0.3.1

    in DSM 5.2 and earlier (Legacy)

    Posted

    Yes, he could have just sent you a PM instead...

    But well... Never mind! :grin:

    i believe it was for me atleast, it makes sense since he posted it in all the same places i did

     

    Can we use any other PAT file or must be DSM_DS3612xs_4482.pat?

     

    Possible to use DSM from other hardware, like DS412+ (DSM_DS412+_4482.pat) or DS413 (DSM_DS413_4482.pat) ?

     

    Thank you,

    Alex_G

    Why? why would you even want to?

    Gnoboot, Trantor, and now Nanoboot. Security?

    in Archives

    Posted

    Ill stick to GnoBoot I feel safe with what he is putting out.

    in my opinion gnoboot is dead, no activity from him in a while, nanoboot is faster and is based on 5.0 source so better... but its ofcourse up to you xD but since you commented on my site im guessing your tempted haha xD

    gnoboot & DSM 5.0-4482 - Experiences?

    in AMD

    Posted

    Nanoboot worked fine on my VirtualBox test instances :smile:

     

    Used VBoxManage to create .vdi from .img

     

    VBoxManage convertfromraw -format VDI NanoBoot-5.0.2.1-fat.img NanoBoot-5.0.2.1-fat.vdi

    or just use the provided vmdk file? or doesn't vmdk work on virtualbox?

    gnoboot & DSM 5.0-4482 - Experiences?

    in AMD

    Posted

    nanoboot run with not modified pat file

     

    you can use legacy DSM_DS3612xs_4482.pat

     

    ok no need to cry like a little baby about it... aka large and red text. geez. i didn't even know that cuz i dont read fricken chinese/japanese

    Trial of Nanoboot (4493) - 5.0.3.1

    in DSM 5.2 and earlier (Legacy)

    Posted

    Im in the situation that i have a HP MediaSmart Server EX 490 with upgraded CPU. For those of you who don't know the box it's a small server holding up to 4 drives. It is born with Windows Home Server, but that software isn't for me, since I find it very resource heavy. There is no display port and therefore I'm not able to connect a monitor.

     

    I managed to install the Xpenology DSM 4.2 build on it and it has been working great for a long time now, but the last couple of days the Resource monitor tells me that a task named LIBC5 is using 49% cpu (and there is 2 of them) so my fan is completely fucked.

     

    Now for the question:

     

    Is there a way to install DSM 5.0 (4482) with or without nanoboot/gnoboot when I'm not able to connect a monitor. For me it seems like the guides for both gnoboot and nanoboot requires a monitor. Anyone who could clarify this or perhaps have some idea's on how to install the DSM software?

    Essentially you could just press down and enter and guess the key combination :grin: or ofcourse the better idea is to use ESXi since that is managed remotely from another system, hence why many are using it with headless severs :smile: Either way i have guides on how to install gnoboot on both esxi and without and nanoboot, they technically require a monitor but it's essentially down enter or down down enter :smile: just look at the pictures :smile:, my tutorials can be found

×
×
  • Create New...