Jump to content
XPEnology Community

Vaifranz

Member
 View Profile  See their activity

  • Posts

    47

  • Joined

  • Last visited

 Content Type 

Posts posted by Vaifranz

    TinyCore RedPill loader (TCRP) - Development release 0.9

    in Developer Discussion Room

    Posted

    38 minutes ago, Peter Suh said:

     

    Are there any parts where TCRP friend do not work?  

    If you need to change the order, you can mount the bootloader USB in Windows 10 and edit /boot/grub.cfg on the first partition.

    You will find something with set default="3" .

    Change from 3 to 0 .

    Everything works great, I just can't disable Tiny Core Friend on boot after it has done the update, I always have that item selected in the GRUB menu on every boot, even if on the previous boot I selected another one.

    TinyCore RedPill loader (TCRP) - Development release 0.9

    in Developer Discussion Room

    Posted

    1 hour ago, loomes said:

    Why would you do that? TCRPFriend must start first to function. When it comes to an DSM Update Friend detect this and recreate the zImage. When you will boot direct you can remove Friend.

    Thanks for the answer, this method is fine too, but I have not found anything in the forum that would help me in this regard, would you be kind enough to show me how to do it. Thank you

    Aiuto per script ACPID di GitHub per RedPill / DSM 7.x

    in ITALIAN

    Posted

    Ciao, credo tu debba inserirlo nella configurazione iniziale: user_config.json, come estensione, un esempio qui sotto che ho trovato nel forum.

      

    {
  "extra_cmdline": {
    "vid": "0x0951",
    "pid": "0x1603",
    "sn": "XXXXXXXXX",
    "mac1": "XXXXXXX",
    "mac2": "XXXXXXX",
    "netif_num": "2",
    "sata_remap": "24\\>2:25\\>3:26\\>10:27\\>11:28\\>12:29\\>13"
  },
  "synoinfo": {
    "maxdisks": "24",
    "esataportcfg": "0x0000",
    "usbportcfg": "0x0000",
    "internalportcfg": "0xffffff"
  },
  "extensions": [
    "jumkey.acpid2"
  ]
}

     

    alla fine della configurazione è indicata l'estensione che hai menzionato. Spero sia stato utile.

    DSM 7.0.1-42218

    in DSM Updates Reporting

    Posted

    - Outcome of the update: SUCCESSFUL

    - DSM version prior update: NONE

    - Loader version and model: Tinycore img v0.4.5  - DS3615xs v7.0.1-42218 (update 2 automatic)

    - Installation type: BAREMETAL - MB: AsRock Z87 extreme 6 | CPU: Intel Core i5 4670K

    - Using custom extra.lzma: NO

    - Additional comments: Only for test at moment | extra HBA: 1x Marvell 88SE9215 - 1x JMB582 | extra NIC: Intel 82576 - E1G42ET Chip

    Installazione XPEnology

    in ITALIAN

    Posted

    No, la chiavetta USB è indispensabile per fare il boot del sistema, è il punto di partenza di tutto, nel BIOS della scheda madre devi impostare come dispositivo di BOOT proprio quella chiavetta USB, altrimenti non si avvia niente.

    DSM 7.0

    in ITALIAN

    Posted

    Non aggiornate, Xpenology è compatibile, al massimo, con la versione che avete installato, la DSM 6.2.3. L'aggiornamento causa l'inutilizzo del NAS. per le versioni successioni c'è un gruppo su questo forum che ci sta lavorando.

    Problema di riconnessione alla rete e riavvio

    in ITALIAN

    Posted

    Magari hai lo slot un poco sporco, consiglio pulizia con alcol isopropilico, un buon prodotto per la pulizia in elettronica, sia contatti che altro. La uso anche per togliere i residui di pasta termica sulle CPU quando faccio la sostituzione.


    Inviato dal mio iPhone utilizzando Tapatalk

    new sata/ahci cards with more then 4 ports (and no sata multiplexer)

    in Hardware Modding

    Posted · Edited by Vaifranz 

    [   98.256360] md: md2: current auto_remap = 0
[   98.256363] md: requested-resync of RAID array md2
[   98.256366] md: minimum _guaranteed_  speed: 10000 KB/sec/disk.
[   98.256366] md: using maximum available idle IO bandwidth (but not more than 600000 KB/sec) for requested-resync.
[   98.256370] md: using 128k window, over a total of 483564544k.
[  184.817938] ata5.00: exception Emask 0x0 SAct 0x7fffffff SErr 0x0 action 0x6 frozen
[  184.825608] ata5.00: failed command: READ FPDMA QUEUED
[  184.830757] ata5.00: cmd 60/00:00:00:8a:cf/02:00:00:00:00/40 tag 0 ncq 262144 in
                        res 40/00:ff:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[  184.845546] ata5.00: status: { DRDY }
[  184.849222] ata5.00: failed command: READ FPDMA QUEUED
[  184.854373] ata5.00: cmd 60/00:08:00:8c:cf/02:00:00:00:00/40 tag 1 ncq 262144 in
                        res 40/00:00:e0:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[  184.869165] ata5.00: status: { DRDY }
