snoopy78

Members
  • Content count

    135
  • Joined

  • Last visited

Community Reputation

0 Neutral

About snoopy78

  • Rank
    Advanced Member
  1. 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..
  2. 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.
  3. 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..
  4. 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.
  5. 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...
  6. i'm using an LSI 9300-16i on a baremetal system...everything is working fine on Jun's loader...
  7. Update 9 worked, but needed hard reboot. Baremetal, x9srl-f, lsi 9300-16i,
  8. 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...
  9. 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
  10. 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
  11. 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
  12. 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
  13. 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?
  14. 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?