Jump to content
XPEnology Community

TinyCore RedPill Loader (TCRP)


pocopico

Recommended Posts

So I tried to upgrade my test box from 3615xs running 7.0.1 to 3622xs+ running 7.1...

 

Platform is a 3rd gen i5...

 

now before the upgrade I always had a message saying the 3rd disk had errors and the port was disabled. post upgrade (loader only, dsm not installed yet) I get a message stating disk 3 and 4 have errors and the ports have been disabled...

 

now there's only 1 sata drive connected, booting from usb... but the web assistant refuses to continue.

 

setup set sataportmap to 6 and diskidxmap to 00

 

output on telnet:

SynologyNAS> fdisk -l
Disk /dev/sda: 466 GB, 500107862016 bytes, 976773168 sectors
60801 cylinders, 255 heads, 63 sectors/track
Units: sectors of 1 * 512 = 512 bytes

Device  Boot StartCHS    EndCHS        StartLBA     EndLBA    Sectors  Size Id Type
/dev/sda1    0,32,33     310,37,47         2048    4982527    4980480 2431M fd Linux raid autodetect
/dev/sda2    310,37,48   571,58,63      4982528    9176831    4194304 2048M fd Linux raid autodetect
/dev/sda3    587,111,37  1023,254,63    9437184  976568351  967131168  461G fd Linux raid autodetect
Disk /dev/synoboot: 14 GB, 15382609920 bytes, 30044160 sectors
14670 cylinders, 64 heads, 32 sectors/track
Units: sectors of 1 * 512 = 512 bytes

Device       Boot StartCHS    EndCHS        StartLBA     EndLBA    Sectors  Size Id Type
/dev/synoboot1 *  0,32,33     6,62,56           2048     100351      98304 48.0M 83 Linux
/dev/synoboot2    6,62,57     15,205,62       100352     253951     153600 75.0M 83 Linux
/dev/synoboot3    15,205,63   130,138,8       253952    2097151    1843200  900M 83 Linux
Disk /dev/md0: 2431 MB, 2549940224 bytes, 4980352 sectors
622544 cylinders, 2 heads, 4 sectors/track
Units: sectors of 1 * 512 = 512 bytes

Disk /dev/md0 doesn't contain a valid partition table
Disk /dev/md1: 2047 MB, 2147418112 bytes, 4194176 sectors
524272 cylinders, 2 heads, 4 sectors/track
Units: sectors of 1 * 512 = 512 bytes

Disk /dev/md1 doesn't contain a valid partition table

 

I guess the first check before the upgrade should have been to see if the 3rd disk actually had errors:-P

Link to comment
Share on other sites

Hi guys,

 

I am using the 918+ ApolloLake dsm 7.1.0-42661 configuration. PID, VID and Mac address where set correctly. I get this error when I try to install :

 

We've detected errors on the hard drives (1, 2), and the SATA ports have also been disabled. Please shut down your DS918+ to replace or remove the hard drives and try again. 

 

I have a DESKTOP with E-2126G 16G RAM 4 HGST sata drives,the motherboard has 4 sata ports.

Link to comment
Share on other sites

Hello

 

I am using the 918+ with dsm 7.1.0-42661 on Proxmox. I give the VM 6 GB ram and 6 core CPU. But I checked the inforation panel in DSM and it show only 4 core.

The DSM can use 6 core (and just show 4 in info panel), or DSM can use only 4 core with 918+?

syno.JPG

Link to comment
Share on other sites

21 minutes ago, RedCat said:

Hello

 

I am using the 918+ with dsm 7.1.0-42661 on Proxmox. I give the VM 6 GB ram and 6 core CPU. But I checked the inforation panel in DSM and it show only 4 core.

The DSM can use 6 core (and just show 4 in info panel), or DSM can use only 4 core with 918+?

syno.JPG

Check @FOXBIvideo tutorial on YT. There is simple manual how to update this information. Basically, you see what is assigned to your DSmodel (it is a fix value).

Ram is assigned dynamically. Whatever you see, your system uses hardware of your machine. It does not matter what is displayed in CPU section.

Link to comment
Share on other sites

update more... after reboot plugged in all the drives again... sataportmap back to 6, hotplug 1... the 2nd drive is now back... the 3rd drive shows up in slot 5 and is flagged as critical... now this drive has zero bad sectors... has the lowest number of powered on hours... comes back with a clean smart test... drive 1 on the other hand has 336 bad sectors yet is marked as healthy, hours also slightly higher than drive 3 aka 5.

 

