giorgosperi
-
Posts
20 -
Joined
-
Last visited
Posts posted by giorgosperi
-
-
6 hours ago, alienman said:
Hi @giorgosperi,
To create the Virtual Machine and install on it the redpill-tinycore I've used this basic guide: https://www.tsunati.com/blog/xpenology-7-0-1-on-esxi-7-x. With some tips from: https://xpenology.club/install-dsm-7-on-baremetal-or-vm/
And I've added some custom tweaks:
- After download the (last) VMDK of the redpill-tinycore I upload it to my ESXi server, and before adding the disk to the VM I do a VMDK copy: "vmkfstools -i tinycore-redpill.v0.4.6.vmdk -d thin thin-tinycore-redpill.v0.4.6.vmdk". The reason is because the image is created using the qemu tools, and it could generate errors. So I prefer to create a new image from the source, and set the type that I want to use (in this case "thin").
- For the Hard Disk controllers in the VM I use: 1 SATA (0:0) for the redpill bootdrive; 1 SATA (1:0) for the HDD disks (configured as SATA); 1 pvscsi (0:0) for the SSD Cache disks; 1 NMVe only for testing as for nvme disks the SMART fails (lacks a redpill shim). In the future I'll try to passthrough real NVMe disks.
- All HDD (vmdk or RDM) are connected to the second SATA controller. And all SSD (vmdk or RDM) are connected to the pvSCSI controller. Remember to edit the .VMX file to add the corresponding flag of force-SSD-type: scsi0:0.virtualSSD = "TRUE".
- Also I've installed one open-vm-tools package:
But for this we need to work on finishing the shutdown support.
For the rest, it's more or less what you prefer to do. Perhaps a new guide "How to install DSM 7.0 in ESXi with HDD and CACHE" could be writed for this forum. Don't think so?
Regards.
let me check. thanks for that. i was trying yesterday for tinycore i installed it also on my esxi but i couldnt see the gui i guess the vmdk was without the gui. but when i tried to do sftp or ftp or with putty it didnt let me log in. i guess i did something wrong on the installation.
my previous installation i did it on an ubuntu that i have but there is missing some stuff that tinycore has.
yeah probably a guide that has whatever workarounds and fixes because right now i find multiple informations and guides here and there.
*you were right with this guide tinycore worked. so now i m moving to start building the image etc
-
3 hours ago, alienman said:
Hi @giorgosperi,
I don't want to be rude. I understood you mentioned that it can't be detected as a SSD. So if the problem is the target platform (DS315xs vs DS3622xs+), then we know now that it's preferable to use the second, as it could detect both types (HDD and SSD) as your preference for virtual disks.
I apologize for the misunderstanding!
no worries sorry also for the questions that i have. to be honest i followed a guide for 3615xs. do you have one to follow for 3622 if you can please? on your setup it recognizes the ssd as ssd even sata configured?
-
On 3/19/2022 at 3:42 PM, alienman said:
That's not true, see this:
root@DSM:~# synodisk --isssd /dev/nvme0n1 dev:/dev/nvme0n1 is SSDIf you use the patch to discover the VNME devices on other PCI slots, then it will work with DSM 7.0.1-42218 with redpill configured for DS3622xs+ using a virtual NMVE device of ESXi 7. So we only need to solve the SMART data of the virtual NMVE devices, and we'll have all needed: physical and virtual devices, HDD or SSD, connected to DSM 7.0. Please, forget DSM 6.x !!
You think that maybe its not recognizing because i did for DS315xs ?
Thanks for the response...
-
On 3/12/2022 at 4:16 PM, alienman said:
FYI, in DSM 7.0 DS3622xs+ virtual nvme disks (ESXi 7) are detected as cache disks when configuring them:
still i think you cant use it as cache because on 7.0 is not detecting it as ssd. on 6.2.3 works because you can use scsi but on this version whatever i tried it didnt recognize the virtual drive if i configure it as scsi.
-
i ve done this but no luck. you think that it might be a missing driver? on 6.2.3 if you configure the virtual drive as scsi it recognizes it as ssd.
on this version is not recognizing scsi at all.
-
i know that the speed is going to be the same. just i wanted to add the drive as SSD cache. it doesnt allow me to do it if its getting recognized as regular drive.
-
i just installed 7.0.1-42218
under esxi7
is there any way to make recognize a virtual disk as virtualSSD or NVME?
on 6.2.3 i used to have it as scsi and DSM was recognizing the disk as SSD.
i m trying to use a partition of SSD or NVME as cache.
-
10 hours ago, Orphée said:
As long as you only added the missing driver and left user_config.json exactly the same, just replace loader disk (SATA 0:0)
And it should be strait forward. Nothing else to do if you already are at same DSM version.
If you upgrading, read other thread/posts. Others did it already. But DSM should ask you to upgrade, as usualthanks i think i got it. i ll check also the other posts to upgrade the old one
-
13 hours ago, giorgosperi said:
how i do that? i just load the new pat file?
just an update. i added the vmxnet3 driver in the image and it recognized full speed the sfp+ card but i did this like a new installation.
how i can update the existing installation with the new image? sorry for the questions i m missing only this part.
-
47 minutes ago, Orphée said:
Yes
how i do that? i just load the new pat file?
-
2 hours ago, Orphée said:
The MAC address set in json will override MAC address used in ESXi VM setting when loader boot (like it does on baremetal).
So of course it is better to have it matching in order to have the same DHCP IP when boot on Tinycore OS vs DSM. But it is not mandatory.as long as your only default LAN card on ESXi is the card you want (sfp+). it should work.
yeah i think my case is just that i dont have the vmxnet3 loaded on the image that i installed. can i build a new image with the driver and upgrade it on the existing one?
-
3 hours ago, Orphée said:
the mac address is defined on ESXi VM settings... So I don't understand you.
Or you give the card like PCI passthrough directly inside the VM, and then yes you have to manage the card directly.
But I don't catch you on this... How is your ESXi configuration set ?
yeah i know just i thought that you have to match on the json that you make before the build of the image the mac address of your nic that is my virtual nic.
-
2 minutes ago, Orphée said:
If it is you main and only LAN card, you don't need a mac2 value.
From ESXi point of view, as long as you are not using passthrough and only let ESXi handle lan card. you only have to match number card between real and VM.
So you if you want to have 2 lan card inside your ESXi, yes you will need mac1 and mac2.... etc...
yeah but right now the image i think i built it based on the other card so its going to be different mac address. maybe i ll remake the image just with one card the sfp+ but is it possible to make the image with the vmxnet3 and lets say upgrade it on the existing installation or i will have to start from the beginning?
-
3 minutes ago, Orphée said:
You run the "ext add" command before launching the build command.
The missing ext should then be added to the loader. as usual.
Edit : I'm assuming you are using Tinycore OS from @pocopico , if not, you already probably know how to add an extension from @haydibe script.
i built the image on ubuntu. i guess its the same process. my knowledge on this is a bit limited but i think i m getting it.
so before the build command i run the ext add to add the vmxnet3 driver. i need also to add the mac addess of this card as mac2 i dont think that i did it on the image that i have. can i 'upgrade' the existing installation with the new image that im going to make or i will need to redo it?
-
2 minutes ago, Orphée said:
If the expected driver is Vmxnet3, you may want to manually install it :
./rploader.sh ext [loader_version] add https://raw.githubusercontent.com/pocopico/rp-ext/main/vmxnet3/rpext-index.jsonand then launch your build.
Or you can change VM settings to E1000e and install the matching extension :
https://raw.githubusercontent.com/pocopico/rp-ext/master/e1000e/rpext-index.jsone1000e is working fine with my other gigabit card.
on one of my tests i used e1000e on the sfp+ card and recognized the card but as a gigabit card.
yeah for this card is expecting VMXNET3 to fully recognize it.
so i have to add it on the image and after reinstall it using the new image?
-
On 3/2/2022 at 4:21 PM, RedwinX said:
If you read/search on this post, I can confirm you that you can upgrade easily from 6.2.3 to 7.0.1. Please make a backup first, as always. The upgrade is simple, and works fine (tested on 5 xpenology in production --> upgrade from jun's loader 1.04b/1.03b).
For sfp+, what's your card reference? You can use extension from @pocopico. Just give me the reference of your card, and I will told you which driver used.
I m using this sfp+ card BCM957810A1006G Broadcom. On 6.2.3 works fine with VMXNET 3. ( i have it under esxi). On 7.0.1 it's not showing it.
I will check about the upgrade it is on the previous pages?
Thanks for the response also.
i started reading the posts i saw other people having the same issue. I guess the driver is missing? Can i add somehow the driver on the existing installation?
-
hi, i installed dsm 7.0.1-42218 on esxi.
the only issue that i have so far is that its not detecting the sfp+ card. on 6.2.3-25426 it was working.
also do you know if i can upgrade the 6.2.3 to 7.0.1?
thanks
-
- Outcome of the update: SUCCESSFUL
- DSM version prior update: DSM 7.0.1-42218 Update 2
- Loader version and model: RedPill DS3615xs v7.0.1-42218 Beta
- Using custom extra.lzma: NO
- Installation type: esxi 7.0U3
- Additional comments: everything looks fine so far just a question. on the same version of esxi but the older xpenology my sfp+ card is working fine. on this version of xpenology it doesnt detects the card. Anybody has similar setup or an other NIC card maybe to buy?
-
I couldnt find where to add this post. Sorry if i did wrong.
I just have an issue if andybody has an idea.
I m running under esxi 7.0
So i created one virtual drive for files etc. and 4 virtual drives for ssd cache mounting on esxi 4 virtual drives from one ssd that i have.
The issue that i have is that after reboot i m loosing one of the ssdcache virrtual drives
Do you have any idea?
Thank you in adance
TinyCore RedPill Loader (TCRP)
in Loaders
Posted
me why i m still getting syntax error? lol