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

Hi. First of all, see if your system is getting an ip. Check your router and see if it assigns an ip address, or use synology assistant. Second, see if your disk are ok, load a linux live distro and check smart info. It is hard to guess why your system is not working. If you have a spare disk drive, disconnect all other and use it to see if your system is working with it. Maybe use that spare disk and a new usb stick to create an arpl loader and install a more recent version of DSM. Merry Xmas.

Merry Xmas to you too.

Hi. From my point of view: Question 1. I would go with jbod. I think you know that raid is not a replacement for backup and raid 5 will wear ssd faster so if you have backups, the chance for one ssd to fail, if they are from a good known brand, it's unlikely. I have a jbod with 2 and 4 tb ssd and it's doing fine. You can also install Petaspace, make storage pools and volume for each ssd and create a shared folder with Petaspace so that all ssd will be like one volume. With Petaspace, all data will be spread across all ssds, like one file on 1st ssd, second file on 2nd and so on. With jbod data is filled till the disk is full, then it moves to the second one. Question 2. You can make any storage pool you need, but be advised, when created, all data stored will be deleted Question 3. exFat is supported on external drives only. Internal you can have either btrfs or ext4. Btrfs is mandatory for virtual machine. Question 4. AFAIK transcoding is available on DS918 only, which is a great platform, you can have as many disk as you like (almost, max is 24, i think) One important aspect is hdd/ssd hibernation, so that drives wont spin/work all the time, check scemd log for errors.

Maybe try with different usb stick and/or different usb port. I have a mb that will boot arpl on all usb ports but couldnt boot dsm on some specific usb ports.

Usually, avoid sata cards with more than one chipset (yours seems to have 88SE9215+JMB583), most likely DSM will see only some of them 2 or maybe 4 because of sata multiplexer. I've tested a 6 port x1 pcie 2.0 card with ASMedia ASM1166 chipset and it works fine.

01:00.0 Ethernet controller [0200]: Qualcomm Atheros AR8131 Gigabit Ethernet [1969:1063] (rev c0) Subsystem: Device [104d:9082] Kernel driver in use: atl1c 02:00.0 Network controller [0280]: Qualcomm Atheros AR9285 Wireless Network Adapter (PCI-Express) [168c:002b] (rev 01) Subsystem: Device [105b:e017] 01:00.0 Ethernet controller [0200]: Qualcomm Atheros AR8131 Gigabit Ethernet [1969:1063] (rev c0) 02:00.0 Network controller [0280]: Qualcomm Atheros AR9285 Wireless Network Adapter (PCI-Express) [168c:002b] (rev 01)

db post

Hi fbelavenuto, Please, can you help with atheros ar8131 addon? I have IP while building the loader for v1000-42218, but no IP after. Thank you very much.

I have an AMD Athlon II X3 450 that runs a DS3617 6.2.3 in Proxmox, so my guess yours should work on ESXI

Still the same. Thank you for your patience @pocopico