Jump to content
XPEnology Community

AllGamer

Member
  • Posts

    222
  • Joined

  • Last visited

Recent Profile Visitors

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

AllGamer's Achievements

Super Member

Super Member (5/7)

3

Reputation

  1. Does anyone know if ARC and/or ARPL supports LSI 9200 series controllers ? The last time I tried it wouldn't detect the drives properly with my ATTO ExpressSAS H60F I'm shopping for new 16 port cards to replace my old one. Seems like most people are now using LSI 9300 and 9400 series, but both of them are quite pricey.
  2. BeeStation BeePhoto BeeFiles Bee AdminCenter The actual product looks like a single drive DSM station, but it's all sealed, and it's heavily encouraging end users to use their C2 cloud platform. meh... no amount of marketing is going to make that popular even if they re branded it as a new fork of the DSM 7.2 If the goal is to have people use Synology C2 cloud services, people might as well just use Google instead.
  3. "Backup and Restore" from DSM 5.x becomes "Hyper Backup" in DSM 6.x / 7.x The backups from 5.x are recognized automatically and can be restored directly to 7.x machines. 99% of the settings and applications will get migrated / upgraded automatically, user accounts, network settings, folders, etc...
  4. I'm trying to use ATTO ExpressSAS H60F controller with the latest tinycore-redpill.v0.9.4.9 During the configuration portion in the initial TCRP setup, when I run : ./rploader.sh satamap it shows 0 (zero drives), but there are actually 24 drives plugged-in. It appears to have properly detected the controllers, but it doesn't see the HDDs are attached. surely enough after I run backup and build commands, then reboot and connect with Synology Agent the DSM welcome pages shows up with a warning about no drives installed. How do I go about making TCRP see my HDDs connected to the ATTO H60F ? Do I need another driver? Do I need to configure something else?
  5. It's not letting me edit the old post. I forgot to mention, for the physical upgrade, I simply took the HDD straight out from the old machine and inserted it into the new machine. If you doing an in-state upgrade, then simply replace the old USB key with 5.x loader, with a the new USB key with the Tiny Core Red Pill Loader for 7.x The first boot, you'll need to do the configuration once, and then you can pretty much forget it for a while until new version comes around. ./rploader.sh update ./rploader.sh fullupgrade ./rploader.sh serialgen DS3622xs+ realmac ./rploader.sh identifyusb ./rploader.sh satamap ./rploader.sh backup ./rploader.sh build ds3622xsp-7.2.0-64570 The PAT file version in the last command is most likely going to change over time, make sure to use the latest compatible version. If you are working on ESXi VMs, you'll probably need to do this before it boots properly. in a Terminal open a SSH shell to your ESXi server. switch to the location of your VM machine for the NAS: cd /vmfs/volumes/datastore1/<VM NAS machine name> then import the red pill loader image: /usr/sbin/vmkfstools -i tinycore-redpill.v0.9.4.9.vmdk DSM-rploader.vmdk Note: replace the red pill loader with the version you downloaded / uploaded to the VM.
  6. Just documenting this for reference, in case anyone was pondering if it can be done. So my starting device was XPEnology DS3615xs running DSM 5.x migrating to XPEnology DS3622xs+ DSM 7.2.0 I practice first on a VM machine, then did it on an actual bare bones metal machine. If you are migrating VMs, make sure the new disk sizes are at least 21 GB, otherwise they'll fail to install DSM. I found out the hard way Scanned with Synology Assistant, it showed up as per screencap. Connected and I was presented with the expected page. Then you get these 2 choices, I left it as default to keep as much settings as possible from the old setup. Then you get this page, I used a downloaded DSM_DS3622xs+_64570.pat file as it's faster. After it's done wait for the machine to reboot. updating part 1 updating part 2 logged in, and found what I was trying to verify, it seems like it did not automatically install the packages I was using. well this kind of makes sense, it was not enabled. Data wise looks good, it kept all my old files as expected and drive config. Very neat, it automatically offered to Repair and Update Old packages, however as obsolete package will need to be uninstalled manually like the Open-VM-Tools After a short little while all Done! Note: the only configuration that got lost was the LDAP, which I had to undo, then rejoin again to register it to the LDAP, from the security point of view it makes sense, as it's technically a new machine joining the network, even thought it was an upgrade. My certificates, and most other settings remains intact.
  7. Figured out the issue, in the end it was due the Size of the HDD, compared to DSM 5x/ DSM 6.x, in DSM 7.x the minimum HDD size must be 21 GB or larger as per after adjusting the HDD sizes, then it worked just fine.
  8. As per the title everything went great during the red pill setup. 2 virtual hard drives for testing purposes, setup as SATA controller, and LSI Logic Parallel It appears DSM doesn't like something, but it sees the hard drives. Any help will be appreciated. Thanks!
  9. Got this email from the syno guys yesterday. --- email starts --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- From 1 May 2023, will no longer provide access to installation files for certain older versions of DiskStation Manager (DSM), packages, firmware, clients, and Router Manager (SRM) due to changes in licensing agreements. This change may affect owners of older systems and legacy (EOL) systems. This includes: Devices that have not yet been set up. Devices that require re-installation. Devices that have yet to be updated to the latest available software. Note: This does not affect devices that are still in service. The software versions listed below will be removed from our website and from distribution from 1 May 2023. Affected products include NAS/SAN (DSM) 6.2.3 and below Video Station 3.0.2 and below Audio Station 7.0.0 and below Media Server 1.4 and below Surveillance 8.2.8 and below Networking (SRM) Version 1.1 - 1.1.7 and 1.2 - 1.2.5 Recommendations We recommend you upgrade your device(s) to the latest DSM and package versions available. For devices that cannot be upgraded to DSM 6.2, we recommend keeping a copy of your device's installation files and packages in case re-installation is required in the future. --- email ends ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------- For those of us that still likes to play around with DSM 6.2 make sure to download all the files you need before they are removed from syno servers. We all know that DSM version 7 and above are becoming increasingly more restricted. Reading between the lines, to me it sounds like the syno guys are planning to lock down their DSM environment, and go to dedicated hardware as it was speculated before in forums / videos.
  10. Hey guys, Just jumping onto the 7.1 bandwagon here. I noticed the original post is a bit outdated with the URLs for the download. Found the latest version as of this posting to be v0.9.4.0 https://github.com/pocopico/tinycore-redpill/releases/ Thanks to the team for pre-compiling the red pills for DSM 7.1
  11. As many of you know the default max capacity if we are to follow Synolgy spec DS3615xs is 32G and DS3617xs is 48GB. Regardless of that for our own custom builts, if I install 64GB or 128GB into my box... will XPEnology actually make use that extra available RAM, or it will ignore anything beyond the Synology's firmware Max RAM 32/48 GB limits? For example more RAM to host Dockers or other types of VMs / Minecraft Server / App Servers / Video Transcoding, etc... Currently I have 64GB installed, but according to DS3615xs static specs it shows 32GB, in the Synology info page.
  12. From experience, the LUN# or physical HDD# don't necessary matches within Synology to actual physical layout. Most of the time the Disk# (LUN#) is determined by the SATA Controller you are using.
  13. instead of going at this backwards... why not just setup a VMware and run DSM6 that is working already in VM ?
  14. I was doing some googling around, and apparently Driver wise for Linux, from Adaptec 6 series and above, it uses the same architecture, as in HDDs from Series 6, 7 and 8 are all interchangeable, however... that might or might not be the same in regards to drivers.
×
×
  • Create New...