primant

Thank you for the help!

I definitely have been editing the /etc.defaults synoinfo.conf file. What I see happening upon editing that and rebooting is the Juno bootloader screen, I cannot connect to the xpenology. I cannot discover it through the app or find.synology.com, then it reboots and resets itself to a default configdmesg.txt I'm including a copy of the DMESG file. System see's all the drives, just ends up resetting itself after the initial configuration and rebooting. I'll add to this: I edit the synoinf.conf files in both /etc and /etc.defaults, save, reboot. System boots to the juno loader. It sits there doing something for a few minutes (during which I cannot access the system through the app or find.syno*.com. It then reboots and falls back to a default config. I can then discover it, re-install it and we're back at square one again.

i've been using Xpenology 3617xs on a Norco 4224 chassis for almost 2 weeks now, learning as I go. Original I did the expand use case editing the max disks, esata, usb and internaldevices with 0 problems. (Edited the synoinfo.conf based on this thread: It's been working as well as I can expect it to the entire time. I powered it off last night for some maintenance and when I powered it on this morning it's not using the settings I had originally set and now it's not keeping the settings I re-enter so it keeps defaulting to 12 total drives usable. I have 24 drives installed plus a ssd connected to the motherboard as a SSD cache. Nothing I do seems to keep the config, upon reboot, the system is not responsive, ends up rebooting and requires installation over and over again. Is there any point in trying to resolve this (I have all my original data on other NAS devices, and had only started copying data to this box? Thank you synoinfo1.conf

loader v1.03b with 6.2.3 release 25426 the drive was listed under available drives but would not allow me to create a volume with it, reporting that message, however it did let me make it an ssd cache drive. It's an Samsung Evo 840 120gb SSD.

I was planning on installing my xpenology on an older homebrew server I originally built for a windows storage array. Love this site, everything everyone's doing here. Creating my xpenology with a samsung 840evo, I couldn't use it as the installation disk as it was marked as "not tested for compatibility". Today while i'm checking everything I pulled up the SSD cache page and of course it let me add it as a cache drive for the array. I'm kind of confused. I mostly get it, but if I used all SSD's for an array would it give the same compatibility message? Introducing myself, i'm Primant. i've been working in the IT arena for 25+ years now, work for one of the big IT firms as a presales architect for the federal space. Happy to be here!