satdream

Members
  • Content Count

    77
  • Joined

  • Last visited

  • Days Won

    2

satdream last won the day on September 10 2020

satdream had the most liked content!

Community Reputation

9 Neutral

About satdream

  • Rank
    Regular Member

Recent Profile Visitors

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

  1. - Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.2.3-25426 Update 2 - Loader version and model: JUN'S LOADER v1.03b - DS3617xs - Using custom extra.lzma: Yes - Installation type: BAREMETAL - HP Microserver Gen8 - 16Gb - Intel Xeon E3-1265L v2 - Intel NIC - SAS9202-16E-LSI - QNAP USB 3.0 Ethernet 5GbE - Additional comments: REBOOT REQUIRED
  2. Correct, btw the original CMR ST4000DM005 is no longuer sold, but during SMR introduction by Seagate in Q3/2019 it was different reuse/new ref. with sold model wo/precisions ... Finally the Seagate convention is all Barracua STxxxxDM00x are SMR (but not the STxxxDM009...) and obviously not the Barracuda Pro in STxxxxDM... (not very simple for consummers !) It could be errors etc. in all these synthesis as a lot of information to compile/cross-check, and then I will be please to update if any reported, btw updates are made regularly, then it was more appro
  3. Simply to configure, but not "inside" the gen8 , and it is 6+6 = 12 HDD ... - a low-profile SAS card, a LSI 9202-16E which is a 4x ports SFF8644 = 16x HDD support (fully supported by DSM, but need MPT2 extended drivers) - a 12 (1.5U) or 16 slots (2U ) external rack with SAS/SATA (= 3x or 4x Mini SAS SFF-8087) - and 3x or 4x SFF-8644 > Mini SAS SFF-8087 cables ... in my case I toke a 12 slots external rack, and I also use the 4x gen8 internal HDD slots but connected to the LSI card ... disconnecting the internal HP storage card. Best.
  4. Both shows "vermagic=4.4.180+" if I am correct ... [Edit] both= checked only 918+ and 3617
  5. Hi, and again thanks to IG-88 for the amazing work ... As regularly registered tester for the DSM7.0 preview, I got link to download/test the pre-release on an official Synology 920+ ... it works fine (not a real revolution on GUI, certainly more on the core features especially on rebuild optimisations etc., but not tested obviously). By chance the overall Synology versions are available for the registered preview testers (I will not share, please don't ask), and I tried the 3617XS on an Xpenology baremetal under DSM 6.2.3-25426 Update 2. The update is well
  6. Have a look here (Satdream 3.5" Western Digital) I compiled (and maintain up to date) overall Western Digital HDD, with each certified core product (eg. cad US7SAP) and different branding reuse, the 3.3v pin is Power Disable function of SATA 3.2+ and next release, and only on limited models (and not all in the same capacity !), check the line 3.3v pin issue. Btw, the 3.3v is not affecting most of NAS or microserver etc. as not cabled, but if any issue, alternative to kapton is simply a Molex/SATA supply changer ... Personnaly I have 6x 14TB + 6x 12TB in HP
  7. Au moins sur la hardcopy: Cloud Station Sharesync n'est plus maintenu, il est très avantageusement remplacé par Synology Drive Share Sync qui fonctionne parfaitement pour faire la synchro entre NAS etc. et ce sans besoin d'un ID quickconnect
  8. Hi All, my small contrib here vs. the huge work of @June and other developers with Xpenology (and also the amazing work of @IG-88 with drivers/compiled moduled).. Following long work performed analyzing service manuals, OEM documents, but also mainly the certification requests to authorities (that lists the branding or the sub-version of each physical disk), here is the synthesis of current disks by manufactuer; published also on RedIt and French forums, free to share/reuse keeping the small (c) marking. Hope this help ! Satdream. 3.5" HDD
  9. - Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.2.2-24922 Update 4 - Loader version and model: JUN'S LOADER v1.03b - DS3617xs - Using custom extra.lzma: Yes - Installation type: BAREMETAL - HP Microserver Gen8 - Additional comments: 1) Manual Update 2) Once update finished, the Gen8 start to reboot automatically = switch off quickly (during the "long" boot test process of the Gen8=without issue) 3) Update extra.lzma (simple copy/paste under W10) on the SDCard from which the Gen8 boot 4) Boot Gen8 with updated SDCard
  10. - Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.2.3-25426 - Loader version and model: JUN'S LOADER v1.03b - DS3617xs - Using custom extra.lzma: Yes - Installation type: BAREMETAL - HP Microserver Gen8 - Additional comments: REBOOT REQUIRED -- Manual Update + update /etc.default/synoinfo.conf if specific (eg. more HDDs etc.) The update reseted values, supposed to be restored to - esataportcfg to 0x00000 (instead default 0xff000), - usbportcfg to 0x7C000 (instead default 0x300000) = 5 USB on the Gen8 - internalportcfg to
  11. - Outcome of the update: SUCCESSFUL - DSM version prior update: Disks migration from DS3615xs/6.1.2/loader 1.02b - Loader version and model: JUN'S LOADER v1.03b - DS3617xs - Using custom extra.lzma: YES - Installation type: BAREMETAL - HP Gen8 Micro 12Gb i5 3470T - New install - Dell H310 w/LSI 9211-8i P20 IT Mode + extension Rack of SAS/SATA mixed HDD - Additional comments: Gen8 onboard Dual Broadcom NiC working (no need of additionnal NiC thanks to native drivers from IG-88)
  12. Done tests with fresh install: confirm that IronWolf is working fine in a new fresh install in mixed SAS/SATA environment, but then tried migration and same issue ... Ironwolf support from DSM 6.2.2 24922 update 4 have a bug ... disk is put out of the pool as in default even if status is normal ... Close topic/my contribution, and thanks again to all you sending me suggestions (and private message), and especially to @flyride ! FINISH
  13. Got finally pool working and all status at Normal removing IronWolf, then replacing it, and adding another disk too, after long (long) resync. now config is full working w/DSM 6.2.2-24922 Update 4 ... But IronWolf is really an issue, will made other tests (not with my data, but fake config ) in order to try to understand, but for the moment I have to reconfigure all data accesses etc. Thanks all for support !
  14. Resync finalized with the new WD 12TB, extracted the 10TB IronWolf = all data available ... resync successfull ... But the pool is still failed ... then removed the unused 5TB Toshiba (from the beginning of issues I do not understand why this HDD was status changed to initalized in DSM assuming the Raid manager consider it as Ok in the Raid volume), as DSM asking for a 8TB minimum disk, I plugged a new 8TB Seagate NAS HDD version ... Resync initated, 8h prevision ... for the 1st round ... Rq: the resync duration predication is a bit unprecised, and do not c