blindspot

I'm very sad because of this, he is the only dev that kept dsm 6.2.4 alive and it is also very frustrating thinking that maybe some other dev is involved in this situation. (He did said that someone wanted the source of the drivers he had). It really saddens me. But he deserves a break and hope he will be back someday. Thank you for your amazing work.

Hi. This is great news for me also, because I've tested on some hardware and I wasn't able to figure out why it worked on some and why not on other. I did thought it has something to do with the modules, so please tell me which modules you kept before building the loader. I will retest with what hardware I have at work following your steps. Thank you.

Hi, If you want to rebuild what you had, you should manually install dsm and do not upgrade past 6.2.3-25426 update 3, as it will break your loader. However, I use arpl-i18n which still has options to build loaders with 6.2.4-25556 update 7 for some platforms (DS918/1019, DS1621 etc) but for some reason related to modules they are not working on bare-metal (from my personal experience), only on Proxmox as VM. Good luck arpl-i18n releases

Have you already installed DS918? Post here the results. Maybe is not needed any correction.

AFAIK DeviceTree builds will not keep your order, unless all slots are filled. Give more info.

https://github.com/007revad/Synology_M2_volume

Hi. Boot into a live linux distro, eg ubuntu or fedora and see which drives that distro is detecting. Usually boards with more than one chipset on it eg ASMedia 106x and JMB58x have multiplier sata ports. But you might check on this

If this controller have multiplexed sata ports, DSM wont see all drives connected.

@pocopico Hi. I'm trying to build DS923 v7.1.1-42962 but I have the following error: Rploader Version : 0.9.4.0 .... [-] The extension pocopico.e1000e was found. However, the extension index has no recipe for ds923p_42962 platform. It may not be [-] supported on that platform, or author didn't updated it for that platform yet. You can try running [-] "ext-manager.sh update" to refresh indexes for all extensions manually. Below are the currently known information about [-] the extension stored locally: [#] ========================================== pocopico.e1000e ========================================== [#] Extension name: e1000e [#] Description: Adds Intel(R) PRO/1000 Network Driver Support ... [-] Failed to update recipe for pocopico.e1000e extension for platform ds923p_42962. The script will terminate as you do not [-] have previously downloaded recipe which can be used if download fails. Try again later. If problem [-] persists contact the extension packer for support (displayed below) *** Process will exit *** Same on Rploader Version : 0.9.4.3 after update and fullupgrade For DS920, DS1621, latest version, the build process works fine If I add the ext manualy, it works without error Thanks

@SpiderPOH ./rploader.sh clean rm -rf /mnt/sde3/auxfiles

Hi. You should have the option to make the storage pool read/write, but I think something more serious than one bad block had happened. Each disk has one system partition and one swap partition and they are mirrored across all drives, meaning DSM will start with at least one drive. You could try to clone the disk and then e2fsck it.

@Xeno Log Center app, Logs and select Drives from drop-down list where is General, Connection, File Transfer. Then Clear

My guess is that it will remove the option to create SHR. By default, for models like DS3615/3617/3622, SHR is not among supported RAID types. Does not affect already created raid volumes.

@LestatHi! Don't mess with something that is working fine. Test it first (at least a couple of days) with a spare drive and usb stick then decide if this is what you want. And nobody will tell you that there is zero chance to loose data. Always backup first.

ssh to dsm box and run