Vaifranz

Okay, but shouldn't it boot up DSM after doing the update? I have Tiny Core Friend on loop. What or where am I wrong?

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.

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

Hello, I am trying to update my system, and with TCRP version 0.9.2.9 with withfriend I was successful, I have only one problem, the system always boots with "Tiny Core Friend", how can I modify the GRUB menu to select the item with USB? Thank you.

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.

Confermo quanto scritto da Aigor, consigliato il passaggio a una versione più aggiornata.

- 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

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.

Great job guys, congratulations! I can help somehow, I installed baremetal DSM 7.0.1-42218 DS3615xs, unstable for kernel panic (return to login page every time), on Supermicro 10XSLH-F with CHIP Intel C226 and CPU Intel Xeon E3-1245 v3.

Se hai la possibilità prova a fare un'istallazione pulita, cioè su un HDD formattato. Se va a buon fine il problema credo sia la tua versione di DSM attualmente installata

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.

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

[ 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?

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. I searched the net but found nothing about it, the case has this code CSE-S46524. I hope it will be useful to someone.

Yes, a great idea, I can also try the system that is installed there without a backplane, so only mobos, disks and HBA cards. I will update you, in the meantime thanks for your time.