Jump to content
XPEnology Community

TinyCore RedPill Loader (TCRP)


pocopico

Recommended Posts

Not sure if you can do anything with this or not.  But I ran dmesg while in tc [    0.285607] pci 0000:08:00.0: [1000:0073] type 00 class 0x010400 SAS

                                                                                                                               [    0.285313] pci 0000:00:1f.2: [8086:1d02] type 00 class 0x010601 SATA

 

lspci -nnq 08:00.0 RAID bus controller [0104]: LSI Logic / Symbios Logic MegaRAID SAS 2008 [Falcon] [1000:0073] (rev 03)

                  00:1f.2 SATA controller [0106]: Intel Corporation C600/X79 series chipset 6-Port SATA AHCI Controller [8086:1d02] (rev 05) (on board sata)

 

On the elusive hunt for the Satamap and DiskID

Link to comment
Share on other sites

tc@box:~$ sudo ./rploader.sh update now
Checking Internet Access -> OK
Checking if a newer version exists on the repo -> sha256sum: latestrploader.sh: No such file or directory
There is a newer version of the script on the repo should we use that ? [yY/nN]y
OK, updating, please re-run after updating
cp: cannot stat ‘/home/tc/latestrploader.sh’: No such file or directory
Updating tinycore loader with latest updates
Backing up files to /mnt/sdb3//mydata.tgz
Done.

 

what a mistake this is, I can't go on?

Link to comment
Share on other sites

I'm also stuck on the hunt for the Satamap and DiskID values... I am in Tinycore and this is my output when I do lspci -nnq. Sorry for the screenshot, how do I get the output from my VMWare Workstation to my host? 

image.thumb.png.659cef155faffcaa9c9cb462063bb616.png

 

This is just on my testing system, the system where I want to run the actual installation already has DSM 6 installed now, so I would really like to understand how to get the right settings, so I can apply it to other installations as well. I got as far as uploading the .pat file but then it says it's corrupt, and my Tinycore is gone because it wiped the partition.

Link to comment
Share on other sites

For information purpose and anybody that gives nights to solve the Puzzle:

 

VMWare ESXi and TinyCore runs great if placed in the Hypervisor via SATA 0:0

 

Flawlessly.

 

In my Case the Problem was the igbx Extension ( thanks @pocopico!) that gave a kernel Panic

 

Imagine how long I’ve been looking at the Machine, the Drives, the NIC…even Cables…

 

I don’t know how to remove an extension, since rploader.sh detects Hardware and places Extensions into the build.

 

The trick was to boot only with minimum Hardware (VM) like VMNET3 NIC and TinyCore Volume, modify the Loader and…that solved my struggle.

 

I can edit SataPortConfig and so on before Build, when I disconnect the passthrough devices…then build, shutdown and reboot with newly builded Settings.

 

Great.

 

Last step: Drive 1 is empty and my PortConfig seems to be complicated.

 

I do have an 3rd controller besides my 2 HBA, but it won’t go to disk 17 behind the Port limit, even 13 (behind the physical attached Disks) doesn’t.

 

Just cosmetics, it’s an Hot-Spare…

 

Running now an I know how. Oh boy, these days were long an annoying. But informative!

 

Thanks to all here, great to get this further, since @ThorGroup seems to be MIA and stay…

  • Like 2
Link to comment
Share on other sites

On 1/14/2022 at 2:45 AM, magara said:

HP microserver Gen8 AHCI baremetal

 

i have foud chinese page that mention something about powerbutton dsm7 acpid

https://www.openos.org/threads/powerbutton-for-dsm7.3696/

 

but files powerbutton-7.0-bromolow.tar + install.sh are missing

 

maybe i have to make new tinycore loader and add 

./rp-helper.sh ext bromolow-7.0.1-42218 add https://github.com/jumkey/redpill-load/raw/develop/redpill-acpid/rpext-index.json

 

and then migrate  to new loader or can i update recompile existing usb stick ?

 

