Jump to content
XPEnology Community

nick w

Member
 View Profile  See their activity

  • Posts

    70

  • Joined

  • Last visited

 Content Type 

Posts posted by nick w

    New HP Gen 8 Installation, best practice?

    in DSM 5.2 and earlier (Legacy)

    Posted

    Just purchased a HP gen 8 for Xpenology and I'm slightly overwhelmed with the install options available to me, just wondering if anyone could give me some best practise advice so I can get it right first time! I've had a little search but most of the threads I'm finding seem to be quite old (not sure if the information is relevant anymore!).

     

    I planning to use the machine for only Xpenology, is there any point in me running Xpenology under ESXi? If not then I will keep it to a bare metal install.

     

    I was planning to use the built in micro SD reader however posts online seem to advise against this and to just stick with a USB drive, is this still the case?

     

    I'm planning to update the drivers etc to latest versions before the install, any known issues with doing this?

     

    I will be using 2 x 4TB WD Reds for now, looking to grow as they fill up, I've seen lots of different configurations of the drives, some involving ESXi, some not. Is there a general consensus on which is best to use?

     

    +any other tips or suggestions regarding the Gen 8's?

     

    Many thanks in advance!

     

    You have 2 main options to plan your install

    Virtulise it of baremetal install

     

    xpenology.nl has guides on both paths to your install

     

    Xpenology.nl is a great place for guides....

     

    N

    HP Gen7 n54L - Anyone successful in updating to 5.2?

    in AMD

    Posted

    have you tried this

     

    For those who made th Update to 5.2-5565 Update 1 and can't access the dsm:

     

    1. First to get access

     

    crowpet wrote:Think i got it on my n54l with Monitor and keyboard localy atached!

     

    1. Login as root

    2. type su

    3. ifconfig eth0

    - I only had a ip v6 adress -> so no connection

    4. type ifconfig eth0 #IPofNAS# netmask 255.255.255.0 up -> now you can connect via browser on the given ip

    5. Login in DSM in Browser

    6. Goto "Controlcenter" -> "Network"

    - Check the settings on your NIC "LAN1" and tourn off ipv6

    - I have set the ip to static

     

    Don't reboot!!!

     

     

     

    2. Now you can Trry to downgrade (migration install) - to keep your app's and configs

     

    - Ive done the steps here "http://xpenology.me/how-to-downgrade-from-dsm-5-2/" but ive installed the "DSM 5.2-5565" from here "http://xpenology.me/downloads/"

     

    - After the migration install iam up an running and everthing seems fin now :smile:

     

    Dont update again or the dsm will got the same errors!!!!

     

     

    Hope this is a help

     

    3. Think about a clean install / test system

    Would you suggest not going to update 1?

     

    Shall I avoid it now when i got to 5.2

     

    Thanks. N

    HP Gen7 n54L - Anyone successful in updating to 5.2?

    in AMD

    Posted

    The process I used to update my G7 N54L Server (going from 5.1-5055 Update 5 to 5.2-5565 Update 1)

     

    Power Down Server

    Take out usb boot drive and update with latest boot image / re-insert usb drive

    Power On

    Select XPEnology DSM 5.2-5565 top boot option NOT debug or install/upgrade option

    wait for it to boot

    log in via web browser

    Download DSM 5.2-5565.pat from http://www.xpenology.nl/xpenology-software/

    update and let it reboot

    log back in via web browser

    go to control panel - update and restore, check for updates, let it download and install update 1

    wait for it to reboot

    Done

    So why not upgrade? Thats what I normally do during upgrades. If I don't select update do i lose my apps?

    Thanks. N

    HP Gen7 n54L - Anyone successful in updating to 5.2?

    in AMD

    Posted

    Has anyone successfully updated to 5.2 on an HP Gen7 Micro Server

     

    The process -

    Write Image to new USB

    Power Down Server

    Take out old usb and insert new one

    Power On

    Select Update/install/downgrade

    wait for it to boot

    synology assistant - connect to server

    Migrate

    = Done

     

    DSM 5.2-5565 PAT download c50385e13495fef366fbd590bbe376fb

    I wont go to update 1 just yet

    Is that correct?

     

    Thanks

    N

    Can we change the forum rules?

    in Archives

    Posted

    Hello.

    I try to solve problems with spam on this week.

     

    Make it a paid site for new members. $5 in order to see and post on the forums. That will help pay for web hosting... and if spammers want to pay $5 to spam your site, then they get banned. Win win.

    Not a very good idea imo. Would you pay?

     

    Sure. It isn't much.

    Really. People would defect to free sites..

    A forum I browse closed during peak periods to non paying members. People ended up leaving to other sites and it disappeared from the web.

    Raid0 volume crashed

    in Archives

    Posted

    Hi,

     

    This is all the knowledge I have, try these steps. Unfortunately if this does not work, there's nothing I can help you with.

    Make sure you have mdadm and lvm2 packages installed in your Ubuntu Linux.

    For my test, I did an installation of Ubuntu and made sure NOT to use Logical Volume Management so that I was sure that my tests only show results of the synology volume. Don't know how bootable USBs show up, but I guess that will not be an issue.

     

    FIRST OF: become and stay(!) root by typing "sudo su -" (don't forget that last minus-sign) and create a mount point you can use by creating a directory:

    mkdir /mnt/syno

     

    mdadm --detail --scan

    Try this, see if your RAID details are visible

     

    fdisk -l

    Check if you see a mdxxx device. In my test, I saw a /dev/md127. Try to mount it, create a mount point somewhere (remember that mkdir /mnt/syno???) and try to mount: "mount /dev/mdxxx /mnt/syno".

    But probably you will get an error (unknown filesystem type 'LVM2_member')

     

    lvmdiskscan

    This will output all kinds of info. You are hoping to see something like /dev/vg1000/lv and-or /dev/mdxxx and "1 LVM physical volume"

     

    lvdisplay

    You should see something like "LV Path /dev/vg1000/lv".

     

    vgdisplay

    Should display the volume name

     

    lvscan

    Should return the volume of your synology. When you see "Active", you are as good as set. If you see your volume, but "INACTIVE",

    try "modprobe dm-mod" followed by "vgchange -ay" and run lvscan again.

     

    If it's ACTIVE (for example, you see the output "ACTIVE '/dev/vg1000/lv' [xxxx GiB] inherit" you should be able to mount it with

    mount /dev/vg1000/lv /mnt/syno

     

    That's all the info I can give you. I wish you all the luck!

    Amazing post. So good I have saved it should I have any issues. Thanks. N

    DSM 5.0-4493 Update 7

    in DSM Updates Reporting

    Posted

    Nick,

    I don't see any issue with going straight from U1 to U7 although you might need to make sure your boot .iso/usb is 4493 _U7 (not too sure if this is a show stopper or not).

     

    Regarding the magical commands, here is how the update procedure works, as I understand it:

    Downloading (either straight from synology, or manual from a .pat file) creates two files, one is the .pat file, the other is an "Update info" file.

    The .pat file is just a compressed archive, ins some cases the synology will uncompress it to /volume1/@tmp/some directory, in some cases it just downloads the .pat to /volume1/@temp/some_number.pat. Whether the .pat file is uncompressed or not seems to be dependant on how major the update is, but is anyways uninmportant with respect to the "magical Command"

     

    The "update info" file will either just have a string indicating where the uncompressed.pat file is, or a list of each individual update and where they are if the update is uncompressed by the download mechanism.

     

    On a real synology there is a flash memory device, which contains the boot code for the box. This device is updated by a patch called "flashupdatedeb". Since our xpenology boxes don't have a real flash device (this is why we boot from a usb or .iso image), we can't update that device. Presumably the synology update procedure will fail if it cannot update the boot device (obviously the first test for the update procedure is "Where did I boot from?, can I update it? If No, exit".

     

    What the magical commant does is modify the "update info" file named "autoupd@te.info" , changing every instance of "flashupdatedeb" to "flashupdatedeb1" i.e. to an update that does not exist in the extracted directory structure. The sed command makes a 2nd copy of the "update Info" called "autoupd@te.info1, which we overwrite the orginal autoupd@te.info with via the "mv" command.

     

    Fortunately the synology update procedure doesn't do any testing to see if every update listed in the .info file is actually there, so that when you then click on "update" in the GUI, the software then just steps through the updates listed in the info file, ignoring the flashupdatedeb (because it isn't listed) and wordlessly skipping the updateinfodeb1 (because it doesn't exist), but it updates everything else.

     

    On updates that don't include changes to the flashdevice the magical command isn't needed.

     

    The update info file is just a text file, you can look at it with any editor/viewer. The .pat file is just an archive, you can expand it with tar -xvf or 7zip in windows and see what is inside.

     

    Andrew

     

    Super post. Have a beer token from me!

    Thanks Andrew for taking the time out to type that.

    Synology assistant confirmed i was on 4493 so simple update. Hung on restart but once forcibly shutdown, it was back up with no issues.

     

    Thanks

    N

    Trial of Nanoboot (4493) - 5.0.3.1

    in DSM 5.2 and earlier (Legacy)

    Posted

    Today I tried to update from DSM4 3202 to DSM5 4588 and for some reason I cannot update with the synology assistent.

    If I use the NanoBoot 5.0.2.4 or GNOboot 10.5.7 stick the synology assistent says my configuration is lost.

    If I use the original stick, my DSM won't properly boot and shows up in the synology assistent with the wrong ip adres and stating that it is running DSM5 4482. But I can't get any data from the drives or shares.

    If I try to upload the original PAT file or a DSM4 (3211) I always get the error that the file is corruptes (error 13)

     

    Also, I see no red errors but with all the sticks I use to boot I get ' Startup daemons', date and time and "Excution error"

    I have a HP N36L

    What should I do now?

     

     

    Restore from backup... assuming you took a backup..

     

    I was on 4.3 Beta2, went to DSM5 4598 Nanoboot last night without any issues. SMOOTH!

    16TB so i was a little bit worried if it failed!

×
×
  • Create New...