Jump to content
XPEnology Community

spiderben25

Member
 View Profile  See their activity

  • Posts

    24

  • Joined

  • Last visited

 Content Type 

Posts posted by spiderben25

    DSM 6.1.x Loader

    in Loaders

    Posted

    Press the down arrow (or any key) multiples times during the boot sequence in order to access jun's loader boot menu (if you don't press anything it will default to the standard boot), then you will have several choices : standard boot, reinstall, force install, amd boot (that's the one you want to try) and vm.

    DSM 6.1.x Loader

    in Loaders

    Posted

    I just created a new boot drive with the latest loader, problem remains the same...

     

    EDIT : got it working!

     

    For anyone running baremetal and experiencing trouble getting an IP with update 9, try the "AMD" boot entry on the boot menu, even if you're not using AMD hardware.

    DSM 6.0.2-8451 Update 9

    in Archives

    Posted

    Je suis en baremetal sur un HP N54L.

    Je suis passé de update 7 à 9, avant de voir les posts d'avertissement (grosse erreur...), résultat plus d'accès au NAS.

    Je viens d'essayer de refaire une clef avec le loader 1.01 (j'étais en 1.0), ça n'a malheureusement rien changé. Je sais pas trop quoi faire du coup pour débloquer la situation.

    DSM 6.1.x Loader

    in Loaders

    Posted

    Hi,

    After writing the latest .img file (the 30/10 one) with Win32DiskImager, I can't access it from my Windows machine in order to edit the grub.cfg file. It just doesn't pop up in the Explorer. Same on my Mac.

     

    With the other XPEnoboot img files I didn't have this problem, the USB drive was accessible directly in Windows explorer.

     

    Thanks for any help provided.

    Just remove the key and plug it again.

    :smile:

     

    This is because Jun uses EFI partition table to create the image instead of MBR. You won't be able to see the usb content with Windows 7. With Win 10 you will without any problem. With Mac OS, you will not be able to see the partition as well so you will need to issue the following commands:

    diskutil list

    this should bring the list of disks available. In my case it's:

    /dev/disk0 (internal, physical):
  #:                       TYPE NAME                    SIZE       IDENTIFIER
  0:      GUID_partition_scheme                        *640.1 GB   disk0
  1:                        EFI EFI                     209.7 MB   disk0s1
  2:                  Apple_HFS El Cap_TESTING_ENVIR... 214.1 GB   disk0s2
  3:                 Apple_Boot Recovery HD             650.0 MB   disk0s3
  4:                  Apple_HFS El Capitan              424.5 GB   disk0s4
  5:                 Apple_Boot Recovery HD             650.0 MB   disk0s5
/dev/disk1 (internal, physical):
  #:                       TYPE NAME                    SIZE       IDENTIFIER
  0:      GUID_partition_scheme                        *640.1 GB   disk1
  1:                        EFI EFI                     209.7 MB   disk1s1
  2:                  Apple_HFS Mac 1                   639.8 GB   disk1s2
/dev/disk2 (internal, physical):
  #:                       TYPE NAME                    SIZE       IDENTIFIER
  0:      GUID_partition_scheme                        *2.0 TB     disk2
  1:                        EFI EFI                     209.7 MB   disk2s1
  2:                  Apple_HFS Backup_OSX              1000.0 GB  disk2s2
  3:                  Apple_HFS Backup_DATA             999.9 GB   disk2s3