maybe somebody know what to do with it :))  thanks

Link to comment
Share on other sites

1 hour ago, kiberboi said:

I did it during the installation. I still get abovementioned error.

I got the same error as you when used the satamap script to try and determine what I had. In the end I had to manually change the satamap to =1 and left the other value (diskidxmap) I think it was to 00.

 

Once I did that then the install went as planned. pocopico has advised a few people to try that and it appears to have got a lot of them going.

Link to comment
Share on other sites

1 hour ago, kiberboi said:

I did it during the installation. I still get abovementioned error.

I went thru same problem. Let me explain.

In original user.config.json is SataPortMap; "1" and DiskInxMap: "00"

 

When I run command sudo ./rploader.sh satamap now I got this: SataPortMap; "5" and DiskInxMap: "00" what is not correct because I got error when says something is error on hdd (2, 3, 4, 5)

 

Ok, then I left what is was on SataPortMap; "1" and DiskInxMap: "00" and when I install DSM it's showing only one HDD but I have 3. (Yes, I check in BIOS and it's recognize all 3)

 

Then I figure out to put number 3 in  SataPortMap because I have 3 hdd, but again when try to install DSM I got something is error on hdd (3)

 

Next what I did I change DiskInxMap: "00" with different numbers and what this have effect is just changing position number on hhd's. 

Example: if iI set up SataPortMap; "1" and DiskInxMap: "13" showing I have 1 hdd on position 13.

 

On end I put SataPortMap; "2" and DiskInxMap: "00" and I got 2 hdd showing in DSM on position 1 and 2. 

 

I did't have luck to install DSM with all 3 hdd but it's ok for now I'm happy how works.

 

What is annoying every time when I play around  SataPortMap and DiskInxMap in user.config.json i have to build the loader from beginning and that's so so annoying instead only to change that in user.config.json and save it. If u asking me how I now, I did try to change that and have no effect at all. So only way is to have to build the loader from scratch.

 

If someone know better/easier way please let us know.

Bu the way "pocopico," made great job making script/loader and I want to thank you so much.

Cheers

Edited by djoka
Link to comment
Share on other sites

So this morning I decided to increase the complexity of my testing, and introduced one of my older PCI Express SATA card (with 4 Sata Ports)

 

Test System configuration:
6 Sata ports on motherboard - 1 x 2TB Disk connected to port 0
4 Sata ports on my PCI Express Sata Card - 4 x 4TB Disks connected ports 0,1,2,3
1 USB thumb drive for the Tinycore Loader

  • I installed DSM 6.2 using the JUN 1.04b loader and configured:
  • Single disk Volume with the single 2TB Disk
  • SHR2 Volume with all 4 x 4TB Disks
  • Created two Shares one on each volume
  • copied some files to each, confirmed accessible from my PC
  • Rebooted and swapped USB thumb drives to the tinycore loader
  • Ran the command "sudo ./rploader.sh satamap now"
    • Which returned the following results:
      • SataPortMap=64
      • DiskIdxMap=0004

Building the loader with that configuration, the DSM 7 installer returned the SataPortMap errors on Disks 2,3,4,5,6 for Sata Controller 1