[  184.872839] ata5.00: failed command: READ FPDMA QUEUED
[  184.877994] ata5.00: cmd 60/00:10:00:8e:cf/02:00:00:00:00/40 tag 2 ncq 262144 in
                        res 40/00:00:e0:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[  184.892784] ata5.00: status: { DRDY }
...
[  185.559602] ata5: hard resetting link
[  186.018820] ata5: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[  186.022265] ata5.00: configured for UDMA/100
[  186.022286] ata5.00: device reported invalid CHS sector 0
[  186.022331] ata5: EH complete
[  311.788536] ata5.00: exception Emask 0x0 SAct 0x7ffe0003 SErr 0x0 action 0x6 frozen
[  311.796228] ata5.00: failed command: READ FPDMA QUEUED
[  311.801372] ata5.00: cmd 60/e0:00:88:3a:8e/00:00:01:00:00/40 tag 0 ncq 114688 in
                        res 40/00:ff:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[  311.816151] ata5.00: status: { DRDY }
...
[  312.171072] ata5.00: status: { DRDY }
[  312.174841] ata5: hard resetting link
[  312.634480] ata5: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[  312.637992] ata5.00: configured for UDMA/100
[  312.638002] ata5.00: device reported invalid CHS sector 0
[  312.638034] ata5: EH complete
[  572.892855] ata5.00: exception Emask 0x0 SAct 0x7fffffff SErr 0x0 action 0x6 frozen
[  572.900523] ata5.00: failed command: READ FPDMA QUEUED
[  572.905680] ata5.00: cmd 60/00:00:78:0a:ec/02:00:03:00:00/40 tag 0 ncq 262144 in
                        res 40/00:ff:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[  572.920462] ata5.00: status: { DRDY }
...
[  573.630587] ata5.00: status: { DRDY }
[  573.634262] ata5: hard resetting link
[  574.093716] ata5: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[  574.096662] ata5.00: configured for UDMA/100
[  574.096688] ata5.00: device reported invalid CHS sector 0
[  574.096732] ata5: EH complete
[  668.887853] ata5.00: NCQ disabled due to excessive errors
[  668.887857] ata5.00: exception Emask 0x0 SAct 0x7fffffff SErr 0x0 action 0x6 frozen
[  668.895522] ata5.00: failed command: READ FPDMA QUEUED
[  668.900667] ata5.00: cmd 60/00:00:98:67:53/02:00:04:00:00/40 tag 0 ncq 262144 in
                        res 40/00:ff:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[  668.915449] ata5.00: status: { DRDY }
...
[  669.601057] ata5.00: status: { DRDY }
[  669.604730] ata5.00: failed command: READ FPDMA QUEUED
[  669.609879] ata5.00: cmd 60/00:f0:98:65:53/02:00:04:00:00/40 tag 30 ncq 262144 in
                        res 40/00:00:e0:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[  669.624748] ata5.00: status: { DRDY }
[  669.628425] ata5: hard resetting link
[  670.087717] ata5: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[  670.090796] ata5.00: configured for UDMA/100
[  670.090814] ata5.00: device reported invalid CHS sector 0
[  670.090859] ata5: EH complete
[ 6108.391162] md: md2: requested-resync done.
[ 6108.646861] md: md2: current auto_remap = 0

    I had the same problem with this HDD model: WDC WD60EFAX-68SHWN0, connected to JMB585.  So it's really a problem with Western Digital drives especially the 6Tb WD Red model.

     

    I haven't tried the “libata.force = noncq” modification yet.  What difference does the system have with this change?

    new sata/ahci cards with more then 4 ports (and no sata multiplexer)

    in Hardware Modding

    Posted · Edited by Vaifranz

    I did some tests, my system works fine without the 24 bay case backplane, I will test it with other systems like OMV or Unraid or FreeNAS to understand if the problem is hardware or software.  Here I took a photo of the only code present.

    21B60B19-299B-4F2A-B873-713712BC773C.jpeg

    I searched the net but found nothing about it, the case has this code CSE-S46524.  I hope it will be useful to someone.

    new sata/ahci cards with more then 4 ports (and no sata multiplexer)

    in Hardware Modding

    Posted

    2 hours ago, IG-88 said:
    7 hours ago, Vaifranz said:

    Does the 3615 kernel also have this "flaw"?

    same kernel version as 3617, no reason to assume a change in central ahci code would not be in both

    What I thought, I'm not very well versed in computer systems, just a little passionate.

     

    2 hours ago, IG-88 said:
    7 hours ago, Vaifranz said:

    Could you be more precise and tell me where to insert the command "libata.force = noncq", in the file grub.cfg?

     

    just add it at the end of the line as additional parameter to the others 

    
