Jump to content
XPEnology Community

unmesh

Member
 View Profile  See their activity

  • Posts

    167

  • Joined

  • Last visited

 Content Type 

Posts posted by unmesh

    Control Panel won't open after update

    in General Questions

    Posted

    16 hours ago, dj_nsk said:

    if you are using the Arc Loader in one of the latest versions (with "-next" in the name), then read the author's comments: "Rebuild Loader with CLEAN Config recommended. If you encounter issues with this version, please select "Force-Reinstall DSM" in Grub (First Boot Screen)."

     

    [add:] after "Force Reinstall", it will return to 7.2.1 Update 3 and work normally. Then you can reinstall Update 4

     

    Force Reinstall worked!

     

    Thanks

    Tutorial: Install DSM 7.x with TinyCore RedPill (TCRP) Loader on ESXi

    in Tutorials and Guides

    Posted

    On 11/26/2023 at 4:08 AM, dj_nsk said:

    not really. With Arc:

    1. Skip the "Preparing the TCRP Image" section - just download the latest release arc-XXX.vmdk-flat.zip and unzip it
    2. ... 
    3. "Select Add hard disk (existing hard disk) and choose the TCRP vmdk created in the previous step" Upload (upload alternately both files received in step 1) - arc.vmdk - Select
    4. ...
    5. Skip the "System-Specific Parameters and SATABOOT" section
    6. Boot to Arc configuration menu, choose model and DSM version, Enter, Enter, ... Ok Rebooting to DSM :)

    With Arc, does the VM always boot into Arc first to give you an opportunity to reconfigure the loader? If not, how does one do that?

     

    Also, I will be running on a PC with an i3-8100 connected to a Q370 and one each NVMe SSD and SATA HDD. Given your installation history, should I use DS918+ or DS920+ as the model?

     

    Thanks

    Automated RedPill Loader (ARPL)

    in Loaders

    Posted · Edited by unmesh

    On 11/7/2022 at 2:33 AM, Orphée said:

    Hi,

     

    3rd in a raw !

    I updated my N54L from TRCP v0.8 DSM 7.0 to latest DSM with ARPL, really great to use web GUI, just so easy to use !

    (I took care about direct boot TRUE)

    Thanks :)

    I tried using ARPL for the first time on my N40L and it seems to be in a bootloop when trying to boot DSM DS3615xs 7.1.1 .

     

    What did you mean by "direct boot TRUE"?

     

    P.S.: I have a Realtek PCIe GbE NIC in addition to the built-in Broadcom NIC, both of which were recognized in build mode.

    Recovering from hard drive crash

    in DSM 6.x

    Posted

    I have DSM 6.2.3 U3 running on Jun's bootloader on ESXi 7.0 U3 with hard drives passed through using RDM. One of them reported as crashed earlier today. Fortunately, I have a backup but would like to get this server up and running again.

     

    I tried deleting the storage pool in DSM and re-adding it but it still shows crashed. I looked at the drive using ESXI SMART and got this:

    Parameter                          Value  Threshold  Worst  Raw
    ---------------------------------  -----  ---------  -----  ---
    Health Status                      OK     N/A        N/A    N/A
    Write Error Count                  0      0          N/A    0
    Read Error Count                   251    51         N/A    251
    Power-on Hours                     34     0          34     130
    Power Cycle Count                  52     0          N/A    52
    Reallocated Sector Count           0      140        N/A    0
    Drive Temperature                  32     0          N/A    32
    Sector Reallocation Event Count    0      0          N/A    0
    Pending Sector Reallocation Count  2      0          N/A    2
    Uncorrectable Sector Count         0      0          N/A    0
     

    Does the combination of the read error count and the pending sector reallocation count explain why DSM cannot use this hard drive?

     

    Anything else to try before I get and install a new hard drive?

     

    DSM 7.x Loaders and Platforms

    in Tutorials and Guides

    Posted

    On 1/18/2023 at 3:33 AM, glenshep said:

    Installer DS3615xs DSM 7.1.1. Bare Metal HP54L

    Ssh tc@192.168.1.73 in my case
    Password - P@ssw0rd

    ./rploader.sh update
    ./rploader.sh fullupgrade
    ./rploader.sh identifyusb now
    ./rploader.sh satamap
    ./rploader.sh serialgen DS3615xs realmac
    ./rploader.sh backup now
    ./rploader.sh build ds3615xs-7.1.1-42962
    ./rploader.sh backuploader
    exitcheck.sh reboot

     

    works perfect for me ;) NJoY

     

    Which bootloader did you use? I'm currently on TCRP 0.8.0.4 and DSM 7.1.0U4

    DSM 7.x Loaders and Platforms

    in Tutorials and Guides

    Posted · Edited by unmesh
    Clarified the ask

    @flyride

     

    I've been running DSM6 on ESXi 7.x with RDMed drives for many years now and would like to add a new server but running Proxmox because its hardware will not be supported by ESXi 8. Regarding your table in the first post, are there server CPU architecture considerations that would affect the choice of the Synology platform even if only NAS functionality is required or is that all virtualized away?

     

    Thanks

    Automated RedPill Loader (ARPL)

    in Loaders

    Posted

    36 minutes ago, Kanedo said:

     

    For VMware ESXi, I've been using "Other Linux x64" without issues.  Would love to hear if there's a better one to pick.
    The only order that matters is that you configure VMware to boot from the loader SATA drive.

    One thing I discovered with ESXi 7.0 is that "Other Linux (x64)" doesn't allow you to add SATA controllers and I had to pick "Other 5.x or later Linux (x64)"

    Tutorial: Install DSM 7.x with TinyCore RedPill (TCRP) Loader on ESXi

    in Tutorials and Guides

    Posted · Edited by unmesh

    On 7/13/2022 at 2:44 AM, phone guy said:

    After you have your xpenology setup, you can add another drive in proxmox and symbology dsm will auto detect it.

     

    Did you pass thru a pci card? Or sata controller? One just one hdd entirely thru proxmox to dsm?

    Just the hard drive using RDM

     

    And this should have said ESXi VM on this thread though I have a test VM on Proxmox too that I talk about on another thread.

    Tutorial: Install DSM 7.x with TinyCore RedPill (TCRP) Loader on ESXi

    in Tutorials and Guides

    Posted

    I've been successfuly running DSM 6.2.3 on the DS3615xs platform as a VM on ESXi7 with Jun's bootloader and a single RDMed hard drive for a while now and was wondering if there was any consensus on whether TCRP was stable enough to migrate one's data to it.

     

    If so, would a best practice be to first get DSM 7.1.0 up and running with a virtual disk as the target drive and then add the RDMed drive (and then optionally removing the virtual drive) or would that mess up the sata diskmap generation process that is done in TCRP?

     

    If I use the DS918+ platform instead of DS3615xs, would I be able to retain the data on the RDMed drive?

     

    Thanks

    ESXi to baremetal as a disaster recovery strategy

    in DSM 6.x

    Posted

    Today I tried to do this though a little differently than using a brand new USB bootloader.

     

    My ESXi XPE VMs use the synoboot.img file and a .vmdk "wrapper" rather than generating a .vmdk file, both in the datastore. I shut down the VM, used the Datastore Browser to copy the current version of the synoboot.img from the ESXi server to my Windows laptop and flashed it to a USB drive. I then put both the USB drive and the Hard drive from the ESXi server into the N40L and booted the machine. Since this was just a test, I did not bother re-editing grub.cfg to change the USB VID:PID or the MAC address.

     

    The bootloader showed its menu but DSM did not respond on the network. Should it have?

     

    The "wrapper" .vmdk is posted below

      

    # Disk DescriptorFile