:(

 

I rebooted and edited my boot loader trying: SataPortMap=641 SataIdxMap=000105, however this still failed
 

(Remember that if you edit it in the boot loader menu (pressing e during the 4 seconds window) it only retains this configuration for that boot up. However this is enough for the DSM install to complete its detection process prior to the DSM 7 install)

 

I reran a few checks from the Telnet console of my DSM 7 Installer:


Extract for my TestNAS configuration from the dmesg within Tinycore:

dmesg |grep sd
[    0.781688] sd 0:0:0:0: [sda] 3907029168 512-byte logical blocks: (2.00 TB/1.82 TiB)

[    0.957422] sd 6:0:0:0: [sdb] 7814037168 512-byte logical blocks: (4.00 TB/3.64 TiB)
[    0.957548] sd 7:0:0:0: [sdc] 7814037168 512-byte logical blocks: (4.00 TB/3.64 TiB)
[    0.957697] sd 8:0:0:0: [sdd] 7814037168 512-byte logical blocks: (4.00 TB/3.64 TiB)
[    0.958227] sd 9:0:0:0: [sde] 7814037168 512-byte logical blocks: (4.00 TB/3.64 TiB)

[    7.964299] sd 10:0:0:0: [sdf] 30031872 512-byte logical blocks: (15.4 GB/14.3 GiB)


0:0:0:0 = Single Drive on 6 Port Sata Controller
6:0:0:0, 7:0:0:0, 8:0:0:0, 9:0:0:0 = 4 Drives on my 4 Port PCI Express Sata Card
10:0:0:0 = USB Thumb Drive

 

Remembering all the learnings from my previous nights testing:

 

I put together the following sataport configuration:


SataPortMap=141 (1 = 1 active disk on the first sata controller, 4 = 4 active disks on the 2nd controller, 1 = 1 active thumb drive)

&

DiskIdxMap=000105 (00 = index location of my first drive on 6 port sata controller, 01 = index location of my 4 drives for my PCI Express Sata Controller, 05 = index location of my USB thumb drive

 

Once booted with 141 + 000105, the test NAS Was migratable :)

NAS_TEST_SATACARD_2.thumb.png.89d99c68352309d58416b556fd91ce6d.png

 

After DSM 7 was installed and operational I remembered it booted with the original SataPortMap configuration: 64 + 0004.

 

Looking at DSM Storage manager, all disks were operational:

(Ignore the Failing drive, its an only crappy 4TB Drive with some bad sectors - fine for testing purposes)

NAS_TEST_SATACARD_1_storage_manager.thumb.png.fb9c86b32c806582f74af317e5c2c091.png

 

There were spaces between the disks based on the SataPortMap and SataIdxMap configuration:

NAS_TEST_SATACARD_1_storage_manager_after_sataidxmap_update.thumb.png.da842eebc09e5e482715f4d0c43eb63d.png

 

I rebooted again and reran the tinycore loader tool and re-setup my boot loader with the following SataPortMap Configuration.
"SataPortMap": "241",
"DiskIdxMap": "000206"

 

DSM 7 started up again without any need for reinstall and my DSM disk view looked as follows:

NAS_TEST_SATACARD_1_storage_manager_after_sataidxmap_update_drop_to_2_Sata_ports.thumb.png.78549b002418f217beaf33d16b3816d2.png

 

I hope this journey will help others.

 

I'm still contemplating upgrading my Production NAS. Just haven't made the jump yet.

  • Like 1
  • Thanks 2
Link to comment
Share on other sites

17 minutes ago, Dvalin21 said:

I will have to try all this, however im starting to believe that my SAS/SATA Raid card is just not compatible. Dell Perc H310

 

I think this extension might help? https://github.com/pocopico/rp-ext/blob/main/aacraid/rpext-index.json

 

"name": "aacraid",

"description": "Adds Dell PERC2, 2/Si, 3/Si, 3/Di, Adaptec Advanced Raid Products, HP NetRAID-4M, IBM ServeRAID & ICP SCSI driver Support"

  • Thanks 1
Link to comment
Share on other sites

I tried to run the tinyloader on my dads production NAS, we wanted to give it a go.. but it wouldn't detect any drives.

 

His DSM 6.2 NAS has a: LSI Logic / Symbios Logic SAS3008 PCI-Express Fusion-MPT SAS-3 (rev 02)

I tried adding this extension:

https://github.com/pocopico/rp-ext/blob/main/mpt3sas/rpext-index.json

"name": "mpt3sas",

"description": "Adds LSI MPT Fusion SAS 3.0 Device Driver Support",

 

But it still didn't seem to detect anything.

 

I assume the command to add it is just: "sudo ./rploader.sh ext broadwell-7.0.1-42218 add https://github.com/pocopico/rp-ext/raw/main/mpt3sas/rpext-index.json"

Because it says it adds it but no effect.

 

Link to comment
Share on other sites

51 minutes ago, killseeker said:

I tried to run the tinyloader on my dads production NAS, we wanted to give it a go.. but it wouldn't detect any drives.

 

His DSM 6.2 NAS has a: LSI Logic / Symbios Logic SAS3008 PCI-Express Fusion-MPT SAS-3 (rev 02)

I tried adding this extension:

https://github.com/pocopico/rp-ext/blob/main/mpt3sas/rpext-index.json

"name": "mpt3sas",

"description": "Adds LSI MPT Fusion SAS 3.0 Device Driver Support",

 

But it still didn't seem to detect anything.

 

I assume the command to add it is just: "sudo ./rploader.sh ext broadwell-7.0.1-42218 add https://github.com/pocopico/rp-ext/raw/main/mpt3sas/rpext-index.json"

Because it says it adds it but no effect.

 

Mine said the same but after help from pocopico he advised to add also mpt2sas. Maybe you can try that? Otherwise check with lspci -nnq.

Link to comment
Share on other sites

There are the 2 extracts, I'm wanting to upgrade to DSM7.0:

 

Primary NAS 1:

0000:00:00.0 Host bridge [0600]: Intel Corporation 4th Gen Core Processor DRAM Controller [8086:0c00] (rev 06)
0000:00:01.0 PCI bridge [0604]: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor PCI Express x16 Controller [8086:0c01] (rev 06)
0000:00:02.0 VGA compatible controller [0300]: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06)
0000:00:03.0 Audio device [0403]: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller [8086:0c0c] (rev 06)
0000:00:14.0 USB controller [0c03]: Intel Corporation 9 Series Chipset Family USB xHCI Controller [8086:8cb1]
0000:00:16.0 Communication controller [0780]: Intel Corporation 9 Series Chipset Family ME Interface #1 [8086:8cba]
0000:00:1a.0 USB controller [0c03]: Intel Corporation 9 Series Chipset Family USB EHCI Controller #2 [8086:8cad]
0000:00:1b.0 Audio device [0403]: Intel Corporation 9 Series Chipset Family HD Audio Controller [8086:8ca0]
0000:00:1c.0 PCI bridge [0604]: Intel Corporation 9 Series Chipset Family PCI Express Root Port 1 [8086:8c90] (rev d0)
0000:00:1c.2 PCI bridge [0604]: Intel Corporation 9 Series Chipset Family PCI Express Root Port 3 [8086:8c94] (rev d0)
0000:00:1c.3 PCI bridge [0604]: Intel Corporation 9 Series Chipset Family PCI Express Root Port 4 [8086:8c96] (rev d0)
0000:00:1c.4 PCI bridge [0604]: Intel Corporation 9 Series Chipset Family PCI Express Root Port 5 [8086:8c98] (rev d0)
0000:00:1d.0 USB controller [0c03]: Intel Corporation 9 Series Chipset Family USB EHCI Controller #1 [8086:8ca6]
0000:00:1f.0 ISA bridge [0601]: Intel Corporation H97 Chipset LPC Controller [8086:8cc6]
0000:00:1f.2 SATA controller [0106]: Intel Corporation 9 Series Chipset Family SATA Controller [AHCI Mode] [8086:8c82]
0000:00:1f.3 SMBus [0c05]: Intel Corporation 9 Series Chipset Family SMBus Controller [8086:8ca2]
0000:01:00.0 Serial Attached SCSI controller [0107]: Broadcom / LSI SAS3008 PCI-Express Fusion-MPT SAS-3 [1000:0097] (rev 02)
0000:03:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 06)
0000:04:00.0 PCI bridge [0604]: Intel Corporation 82801 PCI Bridge [8086:244e] (rev 41)
0000:06:00.0 Ethernet controller [0200]: Intel Corporation 82571EB/82571GB Gigabit Ethernet Controller D0/D1 (copper applications) [8086:105e] (rev 06)
0000:06:00.1 Ethernet controller [0200]: Intel Corporation 82571EB/82571GB Gigabit Ethernet Controller D0/D1 (copper applications) [8086:105e] (rev 06)
0001:00:12.0 Non-VGA unclassified device [0000]: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series SATA AHCI Controller [8086:5ae3] (rev ff)
0001:00:13.0 Non-VGA unclassified device [0000]: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series PCI Express Port A #1 [8086:5ad8] (rev ff)
0001:00:14.0 Non-VGA unclassified device [0000]: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series PCI Express Port B #1 [8086:5ad6] (rev ff)
0001:00:15.0 Non-VGA unclassified device [0000]: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series USB xHCI [8086:5aa8] (rev ff)
0001:00:16.0 Non-VGA unclassified device [0000]: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series I2C Controller #1 [8086:5aac] (rev ff)
0001:00:18.0 Non-VGA unclassified device [0000]: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series HSUART Controller #1 [8086:5abc] (rev ff)
0001:00:19.2 Non-VGA unclassified device [0000]: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series SPI Controller #3 [8086:5ac6] (rev ff)
0001:00:1f.1 Non-VGA unclassified device [0000]: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series SMBus Controller [8086:5ad4] (rev ff)
0001:01:00.0 Non-VGA unclassified device [0000]: Marvell Technology Group Ltd. 88SE9215 PCIe 2.0 x1 4-port SATA 6 Gb/s Controller [1b4b:9215] (rev ff)
0001:02:00.0 Non-VGA unclassified device [0000]: Intel Corporation I211 Gigabit Network Connection [8086:1539] (rev ff)
0001:03:00.0 Non-VGA unclassified device [0000]: Intel Corporation I211 Gigabit Network Connection [8086:1539] (rev ff)
 

