quicknick

Members
  • Content count

    152
  • Joined

  • Last visited

  • Days Won

    3

quicknick last won the day on February 25

quicknick had the most liked content!

Community Reputation

23 Excellent

About quicknick

  • Rank
    Advanced Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Loader sollte nicht freigegeben werden, aber Err0r sprang die Waffe. Schön, dass es für dich geklappt hat. Sent from my SM-N950U using Tapatalk
  2. 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
  3. My loader persists across upgrades Sent from my SM-N950U using Tapatalk
  4. It is addressed in my loader. 64 is limit in my loader. Sent from my SM-N950U using Tapatalk
  5. 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.
  6. 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
  7. quicknick

    10Gbe setup - will this work with 6.1?

    Not true. your extra.lzma may still be used. I will not be able to keep up on driver uodates like you have . Ihaven't had time to compare my drivers vs yours, but any user could replace my extra.lzma with yours and still get all the benefits of my loader because my ramdisk is always last. drivers, firmwares and /etc/modules.conf will always remain in extra.lzma. anyone can replace those portions as they see fit. Personally, I wanted to rename to drivers.lzma, but for compatability between Juns loadrr and mine I left as extra.lzma. Sent from my SM-N950U using Tapatalk
  8. What everyone has failed to notice, is that this guy was using xpenoboot 5.2 which uses heavily modded kernel, not the oem one we currently used in 6.x. That being said, I can make this a permanent solution for the few that need it. My loader will be out in a few days and I can certainly add this from the boot menu. What you should know though, is that even with 12+ drives, DSM will only install to the first 12 drives. You can certainly rebuild the software raid to all attached drives, but it is a manual process. My configuration tool, in the next release, allows you to set to 45 drives, custom amount (12-64) or back to default value of 12 drives automatically. Another cheat way to get more drives, is by using RAID cards. instead using HBAs or JBODs on RAID cards, you can do HW raid and just provision virtual drives to DSM. and do basic no protection 1 drive volumes. Depending on your RAID controller, it could be faster than software RAID, and still have prtectection. Sent from my SM-N950U using Tapatalk
  9. quicknick

    10Gbe setup - will this work with 6.1?

    You are correct. It is about money and lock in. Sent from my SM-N950U using Tapatalk
  10. quicknick

    10Gbe setup - will this work with 6.1?

    It all depends on the use case. I deduced that test4321 just needed connection from 2 nodes. if it was different, then switches would bw the way to go. Even with ESXi hosts or kvm hypervisors traffic can communicate between each other because switching happens on the hypervisor even with multiple portgroups. Or you can get really complicate with VMware and do VXLans, but that is going into the weeds. I keep my traffic east-west and everything north of my fws. ie workstations/laptops/wifi , live in a 1 Gbe world. everything fw, ids ips and below is 10Gbe and all virtual. Sent from my SM-N950U using Tapatalk
  11. quicknick

    10Gbe setup - will this work with 6.1?

    just get the brocade twinax cables and do pc to pc. forget getting a switch unless you got money to spend. also don't use cisco twinax cables with the brocade 1020. Sent from my SM-N950U using Tapatalk
  12. quicknick

    10Gbe setup - will this work with 6.1?

    It will be released in my loader slated to be released tomorrow.
  13. quicknick

    10Gbe setup - will this work with 6.1?

    Cheap route: 10Gbe's are the Brocade (QLogic) BR-1020's and it will always be supported by me because it is what I use. Expensive route: Can't go wrong with most Intel cards because they are easily supported, and most already are
  14. quicknick

    10Gbe setup - will this work with 6.1?

    I use the cheapest 10Gbe card on the market (got them for $33 bucks ea) with great success, originally the Brocade BR-1020, which then became QLogic BR-1020, and now belongs to Cavium. I have a driver built for it that works great in XPEnology.
  15. quicknick

    Tutorial: DSM 6.x on Proxmox

    The reason why I recommend using as usb image vs making it a vdisk, because you don't have to waste a sata or scsi port, and disk stays hidden as synoboot and not accessible inside DSM.