[DSM 7.2-64570 Update 3]

- Outcome of the update: SUCCESSFUL

- DSM version prior update: DSM 7.1.1-42962 (really!)
- Loader version and model: TCRP v0.9.4.9c w\Friend 0.0.8j DS3622xs+
- Using custom extra.lzma: NO
- Installation type: BAREMETAL - SuperMicro X10SL7-F with integrated LSI RAID, 8*4tb SAS drives 

- Additional comments: Loaded the PAT, rebooted no further intervention, all drives and data preserved

[TinyCore RedPill Loader (TCRP)]

14 hours ago, dusty_dragon said:

Has it worked for you? I changed to UEFI on Hyper-V and booted with a hard disk converted from tinycore-redpill-uefi.v0.9.4.8.img. to *.vhdx. 

No luck getting it to work.

 

I wonder if "tinycore-redpill-uefi.v0.9.4.8" can ever be run of Hyper-V?

Sorry, not running in Hyper-V, but that error indicates not booting in UEFI 

[TinyCore RedPill Loader (TCRP)]

4 hours ago, dusty_dragon said:

 

Thanks in advance for a great work 

TinyCore RedPill Loader (TCRP)

 

I am also trying to run this on hyper-v (Windows 11) by creating a "tinycore-redpill-uefi.v0.9.4.8.vhdx" file from "tinycore-redpill-uefi.v0.9.4.8.iso"

For my case, Windows 11 hyper-v does not boot from the tinycrore iso image.

 

Since installation media is not usb, the command "sudo ./rploader.sh identifyusb" does not work.

 

After building with "sudo ./rploader.sh build ds3615xs-7.1.0-42661", the system does not work. I think Grub has been lost.

 

Before building - Running from hyper-v ; booted from a disk (not a usb)

 

 

after building - ssh connection is lost:

 

Cannot start VM after building 

 

 cat user_config.json:
 

 

 

BIOS needs to be set to UEFI boot

[DSM 7.0.1-42218]

Outcome of the installation/update: SUCCESSFUL

- DSM version prior update: DSM 6.2.3-25426 Jun's 1.04b bootloader

- Loader version and model: RedPill DS3615xs v7.0.1-42218 update 2

- Installation type: BAREMETAL - SuperMicro x10slm-f / 8* 4tb SAS drives

- Using custom extra.lzma: NO

- Additional comments: DSM update - 20 min, required prior to build:

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

 

 

[DSM 6.2.1-23824 - WARNING]

- Outcome of the installation/update: SUCCESSFUL

- DSM version prior update: DSM 6.2-23739 Update 2

- Loader version and model: JUN'S LOADER v1.03b - DS3615xs

- Using custom extra.lzma: NO

- Installation type: BAREMETAL - Lenovo LS140 onboard Intel [type] I217LM NIC

- Additional comments: NONE

[DSM 6.1.x Loader]

Updated my bare metal Lenovo ts140 to 1.02b without drama.

 

Thanks for continuing to provide this

[Torrent]

"You turn on beta packages?"

 

How do I turn on beta packages? Thanks for the replies!

Packages/Settings/beta

[Upgrade DSM 5.0-4528 to DSM 5.1-5022 Update 2 - Is It Safe]

The only bug I'm aware of is the expanding storage but that's not new in this release.

There's a thread related to that and a separate one for the update.

[5.1 -5022 update 2 expansion problem]

I had the same problem on 5022 update 1 adding a forth 3tb array already containing 3*3tb drives.

Eventually I deleted the entire configuration and restored from backup as I thought this was an issue I'd created, I was unable to identify anything locking the expansion.

[Question on update]

hi all i installd NB_x64_5032_DSM_50-4528_Xpenology_nl.img on the USB and then DSM_DS214play_4528.PAT on the computer and all is working OK

My Q is in the kontrollpannel it says i can update to DSM 5.1-5022 can i do that ?

 

ore do i install manualy DSM 5.0 4828 update 1 + 2

 

Thx all

do the manual update and then use the time I've saved you to search how many times this has come up in other threads!