could this mean that something in redpill is mixing up the smart test results?

Link to comment
Share on other sites

50 minutes ago, TomY said:

Check @FOXBIvideo tutorial on YT. There is simple manual how to update this information. Basically, you see what is assigned to your DSmodel (it is a fix value).

Ram is assigned dynamically. Whatever you see, your system uses hardware of your machine. It does not matter what is displayed in CPU section.

You got a little misunderstood. It doesn’t matter to me what the DSM shows. I want know that, if it's worth giving more than 4 cores to the virtual machine? I gave it 6 core. Can DSM use more than 4 cores?

Link to comment
Share on other sites

9 minutes ago, RedCat said:

You got a little misunderstood. It doesn’t matter to me what the DSM shows. I want know that, if it's worth giving more than 4 cores to the virtual machine? I gave it 6 core. Can DSM use more than 4 cores?

Limitations are listed here...

 

Link to comment
Share on other sites

1 hour ago, RedCat said:

You got a little misunderstood. It doesn’t matter to me what the DSM shows. I want know that, if it's worth giving more than 4 cores to the virtual machine? I gave it 6 core. Can DSM use more than 4 cores?

Depends, u will run lots containers or lots vm/services on dsm? if not only 4 are fine. 

Link to comment
Share on other sites

1 hour ago, RedCat said:

You got a little misunderstood. It doesn’t matter to me what the DSM shows. I want know that, if it's worth giving more than 4 cores to the virtual machine? I gave it 6 core. Can DSM use more than 4 cores?

I understand. 1621 series is 6 core/12 thread Ryzen, and this is not the only one with >4 cores, so it does work.

 

VM hardware is often way more powerful than a typical nas device. Depending on this, even 1-2 cores might be good enough to start with and still more powerful than a 2 or 4 core J-series. If your VM CPU reaches the limit most the time, there is always possibility to scale up. 

 

For typical nas applications CPU overhead is rather less of a concern, memory and bandwidth might be far more important. If DSM runs on VM, most likely there is no sense to apply another level of virtualization, unless this is a convenience issue. Supervisor can handle other VMs and containers more effectively than VM in the VM (less overhead).

 

Link to comment
Share on other sites

3 hours ago, RedCat said:

Hello

 

I am using the 918+ with dsm 7.1.0-42661 on Proxmox. I give the VM 6 GB ram and 6 core CPU. But I checked the inforation panel in DSM and it show only 4 core.

The DSM can use 6 core (and just show 4 in info panel), or DSM can use only 4 core with 918+?

syno.JPG

Install this script, super easy, will show actual cpu details instead of reading details from db based on model of build

DSM and RP will not limit your cpu usage or ability regardless what info panel reports. :)

 

Link to comment
Share on other sites

Hi 

@pocopico 

 

I used DS3622 platform to build loader and the disk err still there(I changed a new ssd disk this time, booting with UEFI ), but the log were different:

 

what's the problem this time ,please, thank you.

 