Primary NAS 2:

0000:00:00.0 Host bridge: Intel Corporation Device 5918 (rev 05)
0000:00:01.0 PCI bridge: Intel Corporation Skylake PCIe Controller (x16) (rev 05) (prog-if 00 [Normal decode])
0000:00:01.1 PCI bridge: Intel Corporation Skylake PCIe Controller (x8) (rev 05) (prog-if 00 [Normal decode])
0000:00:13.0 Non-VGA unclassified device: Intel Corporation Sunrise Point-H Integrated Sensor Hub (rev 31)
0000:00:14.0 USB controller: Intel Corporation Sunrise Point-H USB 3.0 xHCI Controller (rev 31) (prog-if 30 [XHCI])
0000:00:14.2 Signal processing controller: Intel Corporation Sunrise Point-H Thermal subsystem (rev 31)
0000:00:16.0 Communication controller: Intel Corporation Sunrise Point-H CSME HECI #1 (rev 31)
0000:00:1c.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port #5 (rev f1) (prog-if 00 [Normal decode])
0000:00:1c.5 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port #6 (rev f1) (prog-if 00 [Normal decode])
0000:00:1c.6 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port #7 (rev f1) (prog-if 00 [Normal decode])
0000:00:1d.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port #9 (rev f1) (prog-if 00 [Normal decode])
0000:00:1f.0 ISA bridge: Intel Corporation Sunrise Point-H LPC Controller (rev 31)
0000:00:1f.2 Memory controller: Intel Corporation Sunrise Point-H PMC (rev 31)
0000:00:1f.4 SMBus: Intel Corporation Sunrise Point-H SMBus (rev 31)
0000:02:00.0 Serial Attached SCSI controller: LSI Logic / Symbios Logic SAS3008 PCI-Express Fusion-MPT SAS-3 (rev 02)
0000:03:00.0 Ethernet controller: Intel Corporation I210 Gigabit Network Connection (rev 03)
0000:04:00.0 Ethernet controller: Intel Corporation I210 Gigabit Network Connection (rev 03)
0000:05:00.0 PCI bridge: ASPEED Technology, Inc. AST1150 PCI-to-PCI Bridge (rev 03) (prog-if 00 [Normal decode])
0000:06:00.0 VGA compatible controller: ASPEED Technology, Inc. ASPEED Graphics Family (rev 30) (prog-if 00 [VGA controller])
0001:00:02.0 Non-VGA unclassified device: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D PCI Express Root Port 2 (rev ff) (prog-if ff)
0001:00:02.2 Non-VGA unclassified device: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D PCI Express Root Port 2 (rev ff) (prog-if ff)
0001:00:03.0 Non-VGA unclassified device: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D PCI Express Root Port 3 (rev ff) (prog-if ff)
0001:00:03.2 Non-VGA unclassified device: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D PCI Express Root Port 3 (rev ff) (prog-if ff)
0001:00:1f.0 Non-VGA unclassified device: Intel Corporation C224 Series Chipset Family Server Standard SKU LPC Controller (rev ff) (prog-if ff)
0001:00:1f.3 Non-VGA unclassified device: Intel Corporation 8 Series/C220 Series Chipset Family SMBus Controller (rev ff) (prog-if ff)
0001:06:00.0 Non-VGA unclassified device: Marvell Technology Group Ltd. Device 1475 (rev ff) (prog-if ff)
0001:08:00.0 Non-VGA unclassified device: Marvell Technology Group Ltd. 88SE9235 PCIe 2.0 x2 4-port SATA 6 Gb/s Controller (rev ff) (prog-if ff)
0001:09:00.0 Non-VGA unclassified device: Intel Corporation I210 Gigabit Network Connection (rev ff) (prog-if ff)
0001:0c:00.0 Non-VGA unclassified device: Intel Corporation I210 Gigabit Network Connection (rev ff) (prog-if ff)
0001:0d:00.0 Non-VGA unclassified device: Intel Corporation I210 Gigabit Network Connection (rev ff) (prog-if ff)

