Jump to content
XPEnology Community

thekidz

Rookie
  • Posts

    8
  • Joined

  • Last visited

Recent Profile Visitors

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

thekidz's Achievements

Newbie

Newbie (1/7)

0

Reputation

  1. Hi All I think I found my own answer. On Github it appears that by adding skip_vender_mac_interfaces="" to cmdline was the answer. My DS now boots with the correct IP from my dhcp server and is shows the inputed mac in the Synology DSM. As always I should read before I speak. I hope this helps someone else out Thanx Again
  2. Hi All I want to thank all for all the hard work put into all the loaders. I'm sure you are not thanked enough. I have been running flavors of xpenology since the 5. days. Without you guys this would never have happened. I was running DSM 7.2 with ARPL-i18n v23.8.7. With this version my mac address and serial number from another machine passed through fine and were shown correctly and worked in DSM. I run in ESXI with the video card, ethernet card, and Sata controller all in PCIE passthrough mode. This has worked well since Jun's loader days and has never had an issue. I went to upgrade to the latest version of rr but it wouldn't let me update and said I had to rebuild the loader. I shutdown the old VM and created a new VM with the same parameters. I booted RR v23.11.3 and built the loader adding my MAC and SN like i usually would, and built the loader. The upgrade to DSM 7.2.1 U1 went off without any issues and booted normally. The serial number passed through but the mac didn't. This has caused my machine to boot with a new ip on my home network. Dhcp provides a reserved IP for the mac address entered into RR. The correct mac shows up in the cmdline options of RR at the boot display. Why is the mac not passing through? Is this an issue with the current version of the loader? Is this something that i have done incorrectly? Is it possible to upgrade ARPL-i18n v23.8.7 to RR v23.11.3 via the manual update? If so could somebody please assist me in how to do this? Maybe this would keep the mac intact in the previous VM. Any help that could be offered would really be appreciated.
  3. Hi all I have managed to get redpill working on ESXI 7 U3 . with ds918+ 4 vcpus and dedicated 16g ram I have 1 virtual sata drive configured for the loader I have the cannon lake AHCI controller in passthrough with 6 sata drives 4 for storage and 2 sata cache drives. all in the right location I have a single port of a quad port intel x710 in passthrough 10g I have the intel iris 630 gpu in passthrough It has been running very stable for 2 months now. Don't ask me how I got there, but lets say, it was a lot of trial and error and a lot of reading. You guys are great and I can't thank you all enough. I would like to upgrade to 7.01-42218 update 3. I am currently on update 2. I have seen reports of this being successful on different versions of the tiny core loader. How can I tell which version of tinycore I am running on currently I don't remember. I think I may be on .45. Is it worth trying to upgrade to .46? Any help, thoughts or insight would be greatly appreciated.
  4. found the answer to the ide sata issue https://kb.vmware.com/s/article/1028943. I hope this helps someone.
  5. Hi all I have been a user of xpenology for years. I have 6.2 running in esxi 7U1 with 10g network cards sata controllers and graphics card passed through to DSM. I am trying to give redpill a test. My first attempt was to setup the vm as linux other 64 bit. I was able to install the tinycore vmdk and it looked like it compiled fine. IT was then that i noticed that it was configured as an ide drive. I blew that version away. I created another VM at linux 4 64bit and created a sata drive with the tinycore vmdk , but it refused to boot with the error. Failed to power on virtual machine redpill. Unsupported or invalid disk type 2 for 'sata0:0'. Ensure that the disk has been imported. Click here for more details. - dismiss Does anyone have a good recommended setting for esxi 7 to attempt a setup? Thank you in advance.
  6. Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.2.3 - 25423 - Loader version and model: JUN'S LOADER v1.04b - DS918+ - Using custom extra.lzma: YES 0.11 - Installation type: ESXI V7 - ASROCK H370M-ITX/ac | NIC: Intel intel x710-da2 1 port (passthrough) | Intel Cannon Lake AHCI (passthrough) | Intel UHD 630 graphics (passthrough) | Intel i5-9400 (2 cores) - Additional comments: Reboot required
  7. Hi all Just curious if extra.lzma for DS918+ v0.5_test or extra.lzma for DS918+ v0.4 work with 1.04b loader? I can't seem to find a definitive answer. Also if it does not work, can someone please point me to the 1.03a2 loader. I can't seem to find a link for it either. I am trying to get my nvme drives to function as a cache and can't seem to get the to work with 1.04b and 23739 so I thought I'd give a try with the 1.03a2 extra file a shot. Any help would be greatly appreciated. Thanx Craig
  8. Hi there I just built a new server based on an h370 with two m.2 drives that I would like to use as cached drives. I am not very efficient in Linux but I can follow directions. I'm very interested in how this pans out. Thanx Craig
×
×
  • Create New...