SynologyNAS> cat /var/log/*rc*
START /linuxrc.syno.impl
Insert Marvell 1475 SATA controller driver
Insert basic USB modules...
:: Loading module usb-common ... [  OK  ]
:: Loading module usbcore ... [  OK  ]
:: Loading module ehci-hcd ... [  OK  ]
:: Loading module ehci-pci ... [  OK  ]
:: Loading module xhci-hcd ... [  OK  ]
:: Loading module xhci-pci ... [  OK  ]
:: Loading module usb-storage ... [  OK  ]
:: Loading kernel modules from extensions ...
Loading kmod #0 "mdio.ko" for pocopico.alx (args: )
Loading kmod #1 "alx.ko" for pocopico.alx (args: )
Loading kmod #0 "r8125.ko" for pocopico.r8125 (args: )
Loading kmod #0 "r8168.ko" for pocopico.r8168 (args: )
:: Loading kernel modules from extensions ... [  OK  ]
:: Executing "on_boot" custom scripts ...
Running "check-alx.sh" for pocopico.alx->on_boot
Loading module alx -> Module alx loaded succesfully
Ran "check-alx.sh" for pocopico.alx->on_boot - exit=0
Running "check-r8125.sh" for pocopico.r8125->on_boot
Loading module r8125 -> Module r8125 loaded succesfully
Ran "check-r8125.sh" for pocopico.r8125->on_boot - exit=0
Running "check-r8168.sh" for pocopico.r8168->on_boot
Loading module r8168 -> Module r8168 loaded succesfully
Ran "check-r8168.sh" for pocopico.r8168->on_boot - exit=0
Running "boot-wait.sh" for redpill-boot-wait->on_boot
Still waiting for boot device (waited 1 of 30 seconds)
Still waiting for boot device (waited 2 of 30 seconds)
Still waiting for boot device (waited 3 of 30 seconds)
Still waiting for boot device (waited 4 of 30 seconds)
Still waiting for boot device (waited 5 of 30 seconds)
Still waiting for boot device (waited 6 of 30 seconds)
Still waiting for boot device (waited 7 of 30 seconds)
Still waiting for boot device (waited 8 of 30 seconds)
Confirmed a valid-looking /dev/synoboot device
Ran "boot-wait.sh" for redpill-boot-wait->on_boot - exit=0
Running "install_rd.sh" for redpill-misc->on_boot
Starting ttyd, listening on port: 7681
Ran "install_rd.sh" for redpill-misc->on_boot - exit=0
:: Executing "on_boot" custom scripts ... [  OK  ]
Extensions processed
insmod: can't insert '/lib/modules/etxhci-hcd.ko': No such file or directory
Insert net driver(Mindspeed only)...
Starting /usr/syno/bin/synocfgen...
/usr/syno/bin/synocfgen returns 0
Insert synorbd kernel module
Insert synofsbd kernel module
Insert sha256 kernel module
All disk ready or timeout execeed
Assemble args:
Exit on error [12] No raid status in path /sys/block/md0/md/array_state, go to junior mode...
Thu Apr 21 00:36:54 UTC 2022
none /sys/kernel/debug debugfs rw,relatime 0 0

 

 

 

Link to comment
Share on other sites

On 4/19/2022 at 8:22 PM, Peter Suh said:

 

I've always wondered the root cause of that 55% of the problems that often occur.

If you have a chance, prepare a Telnet connection or ttyd connection

SynologyNAS> tail /var/log/*rc*

Why don't we prepare to monitor the flow of the log and watch when that 55% situation appears.

 

Thanks @Peter Suh for the suggestion.

 

The 10GB disk is virtual disk 1 in VMM with the tinycore-redpill.v0.4.6-img

The 11GB disk is virtual disk 2 in VMM as the empty drive

 

Right after booting and before attempt to install pat file:

DiskStation> tail /var/log/*rc*
get disk fail


========== END OF DUMP OF ALL PARTITIONS DETECTED ==========
Ran "boot-wait.sh" for thethorgroup.boot-wait->on_boot - exit=1
ERROR: Some of the scripts failed! See above for any with exit != 0
:: Executing "on_boot" custom scripts ... [  OK  ]
Exit on error [99] rp ext init exec failure...
Thu Apr 21 04:07:19 UTC 2022
none /sys/kernel/debug debugfs rw,relatime 0 0
DiskStation> fdisk -l
Disk /dev/sda: 10 GB, 10737418240 bytes, 20971520 sectors
1305 cylinders, 255 heads, 63 sectors/track
Units: sectors of 1 * 512 = 512 bytes

Device  Boot StartCHS    EndCHS        StartLBA     EndLBA    Sectors  Size Id Type
/dev/sda1 *  0,32,33     6,62,56           2048     100351      98304 48.0M 83 Linux
/dev/sda2    6,62,57     15,205,62       100352     253951     153600 75.0M 83 Linux
/dev/sda3    15,205,63   130,138,8       253952    2097151    1843200  900M 83 Linux
Disk /dev/sdb: 11 GB, 11811160064 bytes, 23068672 sectors
1435 cylinders, 255 heads, 63 sectors/track
Units: sectors of 1 * 512 = 512 bytes

Disk /dev/sdb doesn't contain a valid partition table

 

After attempting to install pat file, letting it wipe disk, and getting the 55% error:

DiskStation> tail /var/log/*rc*
get disk fail


========== END OF DUMP OF ALL PARTITIONS DETECTED ==========
Ran "boot-wait.sh" for thethorgroup.boot-wait->on_boot - exit=1
ERROR: Some of the scripts failed! See above for any with exit != 0
:: Executing "on_boot" custom scripts ... [  OK  ]
Exit on error [99] rp ext init exec failure...
Thu Apr 21 04:07:19 UTC 2022
none /sys/kernel/debug debugfs rw,relatime 0 0
DiskStation> fdisk -l
Disk /dev/sda: 10 GB, 10737418240 bytes, 20971520 sectors
18859 cylinders, 139 heads, 8 sectors/track
Units: sectors of 1 * 512 = 512 bytes

Device  Boot StartCHS    EndCHS        StartLBA     EndLBA    Sectors  Size Id Type
/dev/sda3    15,205,63   130,138,8       253952    2097151    1843200  900M 83 Linux
Disk /dev/sdb: 11 GB, 11811160064 bytes, 23068672 sectors
1435 cylinders, 255 heads, 63 sectors/track
Units: sectors of 1 * 512 = 512 bytes

Device  Boot StartCHS    EndCHS        StartLBA     EndLBA    Sectors  Size Id Type
/dev/sdb1    0,32,33     310,37,47         2048    4982527    4980480 2431M fd Linux raid autodetect
/dev/sdb2    310,37,48   571,58,63      4982528    9176831    4194304 2048M fd Linux raid autodetect
Disk /dev/md0: 2431 MB, 2549940224 bytes, 4980352 sectors
622544 cylinders, 2 heads, 4 sectors/track
Units: sectors of 1 * 512 = 512 bytes

Disk /dev/md0 doesn't contain a valid partition table
Disk /dev/md1: 2047 MB, 2147418112 bytes, 4194176 sectors
524272 cylinders, 2 heads, 4 sectors/track
Units: sectors of 1 * 512 = 512 bytes

Disk /dev/md1 doesn't contain a valid partition table

 

Thanks for any insight!

 

Link to comment
Share on other sites

2 hours ago, yaleforks said:

Trying to install 7.1 DS920+ loading .pat file from Synology fails at 55-56 percent. Redpill 0.4.6 using ./m.sh script from Peter Suh

 

If there is no fail message at 55% level, the post below posted a review that the installation was successful after waiting for more than 15 minutes.


It doesn't seem to be a constant situation, but I don't know the exact cause.

 

 

Link to comment
Share on other sites

1 hour ago, mxmx said:

 

Thanks @Peter Suh for the suggestion.

 

The 10GB disk is virtual disk 1 in VMM with the tinycore-redpill.v0.4.6-img

The 11GB disk is virtual disk 2 in VMM as the empty drive

 

Right after booting and before attempt to install pat file:







DiskStation> tail /var/log/*rc*
get disk fail


========== END OF DUMP OF ALL PARTITIONS DETECTED ==========
Ran "boot-wait.sh" for thethorgroup.boot-wait->on_boot - exit=1
ERROR: Some of the scripts failed! See above for any with exit != 0
:: Executing "on_boot" custom scripts ... [  OK  ]
Exit on error [99] rp ext init exec failure...
Thu Apr 21 04:07:19 UTC 2022
none /sys/kernel/debug debugfs rw,relatime 0 0
DiskStation> fdisk -l
Disk /dev/sda: 10 GB, 10737418240 bytes, 20971520 sectors
1305 cylinders, 255 heads, 63 sectors/track
Units: sectors of 1 * 512 = 512 bytes

Device  Boot StartCHS    EndCHS        StartLBA     EndLBA    Sectors  Size Id Type
/dev/sda1 *  0,32,33     6,62,56           2048     100351      98304 48.0M 83 Linux
/dev/sda2    6,62,57     15,205,62       100352     253951     153600 75.0M 83 Linux
/dev/sda3    15,205,63   130,138,8       253952    2097151    1843200  900M 83 Linux
Disk /dev/sdb: 11 GB, 11811160064 bytes, 23068672 sectors
1435 cylinders, 255 heads, 63 sectors/track
Units: sectors of 1 * 512 = 512 bytes

Disk /dev/sdb doesn't contain a valid partition table

 

After attempting to install pat file, letting it wipe disk, and getting the 55% error:







DiskStation> tail /var/log/*rc*
get disk fail


========== END OF DUMP OF ALL PARTITIONS DETECTED ==========
Ran "boot-wait.sh" for thethorgroup.boot-wait->on_boot - exit=1
ERROR: Some of the scripts failed! See above for any with exit != 0
:: Executing "on_boot" custom scripts ... [  OK  ]
Exit on error [99] rp ext init exec failure...
Thu Apr 21 04:07:19 UTC 2022
none /sys/kernel/debug debugfs rw,relatime 0 0
DiskStation> fdisk -l
Disk /dev/sda: 10 GB, 10737418240 bytes, 20971520 sectors
18859 cylinders, 139 heads, 8 sectors/track
Units: sectors of 1 * 512 = 512 bytes

Device  Boot StartCHS    EndCHS        StartLBA     EndLBA    Sectors  Size Id Type
/dev/sda3    15,205,63   130,138,8       253952    2097151    1843200  900M 83 Linux
Disk /dev/sdb: 11 GB, 11811160064 bytes, 23068672 sectors
1435 cylinders, 255 heads, 63 sectors/track
Units: sectors of 1 * 512 = 512 bytes

Device  Boot StartCHS    EndCHS        StartLBA     EndLBA    Sectors  Size Id Type
/dev/sdb1    0,32,33     310,37,47         2048    4982527    4980480 2431M fd Linux raid autodetect
/dev/sdb2    310,37,48   571,58,63      4982528    9176831    4194304 2048M fd Linux raid autodetect
Disk /dev/md0: 2431 MB, 2549940224 bytes, 4980352 sectors
622544 cylinders, 2 heads, 4 sectors/track
Units: sectors of 1 * 512 = 512 bytes

Disk /dev/md0 doesn't contain a valid partition table
Disk /dev/md1: 2047 MB, 2147418112 bytes, 4194176 sectors
524272 cylinders, 2 heads, 4 sectors/track
Units: sectors of 1 * 512 = 512 bytes

Disk /dev/md1 doesn't contain a valid partition table

 

Thanks for any insight!

 

 

I can't find any mention of the platform you are trying to install, is it DVA3221?

I think Pocopico can tell you more accurately whether boot-wait ext is associated with a 55% error.

Recently, DS920+ and boot-wait timeout problems were discovered, so I got help to fix the RC script of Pocopico.

There are many versions of boot-wait ext

In my case, pocopico's redfill-boot-wait ext is automatically used in bare metal.

The log indicates that thethorgroup.boot-wait is the initial version with a bug
Why don't you change ext into Pocopico's inside the VM?

 

To replace ext manually, add the manual option at the end of the build as shown below.

 

./rploader.sh ext <your platform> add https://github.com/pocipico/redpill-ext/blob/master/redpill-boot-wait/rpext-index.json

 

./rploader.sh build <your platform> manual


Instead, you should add all exts that you need, not just boot-wait.

--------------------------------------------------------------------

 

This is my normal boot-wait log.

 

Running "boot-wait.sh" for redpill-boot-wait->on_boot

Still waiting for boot device (waited 1 of 30 seconds)

Still waiting for boot device (waited 2 of 30 seconds)

Still waiting for boot device (waited 3 of 30 seconds)

Still waiting for boot device (waited 4 of 30 seconds)

Still waiting for boot device (waited 5 of 30 seconds)

Still waiting for boot device (waited 6 of 30 seconds)

Confirmed a valid-looking /dev/synoboot device

Ran "boot-wait.sh" for redpill-boot-wait->on_boot - exit=0

 

Edited by Peter Suh
Link to comment
Share on other sites

33 minutes ago, Peter Suh said:

I think Pocopico can tell you more accurately whether boot-wait ext is associated with a 55% error.

Recently, DS920+ and boot-wait timeout problems were discovered, so I got help to fix the RC script of Pocopico.

There are many versions of boot-wait ext


it is not just a boot-wait, the installation just quite because of a error message “the file is probably corrupted..” and than you can’t do anything anymore. 
 

I guess the problem is related to the fact that the disks are wiped and somehow it losses connection with the bootlader. 
I’m having the same problem with redpill but the Jun loader works just fine installing DSM 6.2. 
 

So my guess is that if the bootloader partition could be protected against wiping that it should work, just my simple thoughts..

 

Installing on VMM 

Link to comment
Share on other sites

with DS918-7.1, find these in /var/log/messages, is normal or something wrong with SN/MAC etc

 

2022-04-21T14:20:44+08:00 HomeDS synoame-bin-check-license[5877]: boot/boot_lock.c(149): failed to open /proc/sys/kernel/syno_install_flag
2022-04-21T14:20:44+08:00 HomeDS synoame-bin-check-license[5877]: boot/boot_lock.c(214): failed to mkdir.
2022-04-21T14:20:44+08:00 HomeDS synoame-bin-check-license[5877]: boot/boot_lock.c(182): failed to open /proc/sys/kernel/syno_install_flag
2022-04-21T14:20:44+08:00 HomeDS synoame-bin-check-license[5877]: utils.cpp:18 init fail
2022-04-21T14:20:44+08:00 HomeDS synoame-bin-check-license[5877]: license_manager.cpp:34 Failed to get "uuid" from "SLGetUUID()"
2022-04-21T14:20:44+08:00 HomeDS synoame-bin-check-license[5877]: check-license.cpp:9 Failed to create "LicenseManager"

Link to comment
Share on other sites

1 hour ago, Peter Suh said:

 

I can't find any mention of the platform you are trying to install, is it DVA3221?

 


I’m using a HP Microserver Gen8, bare metal install with DS3622xs+ 7.0.1. The logs are from VMM install with DS3615xs 7.0.1, but I’ve tried using DS3622xs+ with same results. 

Link to comment
Share on other sites

12 hours ago, Bobbenoster said:

update more... after reboot plugged in all the drives again... sataportmap back to 6, hotplug 1... the 2nd drive is now back... the 3rd drive shows up in slot 5 and is flagged as critical... now this drive has zero bad sectors... has the lowest number of powered on hours... comes back with a clean smart test... drive 1 on the other hand has 336 bad sectors yet is marked as healthy, hours also slightly higher than drive 3 aka 5.

 

could this mean that something in redpill is mixing up the smart test results?

my story better.. i had old USB boot flashdrive in, the initram on the old one was overwritten during the /mnt/sdb3 mess consisting of dozens of attempts to make a build without error. Fixed that, DSM7 didn't show up and no connection.

Later noticed (LOL) my storage isn't supported that's why DSM7 didn't boot, probably checking pci (I wouldn't mind to boot without RAID tho).

I added the drivers from Jun loader to CPIO, which was the easiest part of the process, and only then DSM7 showed up via NIC.

Also was chaging Sataportmap 41 to 1 hoping to isolate RAID temporarily, without realizing i shifted the second controller to be the first one. So another installation (which always ends in success and then asks for another installation) got 1 member of RAID overwritten instead of SSD, and now getting "SATA port errors 2,3,4" and no loader works.

Anyways, this can't be fixed even with original Syno unit I wanted to buy today just to try to recover the mess, i will need to do it myself :) If I hide SSD and clean RAID member1, might rebuild the RAID:)

Link to comment
Share on other sites

1 hour ago, Bobwin said:


it is not just a boot-wait, the installation just quite because of a error message “the file is probably corrupted..” and than you can’t do anything anymore. 
 

I guess the problem is related to the fact that the disks are wiped and somehow it losses connection with the bootlader. 
I’m having the same problem with redpill but the Jun loader works just fine installing DSM 6.2. 
 

So my guess is that if the bootloader partition could be protected against wiping that it should work, just my simple thoughts..

 

Installing on VMM 

this issue has been discussed here before, right?

 

https://githubhot.com/repo/RedPill-TTG/redpill-load/issues/20

Link to comment
Share on other sites

16 minutes ago, nadiva said:

my story better.. i had old USB boot flashdrive in, the initram on the old one was overwritten during the /mnt/sdb3 mess consisting of dozens of attempts to make a build without error. Fixed that, DSM7 didn't show up and no connection.

Later noticed (LOL) my storage isn't supported that's why DSM7 didn't boot, probably checking pci (I wouldn't mind to boot without RAID tho).

I added the drivers from Jun loader to CPIO, which was the easiest part of the process, and only then DSM7 showed up via NIC.

Also was chaging Sataportmap 41 to 1 hoping to isolate RAID temporarily, without realizing i shifted the second controller to be the first one. So another installation (which always ends in success and then asks for another installation) got 1 member of RAID overwritten instead of SSD, and now getting "SATA port errors 2,3,4" and no loader works.

Anyways, this can't be fixed even with original Syno unit I wanted to buy today just to try to recover the mess, i will need to do it myself :) If I hide SSD and clean RAID member1, might rebuild the RAID:)

If you are simply trying to recover your data? I think open media vault can read the synology disks, at least that will give you the ability to recover your disks. I think that what your trying to do. Google open media vault, and search here, you will find it mentioned that OMV can read the synology drives without data wipe.

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...