Link to comment
Share on other sites

Hopefully this helps someone:

 

I installed on ESXi6. Converted the vmdk so i could add it as sata on a virtual controller. I pass-through the onboard of an HP ml310e gen8 which has 6 Ports.

After much testing and trying to understand the following works:

 

"SataPortMap": "16",
"DiskIdxMap": "1600"

 

16 = 1 Drive on the virtual sata controller which holds the tinycore, 6 Drives on the passed through onboard controller (AHCI Mode)

1600 = index 16 for the boot device since its not wanted/needed, 00 to have the first Drive of the passed through controller shown as the first drive in Synology

 

thanks for everyone else for their contributions :-)

Link to comment
Share on other sites

I did some production testing on 2 systems tonight.

 

I was unable to get 3617XS to detected any disks with the following extensions:

sudo ./rploader.sh ext broadwell-7.0.1-42218 add https://raw.githubusercontent.com/pocopico/rp-ext/master/mptspi/rpext-index.json
sudo ./rploader.sh ext broadwell-7.0.1-42218 add https://raw.githubusercontent.com/pocopico/rp-ext/master/mptsas/rpext-index.json
sudo ./rploader.sh ext broadwell-7.0.1-42218 add https://raw.githubusercontent.com/pocopico/rp-ext/master/mpt2sas/rpext-index.json
sudo ./rploader.sh ext broadwell-7.0.1-42218 add https://raw.githubusercontent.com/pocopico/rp-ext/master/mpt3sas/rpext-index.json

 