version=1
CID=32963afe
parentCID=ffffffff
createType="vmfs"

# Extent description
RW 102400 VMFS "synoboot.img"

# The Disk Data Base 
#DDB

ddb.adapterType = "lsilogic"
ddb.deletable = "true"
ddb.encoding = "UTF-8"
ddb.longContentID = "e090c58a0ae239a6b3dc2e7b32963afe"
ddb.thinProvisioned = "1"
ddb.toolsInstallType = "0"
ddb.toolsVersion = "2147483647"
ddb.uuid = "60 00 C2 9a ee da ca 33-df 5e 04 3f 80 55 f9 62"
ddb.virtualHWVersion = "10"

     

     

    ESXi to baremetal as a disaster recovery strategy

    in DSM 6.x

    Posted

    I have a couple of DSM instances running as ESXi VMs with RDMed SATA hard drives and have recently begun thinking about a recovery strategy should I lose my sole ESXi server but not my hard drives. (I do have backups too in the form of baremetal but those are kept offline).

     

    Is there a way to create USB drives from the synoboot vmdk files, edit grub.cfg with the new VID:PID and MAC address and boot a new supported system off this USB with the hard drives moved to this new system?

     

    Or is it sufficient to create a new USB stick with the same version of bootloader, edit grub.cfg with the new VID:PID and the MAC address from the other system, and "reinstall" the appropriate version of DSM using the old credentials to the hard drives (that already have DSM on them)?

     

    Would I have to be concerned about the order of the drives on the new SATA controller?

     

    Thanks

    Xpenology and QNAP TR-004

    in DSM 6.x

    Posted

    Joining this party a bit late but I was successful in getting Moments with Face Recognition in a temporary installation in a Haswell based machine. I'm excited to consider this as an alternative to Google Photos.

     

    My production machines are either VMs on ESXi on Haswell or baremetal AMD machines as per my signature. Any hope of running on any of these?

     

    If the hardware is capable, is there even a non-destructive way to go from a 3615xs installation to a 918+ one?

     

    Thanks

     

     

×
×
  • Create New...