/dev/disk3 (external, physical):
  #:                       TYPE NAME                    SIZE       IDENTIFIER
  0:      GUID_partition_scheme                        *4.0 GB     disk3
  1:                        EFI NO NAME                 31.5 MB    disk3s1
  2:           Linux Filesystem                         15.7 MB    disk3s2
  3:        Bios Boot Partition                         4.2 MB     disk3s3

     

    find the EFI disk of the USB key. Mine is disk3s1 as you can see above. Then issue:

    mkdir /Volumes/efi

    followed by

    sudo mount -t msdos /dev/disk3s1 /Volumes/efi

     

    Note I have used disk3s1 in my last command. Your disk ID might not be the same so pay attention to what you are doing.

    Thanks that was exactly that! I'm indeed using Windows 7. Used the diskutil command on my Mac and it wen through.

    DSM 6.1.x Loader

    in Loaders

    Posted

    Hi,

    After writing the latest .img file (the 30/10 one) with Win32DiskImager, I can't access it from my Windows machine in order to edit the grub.cfg file. It just doesn't pop up in the Explorer. Same on my Mac.

     

    With the other XPEnoboot img files I didn't have this problem, the USB drive was accessible directly in Windows explorer.

     

    Thanks for any help provided.

    MyDS Center not working on 5.1 XPEnoboot

    in Packages & DSM Features

    Posted

    to make clear, i've something like this:

    APPEND root=/dev/md0 ihd_num=0 netif_num=4 syno_hw_version=DS3615xs sn=B845R4565 mac1=0011223344BBFF vid=0x0EA0 pid=0x2168 loglevel=0 vga=0x305

    After mac1= you can add mac2= and so on.

    Thanks, ill try

     

    Tried this, still not working. I used the real Mac of my NIC and an original serial number from a DS413j. What I don't understand is why it doesn't work anymore while it worked with DSM 5.0.

    MyDS Center not working on 5.1 XPEnoboot

    in Packages & DSM Features

    Posted

    Hi,

    I would like to know if I'm the only one having this problem, and if not, if there is some sort of fix for that.

    It's impossible to connect to MyDS Center on 5.1 (XPEnoboot), it says there has been an unknown error. Therefore, it's impossible to use Quickconnect or DDNS.

    Prior to upgrading to 5.1 (I was on 5.0 nanoboot), it worked properly, and I didn't change my password or anything else.

     

    Thanks for any informations on this matter.

    Change a serial number.

    Already tried that, doesn't work...

    MyDS Center not working on 5.1 XPEnoboot

    in Packages & DSM Features

    Posted

    Hi,

    I would like to know if I'm the only one having this problem, and if not, if there is some sort of fix for that.

    It's impossible to connect to MyDS Center on 5.1 (XPEnoboot), it says there has been an unknown error. Therefore, it's impossible to use Quickconnect or DDNS.

    Prior to upgrading to 5.1 (I was on 5.0 nanoboot), it worked properly, and I didn't change my password or anything else.

     

    Thanks for any informations on this matter.

    [SOLVED] HP Proliant N40L MicroServer native support

    in DSM 5.2 and earlier (Legacy)

    Posted

    Hi,

     

    Yes I connected the white molex connector to the ODD power cable (I had to remove a cable tie), the length was perfect. I didn't try it without it, and I'm a bit lazy so I don't think I will try it to disconnect it to see if it works :grin:

    The black connector purpose is to provide external USB 3.0 ports on cases that offers those ports on the front panel for example. It's not usable in the N54L.

     

    About your spinning down issue, I'm sorry but I won't be of much help, I run Transmission on my NAS with about a thousand torrents on it, so the drives are kinda always busy...

    NEW Update: DSM5.0-4528

    in General Installation Questions/Discussions (non-hardware specific)

    Posted

    If you're using the nanoboot image available on xpenology.nl, there is a couple of .lst files created on the thumb drive used to define menu parameters.

    You can edit the default values.

    sn= is the serial number that will appear on mydscenter, if you want it to be unique you can change it. Personally I used a number similar to my DS413j

    vid (vendor id) and pid (product id) must match the values that define your USB thumb drive if you want nanoboot to hide it to DSM so it doesn't appear as an USB share.

    On a Mac you can easily check this value out in About my Mac, on Windows there should be a similar software to do that.

    NEW Update: DSM5.0-4528

    in General Installation Questions/Discussions (non-hardware specific)

    Posted

    Just updated from 5.0-4493u7 to 5.0-4525 on my HP N54L (bare metal).

    I downloaded boot image from xpenology.nl (thanks btw), edited the .lst files (sn, vid and pid so I have a custom SN and my usb thumb drive doesn't show up in DSM) like the previous installation.

    Selected upgrade on nanoboot menu, launched Synology assistant, choose to migrate, used the DS3612xs 4528 pat file and that's all :smile:

    [SOLVED] HP Proliant N40L MicroServer native support

    in DSM 5.2 and earlier (Legacy)

    Posted

    You could take a look at this tread http://xpenology.com/forum/viewtopic.php?f=2&t=2690. See Robjo's post and link for a cheap card - here is an up to date link to the same seller PCIE low profile USB3 with NEC Chip. It works in the N40L using the latest Nanoboot, so it should work in the N54L without an issue. You will also need a power cable to connect up to the Molex on the card.

     

    Just to report back, I installed it this morning, it works flawlessly out of the box (DSM 5.1-4528 on latest nanoboot, bare metal installation). I used the ODD molex cable to power it, not sure if it's really needed though.

    Losing connection to my nas on the network

    in Archives

    Posted

    I have the same problem. Every few weeks, it looses the connection (when connecting using SSH I get Host is unreachable), and as soon as I plug out then in the Ethernet cable it starts working again immediately.

    Using latest DSM 5.0 4493u7, Nanoboot, HP N54L.

     

    Might be something with the DHCP server ? In DSM IP address is set to automatically and in my router the MAC address of the NAS defines a static IP.

×
×
  • Create New...