quicknick Posted February 28, 2018 Share #51 Posted February 28, 2018 Still planning on releasing a new loader this week? Also, one word of caution on the raid-card front - be very careful which RAID adapter you pick. I had some 3ware adapters that would go completely out to lunch and the only way to recover was a hard power cycle. Then occassionally they would mark drives bad under heavy load even though the drives were perfectly fine... it was the ASIC on the RAID adapter losing its mind.Almost there. Added the changing of maxdrives from the grub bootloader. no longer do you have to figure out binary to hex conversions. Just set your max drives and it does the rest during boot all the way to 64 drives.Just 3 other issues to resolve.Sent from my SM-N950U using Tapatalk 2 Quote Link to comment Share on other sites More sharing options...
quicknick Posted March 2, 2018 Share #52 Posted March 2, 2018 (edited) My loader is now complete. Just updating post and uploading and it will be available late tonight... To tease a little bit on topic.... There are now 3 different ways to set maxdisks in my loader, from grub bootloader, from grub.cfg or from my configtool. Let's see how it is done. NOTE: Setting maxdisks should only be done after DSM has been installed. This is because DSM can only install it's OS on a maximum of 12 disks (usuall the first 12 disks). This is hard set in the proprietary binaries. You could, however, manually create a 64 raid 1 md0 and md1 volume for DSM. Option 1, setting maxdisks from grub bootloader is the best option because it does not require editing grub.cfg before and after change. Setting maxdisks from grub bootloader GNU GRUB version 2.02~beta2-36ubuntu3.7 +----------------------------------------------------------------------------+ |*XPEnology DS3615xs DSM 6.1.x quicknick Baremetal | | XPEnology DS3615xs DSM 6.1.x quicknick Baremetal Reinstall | | XPEnology DS3615xs DSM 6.1.x quicknick Baremetal Force Install | | XPEnology DS3615xs DSM 6.1.x quicknick VMWare/ESXI | | XPEnology Configuration Tool v3.0 | | | | | | | | | | | | | | | +----------------------------------------------------------------------------+ Use the ^ and v keys to select which entry is highlighted. Press enter to boot the selected OS, `e' to edit the commands before booting or `c' for a command-line. Hit e to edit the menu entry which is highlighted. Notice the second line after the title set maxdisk= GNU GRUB version 2.02~beta2-36ubuntu3.7 +----------------------------------------------------------------------------+ |setparams 'XPEnology DS3615xs DSM 6.1.x quicknick Baremetal' | | | | set zImage=zImage | | set maxdisks= | | savedefault | | loadlinux 3615 usb | | loadinitrd | | showtips | | | | | | | | | +----------------------------------------------------------------------------+ Minimum Emacs-like screen editing is supported. TAB lists completions. Press Ctrl-x or F10 to boot, Ctrl-c or F2 for a command-line or ESC to discard edits and return to the GRUB menu. Change this value to any of the following values: 12, 16, 20, 24, 25, 26, 28, 30, 32, 35, 40, 45, 48, 50, 55, 58, 60, 64 When done it will look like set maxdisks=64 Note: With the exception of 64, internal drives added can be the max number listed above. 64 can only have a maximum of 63 drives because the boot drive takes 1 slot. esata is always set to 8, and usb is always set to 4, but for 64, no esata, and only 1 usb. GNU GRUB version 2.02~beta2-36ubuntu3.7 +----------------------------------------------------------------------------+ |setparams 'XPEnology DS3615xs DSM 6.1.x quicknick Baremetal' | | | | set zImage=zImage | | set maxdisks=64 | | savedefault | | loadlinux 3615 usb | | loadinitrd | | showtips | | | | | | | | | +----------------------------------------------------------------------------+ Minimum Emacs-like screen editing is supported. TAB lists completions. Press Ctrl-x or F10 to boot, Ctrl-c or F2 for a command-line or ESC to discard edits and return to the GRUB menu. Then hit Ctrl+X or F10 to boot If you have a serial connection, you will see the following during boot: :: Setting Max Supported Disks in DSM to 64![ BUSY ][ OK ] maxdisks=64 internalportcfg=0x7fffffffffffffff esataportcfg=0x0000000000000000 usbportcfg=0x8000000000000000 Now to see the profit. Log in to DSM and open Storage Manager Setting maxdisks from grub.cfg In your favorite editor edit /grub/grub.cfg on the 1st partition of the loader scroll down and you will see the set maxdrives= variable. ########################################################################################## ### Max Supported Disks ################################################################## ### set maxdisks=48 will mean that XPEnology will now see 48 drives in DSM. ############## ### No changes to /etc.defaults/synoifno.conf needed. Changes are made during boot. ##### ### Acceptable maxdisk values: 12,16,20,24,25,26,28,30,32,35,40,45,48,50,55,58,60,64 ##### ### default value is 12. leave blank for 12 disks. ###################################### ########################################################################################## set maxdrives= Set maxdrives= to any of the values listed in grub.cfg. Then boot up. Setting maxdisks from XPEnology Configuration Tool v3.0 From the grub bootloader select XPEnology Configuration Tool v3.0 GNU GRUB version 2.02~beta2-36ubuntu3.7 +----------------------------------------------------------------------------+ | XPEnology DS3615xs DSM 6.1.x quicknick Baremetal | | XPEnology DS3615xs DSM 6.1.x quicknick Baremetal Reinstall | | XPEnology DS3615xs DSM 6.1.x quicknick Baremetal Force Install | | XPEnology DS3615xs DSM 6.1.x quicknick VMWare/ESXI | |*XPEnology Configuration Tool v3.0 | | | | | | | | | | | | | | | +----------------------------------------------------------------------------+ Use the ^ and v keys to select which entry is highlighted. Press enter to boot the selected OS, `e' to edit the commands before booting or `c' for a command-line. If you have serial you can log directly in, or you can connect via ssh or telnet. Here is what you see prior to logging in: :: Starting sshd service ... sshd service is running with pid 8682 You must copy the text below into ~/xpenology-id_ed25519 in order to connect via ssh. Make sure you chmod 600 ~/xpenology-id_ed25519 to connect execute: ssh -i ~/xpenology-id_ed25519 root@192.168.0.27 ========================== id_rsa ============================== -----BEGIN OPENSSH PRIVATE KEY----- b3BlbnNzaC1rZXktdjEAAAAABG5vbmUAAAAEbm9uZQAAAAAAAAABAAAAMwAAAAtzc2gtZW QyNTUxOQAAACA2/7Ajp8Mg6ipSAGiDJFgKuaOe3i0w2BQmTLNsD1LS8QAAAJiLuF+gi7hf oAAAAAtzc2gtZWQyNTUxOQAAACA2/7Ajp8Mg6ipSAGiDJFgKuaOe3i0w2BQmTLNsD1LS8Q AAAECtVrCe5hbhLaF0JL+0xawXs/TMLbJ/pS7/HIY7k5RT6Db/sCOnwyDqKlIAaIMkWAq5 o57eLTDYFCZMs2wPUtLxAAAAEHJvb3RARGlza1N0YXRpb24BAgMEBQ== -----END OPENSSH PRIVATE KEY----- ================================================================ :: Starting telnet service ... telnetd service is running with pid 8707 =========== Root Password =========== root password for today is: 303-0201 ===================================== ============ Date ============ Fri Mar 2 22:47:59 UTC 2018 ============================== starting pid 8727, tty '': '/sbin/getty 115200 console' Fri Mar 2 22:48:00 2018 DiskStation login: When you login you will see a the XPEnology Configuration Tool Select option 10. to "Set Max Number of Disks" Answer y for yes to change the number of supported disks You now have 3 options, a to set for 64 drives, b to set custom value in HEX, or d to set default values of 12 drives. I select option a 64 drives. And it automatically sets to 64 drives. I select option b custom. If you enter the values listed, it will set to 45 drives; 45 internal, 8 esata, and 2 usb. I select y to accept the values I have inputed. Now you can reboot after settings are set. I know you all can't wait, but should be up soon. Edited March 3, 2018 by quicknick 2 1 Quote Link to comment Share on other sites More sharing options...
SteinerKD Posted March 2, 2018 Author Share #53 Posted March 2, 2018 Yes, but setting the Maxdisk is just part of the problem, you still have the limit of 26 physical disks, or is this being addressed as well? Quote Link to comment Share on other sites More sharing options...
quicknick Posted March 2, 2018 Share #54 Posted March 2, 2018 Yes, but setting the Maxdisk is just part of the problem, you still have the limit of 26 physical disks, or is this being addressed as well?It is addressed in my loader. 64 is limit in my loader.Sent from my SM-N950U using Tapatalk 1 Quote Link to comment Share on other sites More sharing options...
tcs Posted March 4, 2018 Share #55 Posted March 4, 2018 You still planning on posting this weekend? I've actually got a system sitting in wait that I've yet to build a custom bootloader for that needs the drive fix. 1 Quote Link to comment Share on other sites More sharing options...
IG-88 Posted March 4, 2018 Share #56 Posted March 4, 2018 On 3/3/2018 at 12:31 AM, quicknick said: Change this value to any of the following values: 12, 16, 20, 24, 25, 26, 28, 30, 32, 35, 40, 45, 48, 50, 55, 58, 60, 64 whats the reason for those specific numbers? or why not 36, 44, 52 or 56? the original number used in 916+ by synology is 4 (and is set to 12 by jun's patch) On 3/3/2018 at 12:54 AM, quicknick said: On 3/3/2018 at 12:35 AM, SteinerKD said: Yes, but setting the Maxdisk is just part of the problem, you still have the limit of 26 physical disks, or is this being addressed as well? It is addressed in my loader. 64 is limit in my loader. how? whats the difference to setting up values in synoinfo.conf after setting up dsm Quote Link to comment Share on other sites More sharing options...
tcs Posted March 4, 2018 Share #57 Posted March 4, 2018 5 hours ago, IG-88 said: whats the reason for those specific numbers? or why not 36, 44, 52 or 56? the original number used in 916+ by synology is 4 (and is set to 12 by jun's patch) how? whats the difference to setting up values in synoinfo.conf after setting up dsm I would imagine he modifies the swap option that I found. My fix works just fine, the only issue was that it doesn't persist across upgrades because Jun didn't change it in his loader so on upgrade the synoinfo.conf would default to whatever was in the bootloader. Quote Link to comment Share on other sites More sharing options...
quicknick Posted March 4, 2018 Share #58 Posted March 4, 2018 I would imagine he modifies the swap option that I found. My fix works just fine, the only issue was that it doesn't persist across upgrades because Jun didn't change it in his loader so on upgrade the synoinfo.conf would default to whatever was in the bootloader. My loader persists across upgradesSent from my SM-N950U using Tapatalk Quote Link to comment Share on other sites More sharing options...
filippo333 Posted March 4, 2018 Share #59 Posted March 4, 2018 Wow thank you for your excellent work Quicknick! Do you accept donations? Quote Link to comment Share on other sites More sharing options...
George Posted March 5, 2018 Share #60 Posted March 5, 2018 Looks like I might have to re-create my USB's before my XPenology build later this week, after I get my MB replacement. G Quote Link to comment Share on other sites More sharing options...
George Posted March 6, 2018 Share #61 Posted March 6, 2018 (edited) Is this (the increase of max_drives in grub.conf) something that HAS to be done before install, or can it be changed later. Looking at my long term plans will probably push up to 24 drives, G Edited March 6, 2018 by George Quote Link to comment Share on other sites More sharing options...
tcs Posted March 6, 2018 Share #62 Posted March 6, 2018 2 minutes ago, George said: Is this (the increase of max_drives in grub.conf) something that HAS to be done before install, or can it be changed later. Looking at my long term plans will probably push up to 24 drives, G You actually CAN'T do it on initial install. If you have more than 12 drives on initial install you'll run into all sorts of issues. Once you're past that initial install is when you increase the number of drives. Still curious when this is going to get posted. I'm assuming nick ran into issues since he said it was uploading last Friday but I still haven't seen it posted anywhere. Quote Link to comment Share on other sites More sharing options...
George Posted March 6, 2018 Share #63 Posted March 6, 2018 Perfect, the new NAS host is being build (prob Wednesday/Thursday once I get my new MB) with 6 HDD's + 1 M.2SSD at the moment, so that will be day one config, but the entire machine is being configured/planned as 16 HDD's + 4 SSD's. so will look at modifying this after install, would prefer to build it with Nick's boot loader. G Quote Link to comment Share on other sites More sharing options...
George Posted March 6, 2018 Share #64 Posted March 6, 2018 me... still curious... So the default pat file we're all using is mapped to the DS3615xs which is specced as being able to support up to 36 drives via a base unit of 12 drives and 2 disk expanders, each of 12 drives. But when we install DSM using the 3615xs pat file it only shows 12 drives capability? Ye I figure thats because the max drives are currently set to 12 drives, basically need confirmation of my logic.... guessing when you add a disk expander to the real synology ds3615xs it then modifies this max_drives itself at time of picking up there are external disk trays attached ? G Quote Link to comment Share on other sites More sharing options...
tcs Posted March 6, 2018 Share #65 Posted March 6, 2018 10 hours ago, George said: me... still curious... So the default pat file we're all using is mapped to the DS3615xs which is specced as being able to support up to 36 drives via a base unit of 12 drives and 2 disk expanders, each of 12 drives. But when we install DSM using the 3615xs pat file it only shows 12 drives capability? Ye I figure thats because the max drives are currently set to 12 drives, basically need confirmation of my logic.... guessing when you add a disk expander to the real synology ds3615xs it then modifies this max_drives itself at time of picking up there are external disk trays attached ? G Native "external" synology enclosures are treated differently than internal drives, that's why. I'm sure it would be possible to simulate external trays, but it's not really worth the effort. Quote Link to comment Share on other sites More sharing options...
IG-88 Posted March 6, 2018 Share #66 Posted March 6, 2018 technically it is possible to have a build in higher max disk count in the loader in the 916+ loader jun did exactly this and changed from the default 4 to the "usual" 12 so if you extract the extra.lzma, change the jun.patch from 12 to 24 and regenerate the extra.lzma with that change you would have a loader with 24 drives instead of 12 (ok in realty you would need to change more than this one thing, there is also internalportcfg, esataportcfg and usbportcfg) but spare the effort, if quicknick releases his loader its already a build in feature --- a/etc/synoinfo.conf +++ b/etc/synoinfo.conf @@ -135,7 +135,7 @@ enableRCPower="no" maxaccounts="2048" maxgroups="256" maxshares="512" -maxdisks="4" +maxdisks="12" maxprinters="2" maxlogsize="64" Quote Link to comment Share on other sites More sharing options...
quicknick Posted March 6, 2018 Share #67 Posted March 6, 2018 The only delay holding me back is time. I am extremely time limited. DS3615xs loader is 100% complete and post is ready to unlock... Just debating whetether I want to do an all in one loader or manage 3 separate loaders. Hence the delay on release for DS3615xs. If all-in-one, then I would want to add a few more pieces in and do some QC testing. Then anyome can just use set model=DS3615xs or DS3617xs or DS916. All in one is easier to maintain than you'd think. The changes between the core files on my rootfs changes very little between the models. Sent from my SM-N950U using Tapatalk 1 Quote Link to comment Share on other sites More sharing options...
George Posted March 7, 2018 Share #68 Posted March 7, 2018 8 hours ago, quicknick said: The only delay holding me back is time. I am extremely time limited. DS3615xs loader is 100% complete and post is ready to unlock... Just debating whetether I want to do an all in one loader or manage 3 separate loaders. Hence the delay on release for DS3615xs. If all-in-one, then I would want to add a few more pieces in and do some QC testing. Then anyome can just use set model=DS3615xs or DS3617xs or DS916. All in one is easier to maintain than you'd think. The changes between the core files on my rootfs changes very little between the models. Sent from my SM-N950U using Tapatalk being a real noob here, if I was to use the jun loader now, can I simply re-imae my USB with your loader when it becomes available and then boot with that or is there more involved. G Quote Link to comment Share on other sites More sharing options...
George Posted March 7, 2018 Share #69 Posted March 7, 2018 9 hours ago, IG-88 said: technically it is possible to have a build in higher max disk count in the loader in the 916+ loader jun did exactly this and changed from the default 4 to the "usual" 12 so if you extract the extra.lzma, change the jun.patch from 12 to 24 and regenerate the extra.lzma with that change you would have a loader with 24 drives instead of 12 (ok in realty you would need to change more than this one thing, there is also internalportcfg, esataportcfg and usbportcfg) but spare the effort, if quicknick releases his loader its already a build in feature --- a/etc/synoinfo.conf +++ b/etc/synoinfo.conf @@ -135,7 +135,7 @@ enableRCPower="no" maxaccounts="2048" maxgroups="256" maxshares="512" -maxdisks="4" +maxdisks="12" maxprinters="2" maxlogsize="64" I'm not going to dabble this deep into modifying this, to new with this, rather wait for quicknic's loader. Still trying to figure out the differences between a 3615/3617 and 916... other than cpu/memory and number of disks supported natively ??? G Quote Link to comment Share on other sites More sharing options...
Polanskiman Posted March 7, 2018 Share #70 Posted March 7, 2018 10 hours ago, quicknick said: The only delay holding me back is time. I am extremely time limited. DS3615xs loader is 100% complete and post is ready to unlock... Just debating whetether I want to do an all in one loader or manage 3 separate loaders. Hence the delay on release for DS3615xs. If all-in-one, then I would want to add a few more pieces in and do some QC testing. Then anyome can just use set model=DS3615xs or DS3617xs or DS916. All in one is easier to maintain than you'd think. The changes between the core files on my rootfs changes very little between the models. Sent from my SM-N950U using Tapatalk For you obviously all in one would be the better option maintenance wise. The thing is, DSM 6.2 is just around the corner now and I think most users are using DS3615xs anyway. DS3617xs and DS916+ loaders were in fact 'mistakes' or better put, unintentional, by jun but he released them nonetheless. In fact it would be good to actually consider if those models are the best to put out. Aren't there any better ones? This is a honest question. With your time limitation this would mean perhaps several weeks at best before your are able to finally release any loader that satisfies your criteria. By that time, your loader (actually any loader) might be obsolete considering the fact that Synology seems to be signing modules which means, well you know what it means. I suppose you can always work on a all-in-one loader during this time, if time permits but releasing the DS3615xs now at least enables you to have some real life feedback from users. Of course it is all up you. Quote Link to comment Share on other sites More sharing options...
George Posted March 7, 2018 Share #71 Posted March 7, 2018 I'm going to stick my hand up for releasing the DS3615xs loader now... It might be selfish, but thats all i need, and can say we can give feedback now, " the fact that Synology seems to be signing modules which means" this does not good at alllll. G 1 Quote Link to comment Share on other sites More sharing options...
filippo333 Posted March 7, 2018 Share #72 Posted March 7, 2018 3 hours ago, George said: I'm going to stick my hand up for releasing the DS3615xs loader now... It might be selfish, but thats all i need, and can say we can give feedback now, " the fact that Synology seems to be signing modules which means" this does not good at alllll. G Honestly if Synology play that game and make it harder and harder, I'll move to a different OS entirely. Most people with an Xpenology either: a) Can't afford a genuine Synology system. b) Have a more powerful system compared to most of Synology's product range (my case). Synology should be smart and offer their OS at a price for third party systems rather than piss off people that wouldn't/can't use their hardware for various reasons. I'd pay good money for DSM personally. Quote Link to comment Share on other sites More sharing options...
George Posted March 7, 2018 Share #73 Posted March 7, 2018 3 minutes ago, filippo333 said: Honestly if Synology play that game and make it harder and harder, I'll move to a different OS entirely. Most people with an Xpenology either: a) Can't afford a genuine Synology system. b) Have a more powerful system compared to most of Synology's product range (my case). Synology should be smart and offer their OS at a price for third party systems rather than piss off people that wouldn't/can't use their hardware for various reasons. I'd pay good money for DSM personally. Ditto. this is a market/customer base that Synology is throwing away, G Quote Link to comment Share on other sites More sharing options...
George Posted March 7, 2018 Share #74 Posted March 7, 2018 Question, if I build the XPEnology now using the Jun loader. how difficult is it, or is not to switch to Quicknic's loader. Is it simply a case of building a new USB, swapping and rebooting ? G Quote Link to comment Share on other sites More sharing options...
filippo333 Posted March 7, 2018 Share #75 Posted March 7, 2018 Just now, George said: Question, if I build the XPEnology now using the Jun loader. how difficult is it, or is not to switch to Quicknic's loader. Is it simply a case of building a new USB, swapping and rebooting ? G I don't think anyone can answer that question right now since the loader currently isn't available. In theory if you use the same serial number, mac address and Synology hardware model (ie DX 3615xs), you should be able to just import your drives into a new loader. I managed to successfully import drives from my Xpenology box to my genuine DS 1515+ when I had one, without issues. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.