I did however have success with 3615XS in detecting disks using these extensions:

sudo ./rploader.sh ext bromolow-7.0.1-42218 add https://raw.githubusercontent.com/pocopico/rp-ext/master/mptspi/rpext-index.json
sudo ./rploader.sh ext bromolow-7.0.1-42218 add https://raw.githubusercontent.com/pocopico/rp-ext/master/mptsas/rpext-index.json
sudo ./rploader.sh ext bromolow-7.0.1-42218 add https://raw.githubusercontent.com/pocopico/rp-ext/master/mpt2sas/rpext-index.json
sudo ./rploader.sh ext bromolow-7.0.1-42218 add https://raw.githubusercontent.com/pocopico/rp-ext/master/mpt3sas/rpext-index.json

 

The only issue I ran into with my 3615XS system. I found the bios was using UEFI USB boot in my bios with the 918+ boot loader. Switching it to Legacy allowed me to boot the Tinycore loader, however my DSM 7 installer came up as "Not Installed" Rather than Migratable. I checked in the DSM installer Telnet options and found all my disks were visible. I just didnt want to proceed to install DSM 7 if it was going to wipe all drives rather than migrate over my existing DSM configuration / data.

 

Are there any known issues with moving from UEFI loaders to Tinycore Loader that could be causing this?

 

