IG-88

1st partition will still not work with win10 but you can edit the 1st partition that way (usb -> image-file -> osfmount -> modded image file -> usb)

the systems all share a installation base and a lot of things are switched on or off by software 3615/17 are sas aware systems, when switching this off and comparing with synoinfo.conf of units supporting DX51x then it might be possible i'd suggest inspection the boot process in that direction rd.gz contains "linuxrc.syno" you might start from there and see how different units are handled by variables that are set or not set, like "SupportSAS" there must be a way how "chaper" units (only using ahci) handle sata multiplex with the DX51x units, i guess multiplexing is active but limited to units on the esata port giving the right answer (like DX51x units)

for testing just unpack and repack something that is working to see if its still working after it what loader, extra.lzma, and pat file are you using? yes we had some already, also i can can test the driver in question here (tg3.ko) with a old HP desktop that also comes with onboard broadcom nic

do,, the drivers are part of the 918+ already thats usually a problem with the vid/pid in grub.cfg (to boot the loader and find it in network every value there works but when installing it needs to be right) https://xpenology.com/forum/topic/7973-tutorial-installmigrate-dsm-52-to-61x-juns-loader/

Realtek 8111H, no direct support from DSM itself (no native driver), but its in the driver package that comes with the loader as you use the original state of the loader with the extra driver for realtek as it comes from jun you should use "DSM_DS3617xs_23739.pat" (nothing newer for now) and test with that its normal that there is no further message on the screen, synology switches the output to serial port you need to search for it in you network, you can download the synology assistant form synology or you can look in your dhcp server (often internet router) the start of the loader itself does not depend on the vid/pid values in the grub.cfg (that gets important when installing the system to disk) you should find the booted loader in network to continue installing (user lan cable connection, dsm does not support wifi) you can also use 918+ (loader 1.04b) with your cpu and on my new system (B360 chipset, coffeelake cpu) the 3615/17 loader did not start the right way seemed to stop when unpacking the kernel (even no output on serial port terminal) if the 3617 loader does not show up you should try the 918+ loader (just for test network connect you dont need to configure grub.cfg, just take the loader as it comes and see if you find it in network, if that works you can start doing the grub.cfg and install, also start with v23739.for 918+)

