Jump to content
XPEnology Community

manfriday

Member
  • Posts

    208
  • Joined

  • Last visited

  • Days Won

    3

Posts posted by manfriday

  1. **Limited Test**** Your mileage may vary** I did this as a test a couple of weeks back, I was testing the Samsung HD204UI issue. Installed 4.3 on 1 single drive system, two packages and one userid. Everything was still there after the upgrade to Nanoboot 5.0-4258.

  2. Feel free to add your experiences regarding removing/adding HDD. I have done this before but do not remember it responding like this.

    System in Zotac Intel Atom based board running DSM4.3-3810 (still) 4x2TB and 2x3TB, 2 of the 2TB drives are Samsung HD204UI so I decided to swap them out as I am close to capacity plus want to finally upgrade to 5+.

    Pulled one of the Samsung HDD and replace with 3TB WD green. System gave an expected response to this, DSM goes into rebuild mode and is now Checking Parity Consistency.

    I see plenty of CPU activity, no HDD activity in widget on screen but I open resource monitor and I/O a plenty is going on.

    My question is I remember the last time I did this the Checking Parity Consistency showed a percentage completed as it was underway. I am not seeing that count and I started the install about 4 hours prior to this post

  3. managed to upgrade to 4528 but not without minor issues.

    New IMG file to USB

    Edit 3 files to change SN, VID & PID

    shutdown DSM

    replace USBs and power up

    open Syno Assistant and find Migrate-able and select

    follow the bread crumbs on GUI

    ----upon reboot screen show a line of garbled characters and no boot

    tried 3 times to Ctl Alt Del, same result

    power off and on, enter BIOS set USB as boot.

    DSM starts and Starting Services sits there for 5 mins

    Install completes.

     

     

    HW= Atom based Zotec board, never had issues with booting before

  4. Has anyone upgraded with Samsung drives of the model type- HD204UI? If so, what happens?

     

    Answering my own question:

     

    Installed DSM4-3 3810 on test rig with only 1 HDD Samsung HD204UI.

    Installed a couple of packages, Antivirus and Download Station

    Added a user

    Let install complete.

    Insert new USB drive and reboot

    Select install/upgrade from menu.

    Select PAT file d/loaded previously

    Installation completed without issue

    Logon to DSM with Admin

    attempt to open Storage Manager - get error saying no privilege and kicks me straight out to Logon Screen

    Log back in with Admin

    select control panel and straight to update to patch 1

    install patch and reboot

    Logon with Admin

    Open Storage Manager - no issue

    Check packages

    Check userid

    All is right with DSM

  5. thanks for the link!

    this work around from said link

    Instructions on how to change this setting (no warranties):

     

    - Log in to your NAS with SSH using the root account (not admin, you need root rights)

    - type "vi /etc/synoinfo.conf" to open the file in VI editor

    - Using your cursor keys, scroll down to the line that says allow_HD204UI="yes". In my version of the file, it's at line 214, at 64% under # Fixed items (lol)

    - Press "i" or hit the insert key to enter edit mode of VI editor

    - Write "#" in front of the line, to comment it: # allow_HD204UI="yes"

    - Press ESC to enter command mode

    - Type :wq and hit return to write the file and quit VI editor

    - Type reboot and hit return to reboot your NAS.

     

    After your NAS has rebooted, you should be able to access the web interface again.

  6. 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:

     

    Just for my clarification:

    When you say .lst files, you mean .debug, .install & .nano.

    Did you change the SN, VID & PID to the same values in all files

    Cheers

    MF

  7. 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:

     

    Just for my clarification:

    When you say .lst files, you mean .debug, .install & .nano.

    Did you change the SN, VID & PID to the same values in all files

  8. 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.

     

    Many thanks for this. I used XPEnology_VenderFilePatcher_v1001.exe previously but that was during the early daze of getting up and running, have not had to use it subsequently with patches etc.

    Cheers

    MF

  9. If you want to start slowly with VM maybe Workstation or VMWare Player. I run VM Workstation under Win 7. I have multiple VM machines (not all powered on at once) and DSM. DSM has 640MB allocated and 2 CPU cores. main system is Shuttle XPC with i5-2500 CPU- 16GB and 5x128GB SSD. Each SSD serves a particular function. 3 are used for VM systems. I have an eSATA card and Sans Digital 4xSATA case, 3 drives are for DSM. Map the drives as physical. The DSM is purely to test updates and other assorted tests

  10. -downloaded update 5

    -stop at Update now

    -run script to execute commands

    -continue with update

     

    8mins in system available but msg says volumes are outside of operating temps

    -reboot (stuck at Starting Services in DSM assistant for a long time)

    System up and volumes not visible

    -shutdown

    -come back tomorrow

     

    ....tomorrow

    -restart , all volumes visible, permissions screwed

    -fix permissions

    -Done!

×
×
  • Create New...