Jump to content
XPEnology Community

unmesh

Member
  • Posts

    167
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

unmesh's Achievements

Advanced Member

Advanced Member (4/7)

0

Reputation

  1. Updated from 7.2.1 U3 to U4 and Control Panel won't load though Package Center, File Station and Storage Manager will. I've tried Chrome/Edge/Firefox and incognito mode and cleared caches in each to no avail. Any suggestions?
  2. Successfully installed on a test basis though on Proxmox rather than ESXi! Need to decide between baremetal bootloader on USB stick with NVMe as cache and Proxmox-on-NVMe with bootloader as VM for production. Thanks
  3. 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
  4. This could be a promising upgrade to my DS220+ if it can run Xpenology https://www.cnx-software.com/2023/10/25/aoostar-r1-an-intel-n100-2-bay-nas-mini-pc-and-2-5gbe-router/
  5. I just got a new hard drive and copied all the files over from another NAS that serves as a nearline backup
  6. 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.
  7. For anyone that is running on a N40L or N54L, did you have to manually adjust the sata related parameters in user_config.json to get the machine to boot into DSM? Mine was running on bootloader 0.8.0.4 but is not booting DSM on the latest 0.9.4.6
  8. 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?
  9. Which bootloader did you use? I'm currently on TCRP 0.8.0.4 and DSM 7.1.0U4
  10. @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
  11. 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)"
  12. For those running on VMware, what version of Linux are you configuring the VM to? And are the SATA ports for the bootloader and storage drives to be assigned in a certain order? Thanks
  13. 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.
×
×
  • Create New...