i will send you a link for a new 918+ test version, would be interested to know if the aquantia driver is working (i can't test this here) btw. nvme needs some more then just loading the drivers https://xpenology.com/forum/topic/13342-nvme-cache-support/page/3/#comments

i have seen shudown problems when testing drivers after a driver oops'ed (crashed) when starting check your log of the system start will look like this [Thu Jan 2 17:05:29 2020] BUG: unable to handle kernel paging request at 00000000ffffffff [Thu Jan 2 17:05:29 2020] IP: [<ffffffff81007b22>] dma_set_mask+0x22/0x50 [Thu Jan 2 17:05:29 2020] PGD 138c87067 PUD 0 [Thu Jan 2 17:05:29 2020] Oops: 0002 [#1] SMP [Thu Jan 2 17:05:29 2020] Modules linked in: skge(F+) ipg(F) uio(F) alx(F) atl1c(F) atl1e(F) atl1(F) libphy(F) mii(F) exfat(O) btrfs synoacl_vfs(PO) zlib_deflate hfsplus md4 hmac bnx2x(O) libcrc32c mdio mlx5_core(O) mlx4_en(O) mlx4_core(O) mlx_compat(O) compat(O) qede(O) qed(O) atlantic(O) tn40xx(O) i40e(O) ixgbe(O) be2net(O) igb(O) i2c_algo_bit e1000e(O) dca vxlan fuse vfat fat glue_helper lrw gf128mul ablk_helper arc4 cryptd ecryptfs sha256_generic sha1_generic ecb aes_x86_64 authenc des_generic ansi_cprng cts md5 cbc cpufreq_conservative cpufreq_powersave cpufreq_performance cpufreq_ondemand acpi_cpufreq mperf processor thermal_sys cpufreq_stats freq_table dm_snapshot crc_itu_t crc_ccitt quota_v2 quota_tree psnap p8022 llc sit tunnel4 ip_tunnel ipv6 zram(C) sg etxhci_hcd mpt3sas(F) mpt2sas(O) megaraid_sas(F) ...

if you read the tutorial, there is osfmount used to alter the grub.cfg https://xpenology.com/forum/topic/7973-tutorial-installmigrate-dsm-52-to-61x-juns-loader/ the image for usb has more then one partition in it, 1st contains grub.cfg, 2nd contains extra.lzma and kernel files for dsm win10 was also able to show the 1st parttion until creators update, atm win10 only mount the 2nd partition if you really have to you can read the usb with "Win32DiskImager 1.0" (set the option "read only allocated partitions") into a image file, use osfmount to alter it and then write it again to usb its also possible to use linux to mount and write the data an the usb, its just win10 behaving that way linux has nothing to complain about the file system on the 1st partition

no, i use a 2nd nas for backup imho its important that you can "extract" the disk if the usb electronic fails so it should have a real sata drive in it as the drive will not have much spin time as a nas drive i guess the brand is not that important

they are not telling you how big it is but usually the write speed drops when its filled up so it can be roughly mesured i dint expect it to manageable but never looked for something like that i thought that smr drives where already outlived as there are 16TB pmr disks

this disks usually have a xxGB area with PMR and the rest is SMR, in kind of desktop usage cases the PMR area softens the blow but using it for backup and a huge ammount of samll files (like using it with rsync) might result in lowe performance your ~5 MB/s seem pretty low but it might depend on the backup software and just using rsync might be the worst scenario with the right backup software and incremental backups it might be no problem but if you want it careless then spend a few bugs extra for a smr drive, it not that much you might read this (and there are more articles about that) https://www.storagereview.com/seagate_backup_plus_external_hard_drive_review_8tb

both sound simmilar, ping still possible? whats in the logs around the time in drops services or network?

from the picture i saw from someone else a few days ago it mas mainly synology distributed packages (well or better maintained packages i guess) and they all broke but when reading this https://xpenology.com/forum/topic/21305-file-station-broken-repair-failed-solved/?tab=comments#comment-122092 it seem nothing new or uncommon

i'd say start over, delete vm with all its data/disks read and try again https://xpenology.com/forum/topic/13061-tutorial-install-dsm-62-on-esxi-67/ maybe watch a video or two an youtube

you should step back an read you post again - you have given absolutely no information about what you used whats the hardware (cpu, mainboard, network and storage controller if not onboard) what loader (version number, type) what additional files like *.pat file used to install dsm, any extra.lzma for drivers what tutorial did you use as base what version did you had before trying to reinstall did you read the faq and normal update tutorial here https://xpenology.com/forum/forum/83-faq-start-here/ https://xpenology.com/forum/topic/13333-tutorialreference-6x-loaders-and-platforms/ https://xpenology.com/forum/topic/7973-tutorial-installmigrate-dsm-52-to-61x-juns-loader/

try the search here with "volume crashed" and select AND https://xpenology.com/forum/topic/23235-crashed-raid5-and-volume-missing/?do=findComment&comment=127151 https://xpenology.com/forum/topic/23791-help-i-lost-access-to-~45-tb-of-data/?do=findComment&comment=128834 https://xpenology.com/forum/topic/22719-volume-crashed-but-raid-good/?do=findComment&comment=125743 first thing is a get a glimpse of what is there and gat yourself a look whats the situation and whats ahead of you dont try to repair anything yet, some rush steps cant be undone

no it should only reset the system, the data volume should not be affected you can try a cross update aka migration from 3615 to 3617 and if that is finished then do a 3617 to 3615 migration it should end with a updated (booting) 3615 and hopefully the plugins work or at least will be working after reinstalling them a little more work but still the hope to keep as much as possible from the configuration

yes, the new 918+ version is not out yet and it needs some rework on my text about the drivers, there versions and on how to use it the list and color coding from the older extra.lzma threads are what it should look like

netzwerk realtek 8111E, gleicher wie beim Asus P8H67-I sata mode im bios sollte auf ahci stehen die CPU G2030 is Ivybridge, zu alt für 918+ da ist 4th gen (hasswell) das minimum wirklich aktuells DSM (6.2.2 Update4) geht jetzt auch, in der neuen 0.5 extra.lzma ist ein aktueller realtek treiber mit dabei https://xpenology.com/forum/topic/21663-driver-extension-jun-103b104b-for-dsm622-for-3615xs-3617xs-918/ wenn das Asus P8H67-I noch in migrierbar ist kannst du ja mal versuchen wie in dem link oben beschrieben wieder zu aktivieren (zImage und rd.gz auf dem DSM_DS3617xs_23739.pat und neze extra.lzma auf den stick kopieren und dabei die vorhandenen dateien ersetzen)

ok here is what i found in your image loader is for DS3615xs 6.2 1st partition: grub.cfg set vid=#0457 set pid=#0151 -> thats not the way it was in jun's original, it should be set vid=0x0457 set pid=0x0151 set netif_num=1 -> if using 3 MAC's then it should be set netif_num=3 2nd Partition: extra.lzma and extra2.lzma !!! -> thats only the case with 918+ image date of extra.lzma is 06.10.2019, thats also the date of the 918+ version, the 0.5 for 3615 came out 16.12.2019 you clearly took the wrong extra.lzma, if you use loader 3615 you will have to use the extra.lzma for this version see in the 1st post below in the section for 3615/17 and read that section about how to use it date of zImage and rd.gz is 01.08.2018 dsm 6.2.2 aka 24922 came out 5/2019 so it must be some older kernel, checking the rd.gz results in v23739 you clearly did not follow what i wrote above about copying the new kernel from the pat file and also did not read the 1st post about how to use the extra.lzma

not anymore https://xpenology.com/forum/topic/21663-driver-extension-jun-103b104b-for-dsm622-for-3615xs-3617xs-918/ and a new version for 918+ is on its way

[Thu Jan 2 22:14:43 2020] e1000e: Intel(R) PRO/1000 Network Driver - 3.3.4-NAPI 3.6.0-NAPI in my 0.5 extra.lzma [Thu Jan 2 22:14:43 2020] i40e: Intel(R) 40-10 Gigabit Ethernet Connection Network Driver - version 2.3.6 2.4.10 in my 0.5 extra.lzma [Thu Jan 2 22:14:43 2020] tn40xx: Tehuti Network Driver, 0.3.6.12.3 0.3.6.17.2 in my 0.5 extra.lzma definitely not what it should be you can try to empty /usr/lib/modules/update/ the files there should be rewritten from the extra.lzma on usb when booting if there are still problems please use "Win32DiskImager 1.0" (with option "real only allocated partitions") to read your usb you are using, upload the file somewhere and PM me the link,i will check the loader for kernel and extra.lzma on it

[Thu Jan 2 21:00:51 2020] jme: Unknown symbol pci_disable_link_state (err 0) THAT should not be there, this message will appear when you use the new 6.2.2 kernel and old driver from 6.2.0 [Thu Jan 2 21:00:51 2020] BUG: unable to handle kernel paging request at 00000000ffffffff [Thu Jan 2 21:00:51 2020] IP: [<ffffffff81007b22>] dma_set_mask+0x22/0x50 [Thu Jan 2 21:00:51 2020] PGD 135599067 PUD 0 [Thu Jan 2 21:00:51 2020] Oops: 0002 [#1] SMP [Thu Jan 2 21:00:51 2020] Modules linked in: skge(F+) ipg(F) uio(F) alx(F) atl1c(F) atl1e(F) atl1(F) libphy(F) ok here the driver you want to use crashed, but the source of the problem might be come from above (old extra.lzma) edit: check the zip file you downloaded, the date of the extra.lzma in the zip file should be 16.12.2019 to be the 0.5_test

unraid seems to use qemu if you google for qemu set vid pid you will find things like https://lists.gnu.org/archive/html/qemu-discuss/2015-07/msg00072.html so you should be able to set the vid/pid to the values you already have in the grub.cfg or you can set anything you want and then set the same in grub.cfg

thats normal https://xpenology.com/forum/topic/9394-installation-faq/?do=findComment&comment=81098 a terminal like putty has a scrollback buffer, you can copy from it https://www.linux.com/tutorials/viewing-linux-logs-command-line/ you can also have a windows share and copy the files in question to that shared folder and access the files usually the destination would be somewhere in /volume1, depending in the name you have given your data folder there is also winscp to access files