yonn

Yes. No space on sda3 ?????? why ?😕

tc@box:~$ df -h|grep sd /dev/sda3 899M 899M 0 100% /mnt/sda3 /dev/sda1 48M 39M 9.5M 81% /mnt/sda1 /dev/sda2 75M 11M 65M 14% /mnt/sda2

At this time: boot from 0.9.3.0.vmdk. ./rploader.sh update ./rploader fullupgrade etc,etc ./rploader.sh build ds3622xsp-7.1.1-42692 withfriend etc,etc I have 4 options in GRUB: USB, SATA, TC Build Image, Tiny Friend I am not very clear about what the fourth option Tinycore Friend is for or how I should use it. If I select it, I get an error: "Loading Linux error: premature end of file /bzImage-friend. loadind initframs.., error: you need to load the kernel first. Booting Tiny Core Friend Press any key to continue...."

I tried directy with 0.9.3.0 vmdk. The same result: in GRUB only Tinycore Image Build boot. I am a novice in Linux, how to send the output to a file? Maybe some like that? ./rploader.sh build ds3622xsp-7.1.1-42692 withfriend >>output.txt And then paste the text file. I won't be able to test it for a few hours

For informational purposes in case it happens to someone else I am playing with VM on ESXI 7.0u3. Using TCRP 0.9.2.9 and updating it to 0.9.3. I follow the process correctly (serialgen, satamap, build, etc, etc). Everything seems to end correctly. But when I boot the VM in GRUB only the TCRP boot option appears. If I repeat the process without updating from 0.9.2.9 to 0.9.3.0 everything works correctly (in GRUB the correct boot options appear) I will try directly with the new version to download TCRP 0.9.3.0

In order to configure TCRP I want to connect via SSH but I don't know which admin/password I should use. I also use an ES keyboard. How can I change the keyboard layout from the command line? Apologies if this has been asked before but I'm pretty new to Linux

Solved. Rookie mistake for taking a long time without installing an Xpenology

Successfully compiled the latest version of ds918p-7.1.1 but on boot the DSM installer is not reached: The boot stucks at: "Booting 'RedPill DS918+ v7.1.1-42962 (SATA, Verbose)' ....... ...... Decompressing Linux... Parsing ELF... done Booting the kernel." I want to compile with another version but during the build process I end up with this message: "No adequate space on /mnt/sda3/auxfiles to download file into cache folder, clean up the space and restart" How to "clean up"? Because I have already deleted the /auxfiles folder and it has not helped Thanks in advance

First question: Following the following the tutorial: Tutorial: Install/Migrate to DSM 7.x with TinyCore RedPill (TCRP) Loader Step 3. Boot into TinyCore and Complete Pre-Configuration Updates When booting the virtual machine (I am on ESXI 7.03), Tinyboot boots correctly but I don´t have mouse support and I need to change keyboard layout (from US to ES). I'm not very proficient with the Linux console but is it possible to force mouse recognition in the virtual machine and change the keyboard with console commands? Second question: Another question: I use a 6500 i5 (Sky Lake) for vmware esxi 7. When selecting platform: STEP 1 from the same tutorial: Step 1. Choose a DSM Platform/Architecture. From available platforms: 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 etc, etc There is not a platform Sky Lake. I understand that I must choose a platform compatible with the processor on which ESXi runs. I'm right? Thanks in advance

Al final he `pillado un "clon" de la Fujitsu 9211-8i D2607 LSI ya con el firmware IT por poco mas de 15€ en Aliexpress, cables incluidos. Funciona a la primera. La unica pega que creo que es inevitable es quen para todos los discos que tenia en modo RAW "ha desaparecido" el "rdmname.vmdk" de cada uno de ellos en el almacen de datos. Estaban inicialmente en una controladora SATA y esxi los identificaba con un nombre diferente al que aparece ahora por lo que supongo que habra que "rehacer" el puntero RDM. Ha sido volver a conectar los discos a la controladora SATA y todo OK a la primera.

A ver si algo de aqui te sirve. Aunque es para otros modelos de tarjeta igual te orienta algo: https://comomolatodo.com/2017/09/08/las-lsi-9211-8i-y-el-modo-it/ https://nguvu.org/freenas/Convert-LSI-HBA-card-to-IT-mode/ https://www.broadcom.com/support/knowledgebase/1211161495925/flash-upgrading-firmware-on-lsi-sas-hbas-upgraded-firmware-on-92

editado por no haber citado correctamente

I'll test one by one on a bare metal test rig and see what happens Thanks a lot

Thanks. This is the info I needed to know. About this: "Unless you have other passthrough devices or more than two controllers, don't deviate from the above." I want to add a board Asmedia with 6 SATA ports and a JMICRON with 5 SATA ports form a total of 15 ports (my main board has only 4 SATA ports. I am on ds918+ In this case how should I configure grub.cfg? 1. No passthrough for none of the boards 2. Passthrough for one or both boards This config in possible? Thanks in advance and sorry for the inconvenience

One aditional question. The disk with the boot loader (synoboot.vmdk) on SATA:0:0 is "visible" as a drive on Xpenology. How can I "hide" it?. If I add another Virtual Sata controller to the VM and add new disks to it these are not visible on Xpenology. Running Xpenology as a VM on ESXi, what about the param "set sata_args='SataPortMap=xyz" on grub.cfg? It's important? I don't know very well ifin this case should be configured or not. And how to do it. If I append a new "real" SATA board I need to modify sata_args? sorry if the questions seem silly but I am a newbie to both esxi and xpenology.I am simply trying to understand how disk allocation works