If I was disconnect my PCI Sata controller, then install DSM 7.0 to another disk off the motherboard SATA Ports, could I add the PCI Sata Controller after DSM 7 is installed and expect to see the Sata Controller + Disk on reboot? (Obviously I'd make sure the SATA Controller drivers are loaded and I update my SATAPortMAP + SATAIDXMap entries in the loader....

 

Any suggestions would be really appreciated, thanks.

 

 

Edited by killseeker
Link to comment
Share on other sites

I got the files running but now the build wont run 
./rploader.sh build bromolow-7.0.1-42218 static
tc@box:~$ ./rploader.sh build bromolow-7.0.1-42218 static
./rploader.sh: line 439: jq: command not found
./rploader.sh: line 423: jq: command not found
./rploader.sh: line 423: jq: command not found
./rploader.sh: line 877: jq: command not found
./rploader.sh: line 878: jq: command not found
./rploader.sh: line 879: jq: command not found
./rploader.sh: line 880: jq: command not found
./rploader.sh: line 881: jq: command not found
./rploader.sh: line 882: jq: command not found
./rploader.sh: line 883: jq: command not found
./rploader.sh: line 884: jq: command not found
./rploader.sh: line 885: jq: command not found
./rploader.sh: line 886: jq: command not found
./rploader.sh: line 887: jq: command not found
./rploader.sh: line 888: jq: command not found
./rploader.sh: line 888: jq: command not found
./rploader.sh: line 889: jq: command not found
./rploader.sh: line 889: jq: command not found
./rploader.sh: line 890: jq: command not found
./rploader.sh: line 890: jq: command not found
./rploader.sh: line 891: jq: command not found
Error : Platform not found
./rploader.sh: line 416: jq: command not found
./rploader.sh: line 416: jq: command not found
rploader.sh

 

Edited by sojab0on
Link to comment
Share on other sites

You have just putthe vmdk on your ESXI server that does not work 

You will need to convert it to the proper format for ESXI 

i had the same thing 

Setup SSH on your host and go to the datastore on your host where the vmdk is stored

 

use cd /vmfs/volumes/datastorename/ replace datastorename with teh actual name of the datastore


and run this vmkfstools -i HostedVirtualDisk ESXVirtualDisk replace hostedvirtual disk with /vmfs/volumes/datastorename/path to vmdk  and replace ESXIVirtualdisk with the name of the new vmdk file with teh same path in front of it. 

 

  • Thanks 1
Link to comment
Share on other sites

25 minutes ago, sojab0on said:

You have just putthe vmdk on your ESXI server that does not work 

You will need to convert it to the proper format for ESXI 

i had the same thing 

Setup SSH on your host and go to the datastore on your host where the vmdk is stored

 

use cd /vmfs/volumes/datastorename/ replace datastorename with teh actual name of the datastore


and run this vmkfstools -i HostedVirtualDisk ESXVirtualDisk replace hostedvirtual disk with /vmfs/volumes/datastorename/path to vmdk  and replace ESXIVirtualdisk with the name of the new vmdk file with teh same path in front of it. 

 

This is the easy way. The hard way is to take the image file export it with Starwind V2V converter to a local ESXi vmdk file. You get two files upload them to ESXI and then create your virtual machine.

  • Thanks 1
Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...