Jump to content
XPEnology Community

snoopy78

Member
  • Posts

    188
  • Joined

  • Last visited

  • Days Won

    2

Everything posted by snoopy78

  1. Loader: Jun's Loader v1.04b for DSM 6.2 DSM: DSM DSM 6.2.2-24922 - DS918+ Bare Metal Chassis: Silverstone RM212 2HE Motherboard: Supermicro X10SDV-2C-TP4F SoC RAM: 2x 8GB Kingston HyperX Fury DDR4 HX424C15FB2/8 RAM 8GB Integrated NIC: 2x Gb LAN (Intel I210) Integrated NIC: 2x 10Gb LAN (Intel X552, SoC) HBA: LSI IT Mode flashed DELL PERC H310 HDDs SAS: 3x 10TB Seagate Exos X10 SDD SATA: 1x 120GB Sandisk Ultra (SATA) SDD SATA: 1x 750GB Cruicial MX300 (SATA) working, just had some trouble to activate the 10G ixgbe interfaces
  2. Hello @all, i'm currently using xpenology on several "small" devices (16 drives) (sc836 & dsn-3200 chassis) and one legit DSN-1812+. Currently I'm re-planning my backup strategy and will use in future LTO6 or 7 to do an real backup. After I have the full backup, I would like to migrate all 3 storages into one large system containing 36+ (maybe 48) drives. Then I could "reuse" my current sas3 hba and saß expanders as well as all my CPU's and RAM and HDDs. So my questions would be: - what is the max amount of HDDs supported by xpenology dsm - which chassis with hitswap sas backplane could you recommend? Thank you in advance.. BR Snoopy78
  3. running similar setup as yours... #1 main system X9SRL-F Xeon E5 CPU 32GB Ram 10G NIC SAS3 HBA 17x HDD (9x 8 TB, 6x 4 TB HDDs + 2 SSDs) => DSM 6.0.2-8451 Update 11, runnig stable all Volumes (Raid Groups) are consisting of max 4 HDDs (in case the system/volume fails in this way i can more easy recover it) Most tricky part was to modify the synoinfo.conf to get all HDDs up and running... #2 backup/toy/whatever system X8SIL-F Xeon ? CPU 8GB Ram 10G NIC SAS2 HBA => DSM 6.1.5-15254 12x HDD (mainly 2TB, 3TB and 4 TB HDDs) when you go from scratch (without any data) you can use the latest DSM....it's just tricky too to get the synoinfo.conf correct... so, if you start from scratch, you could jump to the latest version, otherwise i also recommend to stick at 5.x or 6.0.2... from my experience
  4. here a short DMESG output of my baremetal system running DSM 6.0 (previous 5.2) with following HW - SM X9 MoBo - Xeon E5 - 32GB RAM - LSI 9300-16i (16 Port 12G SAS3 HBA) - QLE 10G NIC 0.000000] DMI: Supermicro X9SRL-F/X9SRL-F, BIOS 3.2 01/16/2015 0.042034] smpboot: CPU0: Intel(R) Xeon(R) CPU E5-2603 v2 @ 1.80GHz (fam: 06, model: 3e, stepping: 04 5.556541] megaraid cmm: 2.20.2.7 (Release Date: Sun Jul 16 00:01:03 EST 2006) 5.561392] megaraid: 2.20.5.1 (Release Date: Thu Nov 16 15:32:35 EST 2006) 5.575972] Fusion MPT base driver 3.04.20 5.748373] mpt3sas0: Allocated physical memory: size(16686 kB) 5.748377] mpt3sas0: Current Controller Queue Depth(9979),Max Controller Queue Depth(10240) 5.748378] mpt3sas0: Scatter Gather Elements per IO(128) 5.794182] mpt3sas0: LSISAS3008: FWVersion(11.00.00.00), ChipRevision(0x02), BiosVersion(08.27.00.00) 15.806292] qlcnic 0000:03:00.0: 2048KB memory map 16.284039] qlcnic 0000:03:00.0: Supports FW dump capability 16.284043] qlcnic 0000:03:00.0: Driver v5.2.42, firmware v4.14.26 16.298144] qlcnic: xx:xx:xx:xx:xx:xx: NC523SFP 10Gb 2-port Server Adapter Board Chip rev 0x54 so only your NIC is in question to work..
  5. snoopy78

    DSM 6.1.x Loader

    after an mayor update it usually is overwritten so yes, with a volume 10+ hdd's it will be a pain in the ass... usually u only need to change the values back and then recheck ur volumes...but it'll take some time..and of course there CAN be data loss... that's why all my volumes consist of max. 4 HDDs in Raid 5...it's more epensive..but less complicated.
  6. snoopy78

    DSM 6.1.x Loader

    if you modify your synoinfo.conf you also can have more than the 12 hdd's internally... DSM 6.0.2-8451 Update 9 but also works for DSM 6.1 (tested on my new backup system) just check the forum about how to do so..
  7. snoopy78

    DSM 6.1.x Loader

    i just did a quick test with my current toy baremetal system and got Jun's DS3617xs "DS3617xs 6.1 Jun's Mod V1.02-alpha" working. Had to use "force install" but so far for an alpha it's fine.
  8. i don't use SataPortMap since afaik i only can address 10 devices on each controller (except 1st one with the values 0-9) so in my setup where my 1st onboard controller has 8 sata (where i only use 2 of them) and my lsi has 16 it should be something like 216 but from what i did read it would be recognized as 2 on 1st controller, 1 on 2nd and 6 ont 3rd...
  9. i'm using an LSI 9300-16i on a baremetal system...everything is working fine on Jun's loader...
  10. snoopy78

    DSM 6.1.x Loader

    Update 9 worked, but needed hard reboot. Baremetal, x9srl-f, lsi 9300-16i,
  11. if you don't want to read or work...then don't update...btw...the main difference is clearely stated on PAGE 1 of this threat...and IF you look around the forum jsut a tiny bit you would be able to find a guide/tutorial...
  12. snoopy78

    DSM 6.1.x Loader

    just one question... curtrently i toy around with my new xpe baremetal system and used jun's 1.01 loader it seems everything is fine, but i can't create brtfs volumes....isn't it expected to work in this loader? i tried - single disk with EXT4 ok - single disk with BRTFS NOK - Diskgroup with EXT4 ok - Diskgroup with BRTFS NOK my HBA is a LSI 9301-16i any suggestions? Update.. solved it by complete fresh install of DSM... stick to "new" raid-groups maybe in next DSM version no support of SHR at all anymore...just to "stay" safe
  13. just an other quesion.. on my mobo i have 6 SATA ports, where i only use 2 (SATA3) of them while i use 16 ports on my HBA which is the 2nd controller When reading about "SataPortMap=xxx" then the example "SataPortMap=444" would mean 4 Ports on Controller 1, 4 Ports on Controller 2 and 4 Ports on Controller 3. So in my case i would stupidly write "SataPortMap=216" which acutally should have an different meaning (2x Contrl. 1, 1x Contrl. 2 & 6x Contrl. 3). Is my understanding correct? How would i remap correctly? Thank you & BR
  14. if u try brtfs volumes with version 2.2 it surely will crash... try ext4 or wait for 2.3/2.4 Gesendet von meinem SM-G925F mit Tapatalk
  15. tried this too, but always get a checksum error, any way to solve it? PID & VID are correct and system is installed, however brtfs volume (created under june's loader) is crashed (as expected, since brfs should run wir 2.3 first) additionally i modified my bios, so that my console (COM1) is redirected to SoL (Serial over LAN), i can see in console then the boot up to the point where i choose the options, afterwards it's blank. any suggestions/tips? System: SM X9SRL-F, Xeon E5, 32GB Ram LSI 9300-16i HBA, QLE 10GB NIC, D-Link 10G NIC
  16. some stupid general question.. i use a supermicro motherboard with COM1 + COM2 enabled and remotely access the system via the IPKVM. However the console output is also stopping at the dedicated point, if i disable the com port i'll get the warning that no com is available. Are there any settings i must do to fully get the output again?
  17. snoopy78

    Working DSM 6

    Of course people are going to report back DSM6 can't be (fully?) upgraded yet. And of course they are going to express the wish it could be. I have yet to see anyone being unappreciative of the work of those who made a provisionary DSM 6 available, though. As for 'wait[ing] for an offical XPE version that supports DSM6,' I haven't heard anything from the 'official' team in ages. In fact, ironicially, this very thread has sprung from the deafening silence on their end. A word or two, every once in a while, wouldn't hurt either. so...the official team is getting paid for their contibution/work?...no!...however feel free to donate to them so much, that they can work on the version all day long... they are usually doing this in their spare time....and of course it would be great to have a regular update...but hey...still they're doing this for free and in their spare time.... so as haydibe already told...it's up to you to spend your money on the real synology if you always must have the latest update as soon as it's available.... alternatively...you can set up your own nas os...there are surely many out there which would meet your requirements for me 5.2 is working stable and fine on my main system...and my new system is running on DSM6 but hey...what do i miss in DSM5 against DSM6?
  18. snoopy78

    Working DSM 6

    baremetal is working for me with supermicro x9srl-f mainboard, additional 10G QLogic NIC & additional 10G D-Link DXE-820T and LSI MPT2SAS/MPT3SAS HBA ext4 fs volumes fine, about brtfs you need to read trough this 30 pages
  19. snoopy78

    Working DSM 6

    hi @ all, i just did a quick test on my BAREMETAL system using following image: " (DSM_DS3615xs_7393_boot.img) file posted by Dynax on page 24 " My System is: X9SIL-F + Xeon E5 32 GB RAM LSI SAS 9300-16i QLE 10G Fiber NIC D-Link DXE-820T 10G Copper NIC (connected & active with DHCP) => when i use IPKVM to remotely manage the system the display output always breaks after i choosed "run" or "install" last message i see is the "booting the kernel" (solved by modifying the syslinux file) ==> when using the "run" option the system won't be available at all ==> when using the "install" option i can install the DSM_DS3615xs_7393.pat ===> afterwards i always can access the system when uning the "install" option at boot => updated to last DSM 6.0.1-7393 Update 2 via WebUI = SUCCESS => create volumes using ext4 = SUCCESS => creating volumes using brtfs = UNsuccessfull, always immediately the message volume crashes comes up
  20. if u only modify the /etc/synoinfo.conf. values..it's active immediately...BUT u need to edit the /etc.defaults/synoinfo.conf too...to make them permanent (reboot permanent).... for me (variables for my system) i run this for both files to modify it permanently... " cat synoinfo.conf>synoinfo.conf.bak | sed -i -e 's/internalportcfg="0xfff"/internalportcfg="0x0fffff"/' -e 's/esataportcfg="0xff000"/esataportcfg="0x00000"/' -e 's/usbportcfg="0x300000"/usbportcfg="0x300000"/' -e 's/maxdisks="12"/maxdisks="21"/'synoinfo.conf "
  21. hi trantor, thx for your great work about implementing DXE-820T DualPort 10G Copper NIC. Today i was finally able to play a bit with my system and swapped the fiber against copper nic in combination with my new 10G copper switch (dxs-1210-12TC). (XPE with 32GB Ram, LSI 9300-16i, DXE-820T DXS-1210-12TC <10fiber> dgs-1510-28x server , the upload is stored in RAM of XPE, so this is the pure network troughput)
  22. Thank You....can't wait to get my hands on it..^^
  23. The driver provided in this package is the broadcom bnx2x driver v1.710.39 (2014/06/02). The version of bnx2x driver in XPEnoboot is v1.78.17-0 (2013/04/11). We need to update it to the latest version v1.713.02 (2015/11/02) but broadcom bnx2 and bnx2x are little touchy to update hi Tranto, thank you for your effort and the try...
  24. Hi Trator, could you please compile the driver for the D-Link DXE-820T (dualport 10G copper nic)... i got some cheap so i think about using them.. the official package can be downloaded finalle from here ftp://ftp.dlink.de/dxe/dxe-820t/driver_ ... 160122.zip thx snoopy78
×
×
  • Create New...