Jump to content
XPEnology Community

Search the Community

Showing results for tags 'tcrp'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Information
    • Readers News & Rumours
    • Information and Feedback
    • The Noob Lounge
  • XPEnology Project
    • F.A.Q - START HERE
    • Loader Releases & Extras
    • DSM Updates Reporting
    • Developer Discussion Room
    • Tutorials and Guides
    • DSM Installation
    • DSM Post-Installation
    • Packages & DSM Features
    • General Questions
    • Hardware Modding
    • Software Modding
    • Miscellaneous
  • International
    • РУССКИЙ
    • FRANÇAIS
    • GERMAN
    • SPANISH
    • ITALIAN
    • KOREAN

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


About Me

Found 14 results

  1. Loader Information and Background RedPill is the core technology that enables DSM 7.x to run on non-Synology hardware. This post is intended to serve as a definitive tutorial/reference for configuring @pocopico's TinyCore RedPill (TCRP) loader. It explains how to install TCRP on baremetal, i.e. with DSM as the only operating system on your NAS hardware. A tutorial to install TCRP using the ESXi hypervisor is located here. There are other hypervisor tutorials in the Tutorials and Guides forum. TCRP uses a two step-process. First, a Linux OS (TinyCore) boots and evaluates the NAS hardware configuration. Therefore, it is best to have the hardware you plan to use (disk controllers and network cards in particular) installed prior to starting the TCRP setup. Then, an individualized loader (RedPill) is created. This loader is used to install and run DSM. After that, you can switch between starting DSM with RedPill, and booting back into TinyCore to adjust and rebuild the loader as needed. Basic Linux command line skills are needed to complete the installation. The tutorial provides examples of the commands that are needed, but exact syntax and capitalization are critical. If unfamiliar, research and review the following minimal list of commands: ls show the files in the current directory cat <file> show the contents of the specified file pwd show the current directory name cd <directory path> change to the specified directory (same rules as Windows, except with forward slashes instead of backslashes). With no argument, it returns to the “home” TCRP directory vi <file> a file editor, for manual editing of configuration files if required Ongoing Development This tutorial is maintained for consistency with the pocopico stable repository. Since TCRP is completely open-sourced, anyone can fork their own repo and contribute to development, and pocopico now maintains a separate development repo. As the best features and ideas are fully vetted and tested, they may be incorporated into the stable repo over time. If you use a repo, script or shell other than the pocopico stable repo, the loader may behave quite differently and the instructions and troubleshooting steps in this tutorial might no longer apply. In an open-source community, you can use any development resource you want, but you add the additional responsibility of understanding, vetting and testing that code on your system. Migration Step 1. Choose a DSM Platform/Architecture Evaluate your intended NAS hardware and your the intended use of DSM, and select a platform that best meets your needs. Reference information here: https://xpenology.com/forum/topic/61634-dsm-7x-loaders-and-platforms/ Write down the selected platform (e.g. DS918+), the corresponding architecture (e.g. apollolake) and whether the platform uses SataPortMap/DiskIdxMap or Device Tree for slot mapping. This information will be needed later. Now, make sure the NAS hardware is compatible, and prepare it correctly: x86-64-compatible CPU with two cores or more Each platform have maximum threads support! Any threads in excess will be ignored For certain platforms, Intel CPUs must be 4th generation “Haswell” or newer with FMA3 instruction set The corresponding AMD CPU architecture is “Piledriver” or newer AMD-based systems may require deactivation of the C1E option in the BIOS 2GB of RAM or more 2GB or larger USB flash drive Configure the BIOS to boot from the USB flash drive ONLY SATA disk controllers are preferred, but SCSI/SAS are compatible IMPORTANT: All SATA controllers must be configured to AHCI mode SATA controllers with port multipliers are not compatible ATA controllers are not compatible (disable embedded ATA in BIOS if possible) At least one SATA/SCSI/SAS drive (HDD or SSD), minimum size 21GB IMPORTANT: Enable SATA port hotplug on each disk port, if hotplug is supported by the BIOS/controller IMPORTANT: Disable M.2 SATA ports that are not in use, if supported by the BIOS/controller NVMe drives are not usable except as dedicated cache devices Host Bus Adapters are not currently compatible with Device Tree platforms Install any NVMe drives intended as cache devices On Device Tree platforms, NVMe drives must be installed prior to loader installation in order for them to be recognized Step 2. Download TCRP and Write Image to the USB Flash Drive The latest pocopico stable loader code is always linked here: https://xpenology.com/forum/topic/7848-links-to-loaders/ Download the tinycore-redpill 7.x loader and save it to your personal computer. Then, open it with a zip manager to show the boot images: tinycore-redpill.vX.X.X.img.gz (for BIOS/CSM/Legacy boot from USB flash drive) tinycore-redpill-uefi.vX.X.X.img.gz (for UEFI/EFI boot from USB flash drive) tinycore-redpill.vX.X.X.vmdk.gz (for virtual machine SATABOOT from disk image) Select the boot image that matches the boot capability of the NAS motherboard. If unsure, choose BIOS/CSM/Legacy boot. Save the gzip file to your personal computer, then open it with a zip archive manager and save the uncompressed version. Write the uncompressed image to the USB flash drive using Win32DiskImager or other appropriate tool. The USB flash drive is used to store TinyCore and the RedPill loader that it generates. It is a permanent component of an operational XPEnology system. Do not remove it, even after the DSM installation is complete and the NAS is fully up and running. Step 3. Boot into TinyCore and Complete Pre-Configuration Updates Start your NAS with the USB flash drive installed and TinyCore will boot. Then, launch a command-line session with either of these methods: Click the Terminal icon at the bottom right of the TinyCore desktop to launch a console window Use a ssh client (e.g. PuTTY) on your computer to connect a network-based console Consult your DHCP server/router for the IP address assignment (TinyCore's host name is "box") Login credentials: tc/P@ssw0rd When the Linux command line prompt ($) is displayed, update the TCRP script ./rploader.sh update Checking Internet Access -> OK Checking if a newer version exists -> There is a newer version on the repo should we use that ? [yY/nN] Y OK, updating, please re-run after updating Updating tinycore loader with latest updates Backing up files to /mnt/sda3//mydata.tgz Then, update the TCRP support files ./rploader.sh fullupgrade <downloads snipped> Current /home/tc size is 114M , try to keep it less than 1GB as it might not fit into your image Should i update the sda with your current files [Yy/Nn] Y Backing up home files to sda : Backing up files to /mnt/sda3//mydata.tgz Finally, choose a DSM release number Each DSM build as provided by Synology has a release number. You can display the combinations of platforms and releases supported by TCRP by just running the script with no arguments ./rploader.sh <command help snipped> Available platform versions: ---------------------------------------------------------------------------------------- apollolake-7.0-41890 apollolake-7.0.1-42218 apollolake-7.1.0-42661 broadwell-7.0.1-42218 broadwell-7.1.0-42661 broadwellnk-7.0.1-42218 broadwellnk-7.1.0-42661 bromolow-7.0.1-42218 bromolow-7.1.0-42661 denverton-7.0.1-42218 denverton-7.1.0-42661 geminilake-7.0.1-42218 geminilake-7.1.0-42661 v1000-7.0.1-42218 v1000-7.1.0-42661 Step 4. Configure System-Specific Parameters Custom system parameters are stored in the user_config.json file. This can be manually edited, or TCRP can help determine appropriate values for the hardware. USB flash drive VID/PID: TCRP can query the USB flash drive for the hardware vid/pid values that DSM uses to identify the loader during bootup ./rploader.sh identifyusb Found: Superdisk Flash SerialNumber: 123456 Vendor ID: 0x1234 Product ID: 0x0001 Should i update the user_config.json with these values ? [Yy/Nn] Y Serial number/MAC: TCRP can automatically generate a serial number for the platform selected in step 1. Additionally, it will generate a random MAC address for the NAS network card. If you prefer to use the actual hardware MAC address instead, append "realmac" to the command. Example 1: random MAC address ./rploader.sh serialgen DS3622xs+ Serial Number for Model : 20C0SQRLR47QM Mac Address for Model DS3622xs+ : 00:11:32:80:B2:36 Should i update the user_config.json with these values ? [Yy/Nn] Y Example 2: real MAC address ./rploader.sh serialgen DS3622xs+ realmac Serial Number for Model : 2150SQRGS7N5T Mac Address for Model DS3622xs+ : 00:11:32:57:3A:9B Real Mac Address : 00:0C:24:62:3E:3D Notice : realmac option is requested, real mac will be used Should i update the user_config.json with these values ? [Yy/Nn] Y Drive Slot Mapping: TCRP can try to determine how to map the NAS disk controller ports to DSM slots. If the chosen platform uses SataPortMap/DiskIdxMap for port mapping, the command below will do this. If it uses Device Tree for slot mapping, the command may be skipped, as the Device Tree is configured automatically during the loader build. ./rploader.sh satamap Found "02:02.0 SATA AHCI controller" Detected 4 ports/2 drives. Override # of ports or ENTER to accept: <4> Recommended settings: SataPortMap=4 DiskIdxMap=00 Should I update the user_config with these values ? [Yy/Nn] Y If the port count is not what you expect, it may be due to the motherboard design servicing physical ports with multiple controllers, or because of M.2 SATA slot support. If necessary, the port count can be overridden with whatever you like. NOTE: If you see a WARNING message, it is certain that either some of your drives are inaccessible or the DSM install will encounter problems. Evaluate and investigate the issue. The satamap command can be rerun as many times as needed to understand the system. Manual Review: With prior loaders (such as Jun's), the configuration of these parameters was completely manual. There is no single setup that works for all hardware. Even after using the tools above, please review and verify the parameters, understand what they do, and manually edit if needed. Whatever changes rploader.sh makes to the user_config.json file can be reviewed by displaying the file contents cat user_config.json and overridden by editing the file vi user_config.json You can also add a simpler editor, nano tce-load -iw nano nano user_config.json And there is also a graphical editor accessible from the TinyCore desktop Step 5. Optional: Manually Add Driver Extensions While TCRP can automatically add drivers based on the detected NAS hardware, it isn’t foolproof. You might want to build a loader for a device you don’t actually have yet. And there are features that are "opt-in" only. So, a process exists to manually add drivers and other functionality. Extensions are stored in repositories hosted on the web. All the extensions in the main repository are viewable here: https://github.com/pocopico/rp-ext To list all the extensions recommended by TCRP's hardware detection algorithm, use ./rploader.sh listmods <architecture>-<version>-<DSMreleasenumber> ./rploader.sh listmods apollolake-7.1.0-42661 To add a specific extension, choose from the list and reference the architecture from Step 1. ./rploader.sh ext <architecture>-<version>-<DSMreleasenumber> <extensionurl> ./rploader.sh ext apollolake-7.1.0-42661 add https://raw.githubusercontent.com/pocopico/rp-ext/master/redpill-acpid/rpext-index.json ./rploader.sh ext denverton-7.1.0-42661 add https://raw.githubusercontent.com/pocopico/rp-ext/master/v9fs/rpext-index.json The examples illustrate adding ACPI and VIRTIO support. These are often chosen enhancements to a basic installation. Step 6. Build the Loader When all preparation steps are complete, build the loader using the command structure ./rploader.sh build <architecture>-<version>-<DSMreleasenumber> Example #1: DS3622xs+, auto detect hardware ./rploader.sh build broadwellnk-7.1.0-42661 Example #2: DS918+, use preselected drivers ./rploader.sh build apollolake-7.1.0-42661 manual TCRP will download resources from the Internet to complete the complex process of the loader build. When finished, it will write it to the USB flash drive and add new items to the GRUB boot menu. Review the output for any errors and make corrections if necessary. Step 7. Optional Backup Tasks Save the TinyCore configuration state as the default, so that the next boot of TInyCore starts with all your settings ./rploader.sh backup Back up the generated RedPill loader partition to available space on the USB flash drive ./rploader.sh backuploader Step 8: Restart and Boot DSM Using the Grub USB Option Cleanly shutdown and reboot with the TinyCore command exitcheck.sh reboot First, the GRUB Menu is displayed. If necessary, use the arrow keys to ensure that USB is selected and press ENTER. The loader will show some initialization information and silently boot DSM. Nothing else will be displayed unless a serial console is attached (see the Troubleshooting section below). Wait a few minutes, then launch either https://find.synology.com or the Synology Assistant desktop utility. If the loader is working properly, a new "SynologyNAS" will be displayed as Not installed (for a new build) or the name of your existing Migratable NAS (if upgrading from a previous version). Use your browser to connect to the NAS. If "Something went wrong" is displayed, jump to the Basic Troubleshooting section below. Otherwise, browse to the Synology Download Center and download the DSM install PAT file that matches the platform and release number specified in the loader build. Do not use the PAT file stored in TinyCore. It has modifications that are incompatible with DSM installation. However, its name may help identify the correct PAT file to download below. There can be several files that appear to be candidates. PAT files marked VirtualDSM will not work. Also there can be patch PAT files with the same numbering. These will not work and will usually be smaller than 50MB. The correct PAT file is 300MB or larger. Once the correct DSM PAT file is saved to your personal computer, upload it to the NAS. Follow the prompts to complete the installation. FOR UPGRADES ONLY: If Synology Assistant shows Not installed, or if prompted to erase the disks during the upgrade, STOP! Some or all of your array disks are not visible to DSM. This must be resolved via troubleshooting and reconfiguration before installing DSM 7.x. IMPORTANT: During the install, always select DSM manual updates. If a new install completes normally, but then fails after the reboot, it may be that DSM has attempted to auto-update itself with incompatible code. Basic Troubleshooting Where to Post for Help It’s easy for requests for installation help to get lost in various unrelated forum threads. Post requests for help as a new topic in the DSM Installation Forum. At a minimum, state the hardware configuration, selected platform, DSM version, user_config.json information (delete or redact the serial number and configured MAC address) and any information from debugging analysis that you have done. DON’T post general requests for help on this thread. Please DON’T post general requests for help on TCRP or RedPill development threads unless providing feedback on a dev issue.
  2. Hi all, A while ago I've started experimenting with a solution that would not require docker and/or a system running linux, but just a simple image that you can boot on your physical/virtual system and create the loader from there. I started with the plain disk image of 200MB size and tried to fit all in this image. As always first partition of the image is the synoboot1, second synoboot2 and third one (synoboot3) is tinycore. Tinycore is a simple linux distribution that can boot to a GUI so you can start creating the loader. Most network modules are included so you can verify also the extensions required on your system. A script will take care most of the actions that you would manually perform and just copy the loader contents to the 1st and 2nd partition. The loader is created from a pre-compiled redpill extension (should work) or you can compile it yourself (still testing). You can bring over and use the rp-helper configuration files so you dont have to do that again. To connect using ssh you will need first to reset the tc user password by typing # passwd tc The image can be found here: https://github.com/pocopico/tinycore-redpill Before starting the loader creation just run # ./rploader.sh update now and answer y I would appreciate any findings to improve the image.
  3. Introduction This tutorial is a supplement to the main TCRP installation tutorial located here: https://xpenology.com/forum/topic/62221-tutorial-installmigrate-to-dsm-7x-with-tinycore-redpill-tcrp-loader/ You should be familiar with all the concepts and procedures in that tutorial, and general knowledge of VMware ESXi installation and virtual machine management. The focus here is on differences between installing on baremetal (with DSM as the only OS on the NAS), and as a virtual machine using VMware ESXi as the hypervisor. However, much of the conceptual information applies to other hypervisors. Some reasons to install DSM using a hypervisor: virtualize unsupported network card virtualize NVMe or other storage and present to DSM as SATA run other VMs in parallel on the same hardware (as an alternative to Synology VMM) share storage or network cards with other non-XPEnology VMs testing and rollback of updates About VMware ESXi ESXi (currently branded as the "VMware vSphere Hypervisor") is a stand-alone hypervisor that is part of the VMware enterprise computing platform. ESXi's strength includes robust testing and support, good compatibility with modern hardware platforms, and very flexible control over the hypervisor configuration. The core hypervisor is free to use, all that is needed is to sign up to receive a lifetime free license key. Key limitations of the free license are 8 vCPU's (8 threads, same as DS918+) and no serial port virtualization. To use the serial console, a physical connection is needed from the motherboard to your personal computer, or if the motherboard has IPMI features, intercepting the physical serial data with the IPMI remote access tools works as well. There is also a trial ESXi license that offers 256 vCPUs and serial port virtualization. ESXi and DSM Platform/Architecture All currently supported DSM platforms can run as virtual machines. As of this writing, the Device Tree platforms (DS920+ and DS1621+) are not supported by the TCRP device tree patcher when ESXi virtual SATA controllers are used. The problem is understood but currently the only way to make these platforms work is to manually patch the DTS. Transcoding platforms are supported with a compatible CPU, but actual transcoding requires a passthrough configuration of the VGA display adapter, which is somewhat complicated to set up, and beyond the scope of a basic tutorial. As DSM is run as a workload inside ESXi, there is an overhead tax, so the minimum requirements are somewhat higher: x86-64 CPU with two cores or more Hardware virtualization features enabled in the BIOS (Intel VT-x or AMD RVI) 4GB of RAM or more Dedicated 138GB or larger boot and storage device for ESXi system files, run-time files and datastore containing VM configuration files and virtual disks Block storage/controllers on ESXi's compatibility list OR compatible with DSM for passthrough Storage for use with DSM (either as backing storage for virtual disks, or passthrough devices) Creating a DSM Virtual Machine, Part 1 When we create a virtual machine we are defining its hardware characteristics. This machine must be compatible with DSM. For the purposes of the tutorial, we'll create a simple DSM VM with a 21GB virtual SATA drive. First the hardware profile must be selected. The recommended options are illustrated below. Other 3.x Linux (64-bit) is best even when installing a DSM platform with 4.x kernel. The selection here doesn't actually have anything to do with the OS being installed - it's just defining the behavior of the emulated hardware. Here's the initial complement of hardware created with Other 3.x Linux (64-bit): The pre-configured Network Adapter is VMware 10Gbe virtual vmxnet3 and is directly supported by TCRP. However, some changes need to be made to the virtual machine: Change the CPU vCore count to 2 or more Change the memory amount to 2048 or more Change the virtual hard disk size to 21GB or larger (see minimum spec here) If desired, open the drop-down menu and change the virtual disk type to Thin if the VM is only for testing Delete the USB controller Delete the CD/DVD Drive Add a second SATA controller - this will initially be called "New SATA Controller" Save the virtual machine. This creates a virtual machine folder on the datastore, and provisions the VM configuration file and virtual disk in that folder. It is not ready for use yet; some additional preparatory steps need to be completed. Preparing the TCRP Image ESXi VMs cannot boot virtualized USB flash drive images. A passthrough physical USB can be used, but is not recommended. Instead, a special version of the loader is used as a bootable virtual SATA drive. When the TCRP loader boots in this manner, it is called SATABOOT. Download the tinycore-redpill 7.x loader and save it to your personal computer. Then, open it with a zip manager to show the boot images: tinycore-redpill.vX.X.X.img.gz (for BIOS/CSM/Legacy boot from USB flash drive) tinycore-redpill-uefi.vX.X.X.img.gz (for UEFI/EFI boot from USB flash drive) tinycore-redpill.vX.X.X.vmdk.gz (for virtual machine SATABOOT from disk image) Save the vmdk gzip file to your personal computer. Then, upload it to the new virtual machine folder contained in the datastore: For the next step, ESXi console access is required. From the web GUI, enable both SSH and the console shell. SSH into the ESXi host and navigate to the new VM's folder: [root@esxi:] cd /vmfs/volumes [root@esxi:] cd <datastore> [root@esxi:] cd MyNewNAS [root@esxi:] ls -la total 65664 drwxr-xr-x 1 root root 73728 May 28 09:02 . drwxr-xr-t 1 root root 81920 May 28 08:58 .. -rw------- 1 root root 22548578304 May 28 08:58 MyNewNAS-flat.vmdk -rw------- 1 root root 474 May 28 08:58 MyNewNAS.vmdk -rw-r--r-- 1 root root 0 May 28 08:58 MyNewNAS.vmsd -rwxr-xr-x 1 root root 1941 May 28 08:58 MyNewNAS.vmx -rw-r--r-- 1 root root 65260813 May 28 09:02 tinycore-redpill.v0.4.6.vmdk.gz The TCRP SATABOOT image is provided compressed and in VMware Workstation format. These commands prepare it for use with ESXi: [root@esxi:] gunzip tinycore-redpill.v0.4.6.vmdk.gz [root@esxi:] vmkfstools -i tinycore-redpill.v0.4.6.vmdk MyNewNAS-TCRP.vmdk Destination disk format: VMFS zeroedthick Cloning disk 'tinycore-redpill.v0.4.6.vmdk'... Clone: 100% done. Creating a DSM Virtual Machine, Part 2 From the GUI console, select the DSM virtual machine and Edit. This is what things look like now: Now the SATABOOT loader must be added to the virtual machine. Select Add hard disk (existing hard disk) and choose the TCRP vmdk created in the previous step It will be displayed as "New hard disk" - expand the dropdown Change the controller to SATA Controller 0 The disk address should be SATA0:0 Save the changes to the VM The default for the Other 3.x Linux (64-bit) hardware profile is to create a SCSI virtual controller and attach all new virtual disks to it. DSM works better with the virtual SATA controller, so we need to move the DSM virtual data disk to it. Edit the virtual machine Expand the dropdown for Hard disk 1 (note that it is 21GB or whatever size we selected) Change the controller to SATA Controller 1 The disk address should be SATA1:0 Save the changes to the VM VMWare has an odd behavior in that it renumbers all the hard disks based on the last edit. This is cosmetic, and only affects the VM configuration screen. It does not change the disk addressing order in any way. The VM edit window now looks like this: Now that no disks are attached to the SCSI controller, we can (and should) delete it. The final configuration of controllers and disks is: SATA Controller 0: SATABOOT (SATA0:0) SATA Controller 1: DSM Data DIsk (SATA1:0) Any additional virtual DSM data disks should be added to SATA1 (i.e. SATA1:1, SATA1:2, etc). SATA0 should be reserved only for SATABOOT. The VM is now ready for the TinyCore boot (main tutorial, Step 3). System-Specific Parameters and SATABOOT ESXi requires minor adjustments to the basic tutorial configuration steps: The USB flash drive VID/PID configuration step (./rploader.sh identifyusb) is invalid and can be skipped when using SATABOOT. When using a virtual network adapter (such as VMXNET 3), its MAC address and the loader's MAC address setting must match. When a virtual machine is booted for the first time, a random address is assigned to each virtual adapter. Unless your primary network interface is a passthrough device, the serialgen configuration step requires the realmac argument to match the virtual NIC's random address to TCRP. Example: ./rploader.sh serialgen DS3622xs+ realmac The Drive Slot Mapping configuration step is the same, but the outcome is different when SATABOOT is in use. ./rploader.sh satamap will enforce the prohibition on data disks attached to SATA0 and warn if this configuration exists. SataPortMap and DiskIdxMap are configured to remove a blank slot between the SATA0 and SATA1 controllers. SCSI/SAS controllers or HBAs (either passthrough or virtual) ignore satamap functionality. When SATABOOT is also in use, there is an unavoidable blank slot between the last SATA controller and the first SCSI/SAS controller or HBA. Boot DSM with GRUB When the GRUB Menu is displayed: if necessary, use the arrow keys to ensure that SATA is selected and press ENTER. Advanced Configuration Examples: Passthrough and Raw Device Mapping (RDM)
  4. I am trying to get HW transcoding working on my Xpenology NAS. I am running TCRP with DSM 7.1 (7.1-42661 Update 4). I am using a real serial/mac address (things like ddns are working fine). I followed this guide when I was trying to make HW Transcoding work: https://drfrankenstein.co.uk/2021/12/06/plex-in-docker-on-a-synology-nas-hardware-transcoding/ Everything seemed to work, the folder /dev/dri/ is present: root@NAS:~$ sudo docker exec -it Plex sh # ls /dev/dri card0 renderD128 But whenever I transcode a movie, it isn't using HW transcoding (see attached file). This is the hardware that I'm using: - Processor: Intel Pentium G4560 Boxed - MoBo: ASRock B250M Pro4 - Power supply: Mini-box picoPSU PicoPSU-160-XT - RAM (8GB): Crucial CT8G4DFD8213 I am hoping that anyone here knows a solution to this problem.
  5. I'm using AMD AM3+ Phenom 2 X4 965 https://www.amd.com/en/products/cpu/965 with motherboard GA-970-D3 https://www.gigabyte.com/Motherboard/GA-970A-D3-rev-30#ov and using 8GB of RAM. As Booting comes up in ARPL AND TCRP both got stuck and no sign of LAN light and activity, so I done some research I encountered that RTL-8111F drivers module are missing and I tried e1000 LAN card but get the Ip address and showing activity light but got stuck and no ping at all waited whole night and unsuccessful... Does this Processor do support ARPL or TCRP Any Help would be appreciated.. Thanks in Advance....
  6. Имеется хрень - tcrp, ds920+, dsm 7.1.0-42661 на железе старого ноута (lenovo g50-30, bay trail-m, celeron n2830, сеть realtek RTL8168/8111, ddr3-1333 2Gb, ssd samsung 850pro 1tb). Изучаю возможности и тестирую под свои задачи, важно наличие usb 3.0 на соответствующей ему скорости.. Сейчас порт 3.0 работает но при копировании с флешки на ssd скорость не превышает 40мб/сек (та же флешка воткнутая в пк на винде дает при копировании 130мб/сек), реально получить те же 130мб/сек на хрени ? На этом же железе загрузился с Win PEшки, получил 80мб/сек (другая флешка, на бб так же), в общем железо исправно.
  7. Hardware: C2Q Q6600 Intel MB 2x 2TB HDDs 2x2 GB DDR2 Setup was working fine for a week, then I upgraded RAM to 4x2 GB DDR2. Then system refused to boot. Tried 3 different pen drives to reinstall, but it stucks while booting TCRP at "Loading Kernel" then black screen and no Tiny Core GUI. System also not available on network. Tried same pen drive on my laptop and it works fine. Also removed both HDDs still same status. Any help would be highly appreciated.
  8. I am currently switching from DSM 6.2 to 7.1 and my setup is as follows: How to expand drive number in DSM7? Now my problem is, that it is not possible to do the same trick in DSM 7 to expand beyond x drives like it was in 6.2. (My setup would allow 22 in total from which 14 are used for now) I already chattet with @Peter Suhabout this topic but unfortunetly we could not solve my problem. Things I tried: Building the loader as described by @Peter Suh (Guide) installed the latest tcrp image with rufus on usb booted in tc & connected via ssh ./rploader.sh update ./my.sh ./rploader.sh clean ./my.sh DS3622xs+J poco noclean Building the loader as described by @flyride (Guide) installed the latest tcrp image with rufus on usb booted in tc & connected via ssh ./rploader.sh update ./rploader.sh fullupgrade ./rploader.sh identifyusb ./rploader.sh serialgen DS3622xs+ #I tried building the loader with and without this command ./rploader.sh satamap vi user_config.json # adding those lines: "maxdisks" : "22", "esataportcfg" : "0x00", "usbportcfg" : "0xc000000", "internalportcfg" : "0x3fffff", ./rploader.sh build broadwellnk-7.1.0-42661 ./rploader.sh backup ./rploader.sh backuploader exitcheck.sh reboot Seutp & outcome VM or BareMetal : BareMetal Hardware (Motherboard/CPU) : MSI MPG Z390 / Intel 9900T Storage-Controller: 2x LSI SAS 9211-8i (HBA in IT mode) Hot Plug Applied : Yes Network Interface 1 : Intel i217v (e1000e) Network Interface 2 : Intel X540-T2 (10 Gbit) Network Interface 3 : Intel X540-T2 (10 Gbit) Loader : TCRP 0.4.6 version of rploader.sh : 0.8.3 Platform : 3622xs+ Platform Version : 7.1 Platform Revision : 42661-U1 GRUB Boot selection : USB Unfortunetly both methods resulted in the same outcome which is the following: My NAS looks physically like this. I numbered the drive slots from 1 - 22 to have an easier time explaining my issue. So slotnumber 1-8 are connected to HBA 2 9,10 and 17-22 are connected to HBA 1 11-16 are connected to the mainboard SATA ports I have 3 PCIx16 Slots on my mainboard First one is used for Intel X540 T2 10 GBit NIC Second one is used for HBA1 Third one is used for HBA2 Currently the slots below are occupied: 1-4 = 4 HDDs 6-9 = 4 HDDs 11-13 = 3 SSDs 17-19 = 3 SSDs = 14 drives in total. Now in this config either slot 6 or 7 isnt recognised in DSM, every other drive works. When I put the drive from slot 6 into slot 5 it is reconised, BUT unfortunately one drive from slots 1-4 is missing then. I tried this with multiple combinations. The outcome was always that 1 drive was missing (not a specific HDD/SSD or SLOT). As soon as I add more than 13 drives it keeps getting weird. Since my setup worked in DSM6 my guess is that either I am missing something or TCRP is missing something. Troubleshooting: TinyCore sd list lrwxrwxrwx 1 root root 0 Jun 26 09:08 loop0 -> ../devices/virtual/block/loop0 lrwxrwxrwx 1 root root 0 Jun 26 09:08 loop1 -> ../devices/virtual/block/loop1 lrwxrwxrwx 1 root root 0 Jun 26 09:11 loop10 -> ../devices/virtual/block/loop10 lrwxrwxrwx 1 root root 0 Jun 26 09:11 loop11 -> ../devices/virtual/block/loop11 lrwxrwxrwx 1 root root 0 Jun 26 09:11 loop12 -> ../devices/virtual/block/loop12 lrwxrwxrwx 1 root root 0 Jun 26 09:11 loop13 -> ../devices/virtual/block/loop13 lrwxrwxrwx 1 root root 0 Jun 26 09:11 loop14 -> ../devices/virtual/block/loop14 lrwxrwxrwx 1 root root 0 Jun 26 09:11 loop15 -> ../devices/virtual/block/loop15 lrwxrwxrwx 1 root root 0 Jun 26 09:11 loop16 -> ../devices/virtual/block/loop16 lrwxrwxrwx 1 root root 0 Jun 26 09:11 loop17 -> ../devices/virtual/block/loop17 lrwxrwxrwx 1 root root 0 Jun 26 09:11 loop18 -> ../devices/virtual/block/loop18 lrwxrwxrwx 1 root root 0 Jun 26 09:11 loop19 -> ../devices/virtual/block/loop19 lrwxrwxrwx 1 root root 0 Jun 26 09:08 loop2 -> ../devices/virtual/block/loop2 lrwxrwxrwx 1 root root 0 Jun 26 09:11 loop20 -> ../devices/virtual/block/loop20 lrwxrwxrwx 1 root root 0 Jun 26 09:11 loop21 -> ../devices/virtual/block/loop21 lrwxrwxrwx 1 root root 0 Jun 26 09:11 loop22 -> ../devices/virtual/block/loop22 lrwxrwxrwx 1 root root 0 Jun 26 09:11 loop23 -> ../devices/virtual/block/loop23 lrwxrwxrwx 1 root root 0 Jun 26 09:11 loop24 -> ../devices/virtual/block/loop24 lrwxrwxrwx 1 root root 0 Jun 26 09:11 loop25 -> ../devices/virtual/block/loop25 lrwxrwxrwx 1 root root 0 Jun 26 09:11 loop26 -> ../devices/virtual/block/loop26 lrwxrwxrwx 1 root root 0 Jun 26 09:11 loop27 -> ../devices/virtual/block/loop27 lrwxrwxrwx 1 root root 0 Jun 26 09:11 loop28 -> ../devices/virtual/block/loop28 lrwxrwxrwx 1 root root 0 Jun 26 09:11 loop29 -> ../devices/virtual/block/loop29 lrwxrwxrwx 1 root root 0 Jun 26 09:08 loop3 -> ../devices/virtual/block/loop3 lrwxrwxrwx 1 root root 0 Jun 26 09:11 loop30 -> ../devices/virtual/block/loop30 lrwxrwxrwx 1 root root 0 Jun 26 09:11 loop31 -> ../devices/virtual/block/loop31 lrwxrwxrwx 1 root root 0 Jun 26 09:11 loop32 -> ../devices/virtual/block/loop32 lrwxrwxrwx 1 root root 0 Jun 26 09:11 loop33 -> ../devices/virtual/block/loop33 lrwxrwxrwx 1 root root 0 Jun 26 09:11 loop34 -> ../devices/virtual/block/loop34 lrwxrwxrwx 1 root root 0 Jun 26 09:11 loop35 -> ../devices/virtual/block/loop35 lrwxrwxrwx 1 root root 0 Jun 26 09:11 loop36 -> ../devices/virtual/block/loop36 lrwxrwxrwx 1 root root 0 Jun 26 09:11 loop37 -> ../devices/virtual/block/loop37 lrwxrwxrwx 1 root root 0 Jun 26 09:11 loop38 -> ../devices/virtual/block/loop38 lrwxrwxrwx 1 root root 0 Jun 26 09:11 loop39 -> ../devices/virtual/block/loop39 lrwxrwxrwx 1 root root 0 Jun 26 09:08 loop4 -> ../devices/virtual/block/loop4 lrwxrwxrwx 1 root root 0 Jun 26 09:11 loop40 -> ../devices/virtual/block/loop40 lrwxrwxrwx 1 root root 0 Jun 26 09:11 loop41 -> ../devices/virtual/block/loop41 lrwxrwxrwx 1 root root 0 Jun 26 09:11 loop42 -> ../devices/virtual/block/loop42 lrwxrwxrwx 1 root root 0 Jun 26 09:11 loop43 -> ../devices/virtual/block/loop43 lrwxrwxrwx 1 root root 0 Jun 26 09:11 loop44 -> ../devices/virtual/block/loop44 lrwxrwxrwx 1 root root 0 Jun 26 09:11 loop45 -> ../devices/virtual/block/loop45 lrwxrwxrwx 1 root root 0 Jun 26 09:11 loop46 -> ../devices/virtual/block/loop46 lrwxrwxrwx 1 root root 0 Jun 26 09:11 loop47 -> ../devices/virtual/block/loop47 lrwxrwxrwx 1 root root 0 Jun 26 09:11 loop48 -> ../devices/virtual/block/loop48 lrwxrwxrwx 1 root root 0 Jun 26 09:11 loop49 -> ../devices/virtual/block/loop49 lrwxrwxrwx 1 root root 0 Jun 26 09:08 loop5 -> ../devices/virtual/block/loop5 lrwxrwxrwx 1 root root 0 Jun 26 09:11 loop50 -> ../devices/virtual/block/loop50 lrwxrwxrwx 1 root root 0 Jun 26 09:11 loop51 -> ../devices/virtual/block/loop51 lrwxrwxrwx 1 root root 0 Jun 26 09:08 loop6 -> ../devices/virtual/block/loop6 lrwxrwxrwx 1 root root 0 Jun 26 09:08 loop7 -> ../devices/virtual/block/loop7 lrwxrwxrwx 1 root root 0 Jun 26 09:11 loop8 -> ../devices/virtual/block/loop8 lrwxrwxrwx 1 root root 0 Jun 26 09:11 loop9 -> ../devices/virtual/block/loop9 lrwxrwxrwx 1 root root 0 Jun 26 09:08 ram0 -> ../devices/virtual/block/ram0 lrwxrwxrwx 1 root root 0 Jun 26 09:08 ram1 -> ../devices/virtual/block/ram1 lrwxrwxrwx 1 root root 0 Jun 26 09:08 ram2 -> ../devices/virtual/block/ram2 lrwxrwxrwx 1 root root 0 Jun 26 09:08 ram3 -> ../devices/virtual/block/ram3 lrwxrwxrwx 1 root root 0 Jun 26 09:08 ram4 -> ../devices/virtual/block/ram4 lrwxrwxrwx 1 root root 0 Jun 26 09:08 ram5 -> ../devices/virtual/block/ram5 lrwxrwxrwx 1 root root 0 Jun 26 09:08 ram6 -> ../devices/virtual/block/ram6 lrwxrwxrwx 1 root root 0 Jun 26 09:08 ram7 -> ../devices/virtual/block/ram7 lrwxrwxrwx 1 root root 0 Jun 26 09:08 sda -> ../devices/pci0000:00/0000:00:17.0/ata1/host0/target0:0:0/0:0:0:0/block/sda lrwxrwxrwx 1 root root 0 Jun 26 09:08 sdb -> ../devices/pci0000:00/0000:00:17.0/ata2/host1/target1:0:0/1:0:0:0/block/sdb lrwxrwxrwx 1 root root 0 Jun 26 09:08 sdc -> ../devices/pci0000:00/0000:00:17.0/ata5/host4/target4:0:0/4:0:0:0/block/sdc lrwxrwxrwx 1 root root 0 Jun 26 09:08 sdd -> ../devices/pci0000:00/0000:00:14.0/usb1/1-5/1-5:1.0/host6/target6:0:0/6:0:0:0/block/sdd lrwxrwxrwx 1 root root 0 Jun 26 09:08 zram0 -> ../devices/virtual/block/zram0 Synology sd list dummy@NAS:~$ ll /sys/block total 0 drwxr-xr-x 2 root root 0 Jun 26 11:00 . dr-xr-xr-x 12 root root 0 Jun 26 11:00 .. lrwxrwxrwx 1 root root 0 Jun 26 11:05 dm-0 -> ../devices/virtual/block/dm-0 lrwxrwxrwx 1 root root 0 Jun 26 11:05 dm-1 -> ../devices/virtual/block/dm-1 lrwxrwxrwx 1 root root 0 Jun 26 11:05 dm-2 -> ../devices/virtual/block/dm-2 lrwxrwxrwx 1 root root 0 Jun 26 11:05 dm-3 -> ../devices/virtual/block/dm-3 lrwxrwxrwx 1 root root 0 Jun 26 11:00 dm-4 -> ../devices/virtual/block/dm-4 lrwxrwxrwx 1 root root 0 Jun 26 11:00 dm-5 -> ../devices/virtual/block/dm-5 lrwxrwxrwx 1 root root 0 Jun 26 11:00 dm-6 -> ../devices/virtual/block/dm-6 lrwxrwxrwx 1 root root 0 Jun 26 11:05 loop0 -> ../devices/virtual/block/loop0 lrwxrwxrwx 1 root root 0 Jun 26 11:05 loop1 -> ../devices/virtual/block/loop1 lrwxrwxrwx 1 root root 0 Jun 26 11:05 loop2 -> ../devices/virtual/block/loop2 lrwxrwxrwx 1 root root 0 Jun 26 11:05 loop3 -> ../devices/virtual/block/loop3 lrwxrwxrwx 1 root root 0 Jun 26 11:05 loop4 -> ../devices/virtual/block/loop4 lrwxrwxrwx 1 root root 0 Jun 26 11:05 loop5 -> ../devices/virtual/block/loop5 lrwxrwxrwx 1 root root 0 Jun 26 11:05 loop6 -> ../devices/virtual/block/loop6 lrwxrwxrwx 1 root root 0 Jun 26 11:05 loop7 -> ../devices/virtual/block/loop7 lrwxrwxrwx 1 root root 0 Jun 26 11:00 md0 -> ../devices/virtual/block/md0 lrwxrwxrwx 1 root root 0 Jun 26 11:00 md1 -> ../devices/virtual/block/md1 lrwxrwxrwx 1 root root 0 Jun 26 11:00 md2 -> ../devices/virtual/block/md2 lrwxrwxrwx 1 root root 0 Jun 26 11:00 md3 -> ../devices/virtual/block/md3 lrwxrwxrwx 1 root root 0 Jun 26 11:00 md5 -> ../devices/virtual/block/md5 lrwxrwxrwx 1 root root 0 Jun 26 11:05 ram0 -> ../devices/virtual/block/ram0 lrwxrwxrwx 1 root root 0 Jun 26 11:05 ram1 -> ../devices/virtual/block/ram1 lrwxrwxrwx 1 root root 0 Jun 26 11:05 ram10 -> ../devices/virtual/block/ram10 lrwxrwxrwx 1 root root 0 Jun 26 11:05 ram11 -> ../devices/virtual/block/ram11 lrwxrwxrwx 1 root root 0 Jun 26 11:05 ram12 -> ../devices/virtual/block/ram12 lrwxrwxrwx 1 root root 0 Jun 26 11:05 ram13 -> ../devices/virtual/block/ram13 lrwxrwxrwx 1 root root 0 Jun 26 11:05 ram14 -> ../devices/virtual/block/ram14 lrwxrwxrwx 1 root root 0 Jun 26 11:05 ram15 -> ../devices/virtual/block/ram15 lrwxrwxrwx 1 root root 0 Jun 26 11:05 ram2 -> ../devices/virtual/block/ram2 lrwxrwxrwx 1 root root 0 Jun 26 11:05 ram3 -> ../devices/virtual/block/ram3 lrwxrwxrwx 1 root root 0 Jun 26 11:05 ram4 -> ../devices/virtual/block/ram4 lrwxrwxrwx 1 root root 0 Jun 26 11:05 ram5 -> ../devices/virtual/block/ram5 lrwxrwxrwx 1 root root 0 Jun 26 11:05 ram6 -> ../devices/virtual/block/ram6 lrwxrwxrwx 1 root root 0 Jun 26 11:05 ram7 -> ../devices/virtual/block/ram7 lrwxrwxrwx 1 root root 0 Jun 26 11:05 ram8 -> ../devices/virtual/block/ram8 lrwxrwxrwx 1 root root 0 Jun 26 11:05 ram9 -> ../devices/virtual/block/ram9 lrwxrwxrwx 1 root root 0 Jun 26 11:00 sda -> ../devices/pci0000:00/0000:00:17.0/ata1/host0/target0:0:0/0:0:0:0/block/sda lrwxrwxrwx 1 root root 0 Jun 26 11:00 sdb -> ../devices/pci0000:00/0000:00:17.0/ata2/host1/target1:0:0/1:0:0:0/block/sdb lrwxrwxrwx 1 root root 0 Jun 26 11:00 sde -> ../devices/pci0000:00/0000:00:17.0/ata5/host4/target4:0:0/4:0:0:0/block/sde lrwxrwxrwx 1 root root 0 Jun 26 11:00 sdg -> ../devices/pci0000:00/0000:00:01.1/0000:02:00.0/host6/port-6:0/end_device-6:0/target6:0:0/6:0:0:0/block/sdg lrwxrwxrwx 1 root root 0 Jun 26 11:00 sdh -> ../devices/pci0000:00/0000:00:01.1/0000:02:00.0/host6/port-6:1/end_device-6:1/target6:0:1/6:0:1:0/block/sdh lrwxrwxrwx 1 root root 0 Jun 26 11:00 sdi -> ../devices/pci0000:00/0000:00:01.1/0000:02:00.0/host6/port-6:2/end_device-6:2/target6:0:2/6:0:2:0/block/sdi lrwxrwxrwx 1 root root 0 Jun 26 11:00 sdj -> ../devices/pci0000:00/0000:00:01.1/0000:02:00.0/host6/port-6:3/end_device-6:3/target6:0:3/6:0:3:0/block/sdj lrwxrwxrwx 1 root root 0 Jun 26 11:00 sdk -> ../devices/pci0000:00/0000:00:1b.4/0000:04:00.0/host8/port-8:0/end_device-8:0/target8:0:0/8:0:0:0/block/sdk lrwxrwxrwx 1 root root 0 Jun 26 11:00 sdl -> ../devices/pci0000:00/0000:00:1b.4/0000:04:00.0/host8/port-8:1/end_device-8:1/target8:0:1/8:0:1:0/block/sdl lrwxrwxrwx 1 root root 0 Jun 26 11:00 sdm -> ../devices/pci0000:00/0000:00:1b.4/0000:04:00.0/host8/port-8:2/end_device-8:2/target8:0:2/8:0:2:0/block/sdm lrwxrwxrwx 1 root root 0 Jun 26 11:00 sdn -> ../devices/pci0000:00/0000:00:1b.4/0000:04:00.0/host8/port-8:3/end_device-8:3/target8:0:3/8:0:3:0/block/sdn lrwxrwxrwx 1 root root 0 Jun 26 11:00 sdo -> ../devices/pci0000:00/0000:00:1b.4/0000:04:00.0/host8/port-8:4/end_device-8:4/target8:0:4/8:0:4:0/block/sdo lrwxrwxrwx 1 root root 0 Jun 26 11:00 sdp -> ../devices/pci0000:00/0000:00:1b.4/0000:04:00.0/host8/port-8:5/end_device-8:5/target8:0:5/8:0:5:0/block/sdp lrwxrwxrwx 1 root root 0 Jun 26 11:00 synoboot -> ../devices/pci0000:00/0000:00:14.0/usb1/1-5/1-5:1.0/host7/target7:0:0/7:0:0:0/block/synoboot lrwxrwxrwx 1 root root 0 Jun 26 11:00 zram0 -> ../devices/virtual/block/zram0 lrwxrwxrwx 1 root root 0 Jun 26 11:00 zram1 -> ../devices/virtual/block/zram1 lrwxrwxrwx 1 root root 0 Jun 26 11:00 zram2 -> ../devices/virtual/block/zram2 lrwxrwxrwx 1 root root 0 Jun 26 11:00 zram3 -> ../devices/virtual/block/zram3 lrwxrwxrwx 1 root root 0 Jun 26 11:00 zram4 -> ../devices/virtual/block/zram4 lrwxrwxrwx 1 root root 0 Jun 26 11:00 zram5 -> ../devices/virtual/block/zram5 lrwxrwxrwx 1 root root 0 Jun 26 11:00 zram6 -> ../devices/virtual/block/zram6 lrwxrwxrwx 1 root root 0 Jun 26 11:00 zram7 -> ../devices/virtual/block/zram7 Ubuntu tryout sd list root@ubuntu:~# ll /sys/block total 0 drwxr-xr-x 2 root root 0 Jun 26 09:24 ./ dr-xr-xr-x 13 root root 0 Jun 26 09:24 ../ lrwxrwxrwx 1 root root 0 Jun 26 09:24 loop0 -> ../devices/virtual/block/loop0/ lrwxrwxrwx 1 root root 0 Jun 26 09:24 loop1 -> ../devices/virtual/block/loop1/ lrwxrwxrwx 1 root root 0 Jun 26 09:24 loop2 -> ../devices/virtual/block/loop2/ lrwxrwxrwx 1 root root 0 Jun 26 09:24 loop3 -> ../devices/virtual/block/loop3/ lrwxrwxrwx 1 root root 0 Jun 26 09:24 loop4 -> ../devices/virtual/block/loop4/ lrwxrwxrwx 1 root root 0 Jun 26 09:24 loop5 -> ../devices/virtual/block/loop5/ lrwxrwxrwx 1 root root 0 Jun 26 09:24 loop6 -> ../devices/virtual/block/loop6/ lrwxrwxrwx 1 root root 0 Jun 26 09:24 loop7 -> ../devices/virtual/block/loop7/ lrwxrwxrwx 1 root root 0 Jun 26 09:25 loop8 -> ../devices/virtual/block/loop8/ lrwxrwxrwx 1 root root 0 Jun 26 09:27 loop9 -> ../devices/virtual/block/loop9/ lrwxrwxrwx 1 root root 0 Jun 26 09:24 sda -> ../devices/pci0000:00/0000:00:01.1/0000:02:00.0/host0/port-0:0/end_device-0:0/target0:0:0/0:0:0:0/block/sda/ lrwxrwxrwx 1 root root 0 Jun 26 09:24 sdb -> ../devices/pci0000:00/0000:00:01.1/0000:02:00.0/host0/port-0:1/end_device-0:1/target0:0:1/0:0:1:0/block/sdb/ lrwxrwxrwx 1 root root 0 Jun 26 09:24 sdc -> ../devices/pci0000:00/0000:00:01.1/0000:02:00.0/host0/port-0:2/end_device-0:2/target0:0:2/0:0:2:0/block/sdc/ lrwxrwxrwx 1 root root 0 Jun 26 09:24 sdd -> ../devices/pci0000:00/0000:00:01.1/0000:02:00.0/host0/port-0:3/end_device-0:3/target0:0:3/0:0:3:0/block/sdd/ lrwxrwxrwx 1 root root 0 Jun 26 09:24 sde -> ../devices/pci0000:00/0000:00:1b.4/0000:04:00.0/host7/port-7:0/end_device-7:0/target7:0:0/7:0:0:0/block/sde/ lrwxrwxrwx 1 root root 0 Jun 26 09:24 sdf -> ../devices/pci0000:00/0000:00:1b.4/0000:04:00.0/host7/port-7:1/end_device-7:1/target7:0:1/7:0:1:0/block/sdf/ lrwxrwxrwx 1 root root 0 Jun 26 09:24 sdg -> ../devices/pci0000:00/0000:00:1b.4/0000:04:00.0/host7/port-7:2/end_device-7:2/target7:0:2/7:0:2:0/block/sdg/ lrwxrwxrwx 1 root root 0 Jun 26 09:24 sdh -> ../devices/pci0000:00/0000:00:1b.4/0000:04:00.0/host7/port-7:3/end_device-7:3/target7:0:3/7:0:3:0/block/sdh/ lrwxrwxrwx 1 root root 0 Jun 26 09:24 sdi -> ../devices/pci0000:00/0000:00:1b.4/0000:04:00.0/host7/port-7:4/end_device-7:4/target7:0:4/7:0:4:0/block/sdi/ lrwxrwxrwx 1 root root 0 Jun 26 09:24 sdj -> ../devices/pci0000:00/0000:00:1b.4/0000:04:00.0/host7/port-7:5/end_device-7:5/target7:0:5/7:0:5:0/block/sdj/ lrwxrwxrwx 1 root root 0 Jun 26 09:24 sdk -> ../devices/pci0000:00/0000:00:14.0/usb1/1-5/1-5:1.0/host8/target8:0:0/8:0:0:0/block/sdk/ lrwxrwxrwx 1 root root 0 Jun 26 09:24 sdl -> ../devices/pci0000:00/0000:00:17.0/ata1/host1/target1:0:0/1:0:0:0/block/sdl/ lrwxrwxrwx 1 root root 0 Jun 26 09:24 sdm -> ../devices/pci0000:00/0000:00:17.0/ata2/host2/target2:0:0/2:0:0:0/block/sdm/ lrwxrwxrwx 1 root root 0 Jun 26 09:24 sdn -> ../devices/pci0000:00/0000:00:17.0/ata5/host5/target5:0:0/5:0:0:0/block/sdn/ I would appreciate any hints🙂
  9. hello, i cannot install on my esxi an DS920+ or DS3622xs+ with DSM 7.1 (it's okay with 7.01) after rploader build the VM boot but NAS not detect HDD an idea ? Thanks
  10. @flyride Since the first TinyCore release I have my DS918+ up and running. Recently I came into the possession of a X550-T2 (2 ports) and I would like to use it. My DS918+ it's not a baremetal but a VM. I know how to pass-through 1 of the ports. The question here is how do add the ixbe driver to loader in order to identify the new network card without messing everything up. Any particular commands that I need to run? I prefer not to rebuild the loader because a lot of stuff have change in TCRP since then... for example Jumkey's ACPI used to work on DS918+ not it does not. Any advice is much appreciated...
  11. I must be missing something, but I can't figure out what it is. I'm trying the following on my ESXi 6.7 system which has been running a JUN DSM6 for several years: I created the VM, with the latest VMDK (0.8.0.0). It boots fine, update/fullupgrade work fine, I believe the version is now 0.8.0.3 or something like that. For the build I've run the following commands: ./rploader.sh serialgen DS3622xs+ realmac ./rploader.sh satamap (where I specify 9 disks, to allow 1 vmdk for volume1 and bringing over my 8 RDM devices for volume2, which I will not do until after testing) ./rploader.sh build broadwellnk-7.1.0-42661 The build seems to go fine and does not display any errors, however when I reboot the VM I still only have TinyCore at the GRUB screen. I don't have any entries for RedPill. Anyone have any ideas?
  12. I build DVA3221 under PVE 7. Hope to Turn off the kvm. I used the following command to add ACPI. But it doesn't seem to work. Where did I do something wrong? ./rploader.sh ext denverton-7.1.0-42661 add https://github.com/pocopico/redpill-load/raw/develop/redpill-acpid/rpext-index.json I see someone suggesting that you use https://github.com/jumkey/redpill-load/tree/develop/redpill-acpid/rpext-index.json. Is there any difference between them?
  13. Dear all, today I tried to install from scratch a new DSM_DS918+ 7.1-42661. Just one Harddisk connected to SATA0 and did the steps (I did this already several times with other hardware). But today I have a new issue. The first *.pat file installation seems to be successful, but after reboot I always get the "Welcome Back" Message, and I have to re-install it several times... now Idea what is wrong
  14. This is for the user who must use proxy to access internet/github/google setPROXY.sh 1. Create the setPROXY.sh script touch setPROXY.sh 2.Prepare script content You need to change the value of myproxy with your proxy setting. It accect 2 way: http and socks5. like this This is a template of setPROXY.sh #!/bin/bash myproxy="http://192.168.1.1:8080" echo -e "curl and git's proxy will set to \033[1m$myproxy\033[0m" #set proxy for current user's curl echo "proxy=\"$myproxy\"" > $HOME/.curlrc #set proxy for root's curl echo "proxy=\"$myproxy\"" > /root/.curlrc set proxy for git git config --global http.proxy \"$myproxy\" git config --global https.proxy \"$myproxy\" this template script expected output will be: "curl and git's proxy will set to http://192.168.1.1:8080" 4.Using vi to change setPROXY.sh vi setPROXY.sh This is another correct sample of setPROXY.sh #!/bin/bash myproxy="socks5://192.168.1.1:8080" echo "proxy=\"$myproxy\"" > $HOME/.curlrc echo "proxy=\"$myproxy\"" > /root/.curlrc git config --global http.proxy \"$myproxy\" this script expected output will be nothing After finishing editing, press "ESC" key, then enter ":wq" to save the file and exit 5. Run setPROXY.sh bash setPROXY.sh If there is no output from the shell, the proxy settings are in effect Sorry about my English level, I hope it can help someone ------------------------------------------------------------ setPROXY.sh
×
×
  • Create New...