set common_args_918='syno_hdd_powerup_seq=1 HddHotplug=0 syno_hw_version=DS918+ vender_format_version=2 console=ttyS0,115200n8 withefi elevator=elevator quiet syno_hdd_detect=0 syno_port_thaw=1'

    a space separates entry's and the line is "closed" with the '

    for 3617 its "set common_args_3617="

    Thanks for the tip, I'll try to follow it ... in the meantime I did a test:

     

    run 3617, DSM 6.2.3 RAID 5 on AsRock Z97 extreme 9 without "libata.force = noncq"

     

    Maxtor   STM3320820AS   on Z97 (built-in mobo)

    Maxtor    6L250S0   on Z97 (built-in mobo)

    WDC    WD6400AAKS-22A7B0    on JMB585 (SATA card)

    WDC    WD4000KS-00MNB0    on JMB585 (SATA card)

    WDC    WD3200AAJS-00Z0A0    on JMB585 (SATA card)

    WDC    WD3200AAKS-00YGA0    on JMB585 (SATA card)

    Seagate    ST3320620AS    on ASMEDIA 1061 (built-in mobo)

     

    RAID completed and no disconnections or warnings except this:

      

    [ 5023.397585] perf interrupt took too long (2643 > 5000), lowering kernel.perf_event_max_sample_rate to 50000

     

    I don't know what to think, except that my problem is the backplane

    new sata/ahci cards with more then 4 ports (and no sata multiplexer)

    in Hardware Modding

    Posted 

    [ 3361.874311] ata14: device unplugged sstatus 0x0
[ 3361.874339] ata14.00: exception Emask 0x10 SAct 0x1c0000 SErr 0x9b0000 action 0xe frozen
[ 3361.882474] ata14.00: irq_stat 0x00400000, PHY RDY changed
[ 3361.887987] ata14: SError: { PHYRdyChg PHYInt 10B8B Dispar LinkSeq }
[ 3361.894350] ata14.00: failed command: WRITE FPDMA QUEUED
[ 3361.899726] ata14.00: cmd 61/80:90:e0:fa:01/00:00:08:00:00/40 tag 18 ncq 65536 out
                        res 40/00:98:e0:fd:01/00:00:08:00:00/40 Emask 0x10 (ATA bus error)
[ 3361.915280] ata14.00: status: { DRDY }
[ 3361.919039] ata14.00: failed command: WRITE FPDMA QUEUED
[ 3361.924377] ata14.00: cmd 61/80:98:e0:fd:01/00:00:08:00:00/40 tag 19 ncq 65536 out
                        res 40/00:98:e0:fd:01/00:00:08:00:00/40 Emask 0x10 (ATA bus error)
[ 3361.939927] ata14.00: status: { DRDY }
[ 3361.943669] ata14.00: failed command: WRITE FPDMA QUEUED
[ 3361.948985] ata14.00: cmd 61/80:a0:e0:00:02/00:00:08:00:00/40 tag 20 ncq 65536 out
                        res 40/00:98:e0:fd:01/00:00:08:00:00/40 Emask 0x10 (ATA bus error)
[ 3361.964596] ata14.00: status: { DRDY }
[ 3361.968605] ata14: hard resetting link
[ 3365.801343] ata14: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 3365.902355] ata14.00: configured for UDMA/133
[ 3365.902362] ata14.00: Write Cache is enabled
[ 3365.906628] ata14: EH complete

    This is the message when I launch dmesg and when a disk disconnects

    new sata/ahci cards with more then 4 ports (and no sata multiplexer)

    in Hardware Modding

    Posted

    5 hours ago, IG-88 said:

    did the reconnects happen to all disks on the jmb585?

    The reconnections did not occur on all the disks but only on one or two. Testing, replacing disks that were disconnecting, there were others that had the same problem. The problem occurred with both 918+ and 3615/17. I try again because I have no feedback to post. maybe tonight. Basically it disconnected the disk, or the disks, and could not create the raid, generally I tried on SHR having disks of different sizes, I think that with SHR it works more.

    new sata/ahci cards with more then 4 ports (and no sata multiplexer)

    in Hardware Modding

    Posted

    Thanks for the reply, I also have the 9211-8i card and I confirm that it works great with both 3615 and 3617, unfortunately it does not have the correspondence of the physical slots with those of the XPEnology system, it always puts them in order one after the other  even if they are in different slots.  I can very well keep track of the number of HDDs.  > However I was interested in making a "more performing" system, the JB585 card travels with PCIe 3.0 while LSI 9211-8-i with PCIe 2.0, considering that I have 6Tb drives, when you build a RAID or rebuild time is  long ... and I also wanted to use this card to "tidy up" the numbering of the discs.

    new sata/ahci cards with more then 4 ports (and no sata multiplexer)

    in Hardware Modding

    Posted

    Hi, I am testing the JMB585 card in a ds3617 system but I am having several problems and I don't understand why.
    Fresh installation, DSM 6.2.3 update 3, during the installation phase everything is ok, during the RAID realization phase (both SHR and RAID5 or 6) I find several disconnections of HDD. Tried it on two motherboards, AsRock Z97 extreme9 and AsRock C226WS +, but the problems are the same, HDD WD RED. Any advice I can follow, thanks.

×
×
  • Create New...