djvas335 Posted April 18, 2020 Share #626 Posted April 18, 2020 Actually I got the ideia to try this from a post by alexku44, when he confirmed that older driver works in his setup, so credit for discovering this goes to him. I confirm upgrade success dsm3615xs to 6.2.3 on Microserver GEN 7, GEN8 and GEN10, this is only hardware I have running DSM 4 minutes ago, IG-88 said: yes i don't doubt that but it will not work for everyone (every hardware) and on 918+ there are three types of extra/extra2.lzma and depending on what type used it will it will "influence" the result (3615/17 does not have i915 hardware transcoding and does not rely on i915 firmware) i guess it wont make things worse to try jun's original files - but don't blame me or djvas335 if it does not and i guess it will be back to what you had before when using the extra/extra2 you used before you tried jun's originals (also no guarantees - as usual) one thing is sure, your data are still there, you just cant use them because you might have lost network access or the storage does not work to get all disks into the raid one "safe" solution might be to boot up open media vault from a external (additional) source/disk, that will give you network access to your raid (data) volume - if you need files from there - thats my personal plan "f" if i loose access when dsm does not boot (if your raid is damaged then you are beyond "f") 1 Quote Link to comment Share on other sites More sharing options...
Eduardo Posted April 18, 2020 Share #627 Posted April 18, 2020 18 minutes ago, IG-88 said: one "safe" solution might be to boot up open media vault from a external (additional) source/disk, that will give you network access to your raid (data) volume - if you need files from there - thats my personal plan "f" if i loose access when dsm does not boot (if your raid is damaged then you are beyond "f") Interesting. Should it work when SHR used? Quote Link to comment Share on other sites More sharing options...
IG-88 Posted April 18, 2020 Author Share #628 Posted April 18, 2020 1 minute ago, Eduardo said: Interesting. Should it work when SHR used? i'm not using SHR aka lvm2 (in addition to mdadm) but afaik it shoud work too (SHR is "just" a clever combination of mdadm and lvm2) on purpose I'm using plain mdadm raid6 for my own system - makes recovery easier (if needed, and tbh i did need that once even with 2 redundancy disk - and as it should be i do have a backup too, because raid is not a replacement for backup!!!) mdadm and lvm2 are no rocket science and no exclusives to synology so its possible to recover and use SHR volumes with usual linux look for @flyride posts for help to recover problems with storage (i like to work in that field too in my spare time - but he is much more capable in that field - if you want to learn about that read his threads) 1 Quote Link to comment Share on other sites More sharing options...
alirz1 Posted April 18, 2020 Share #629 Posted April 18, 2020 (edited) - Outcome of the update: FAILED - DSM version prior update: DSM 6.1.7 UPDATE 2 - CURRENT Loader version and model: JUN'S LOADER v1.02b - DS3617xs..... Trying upgrade using 1.03b with new dsm kernel file - Using custom extra.lzma: YES - Installation type: BAREMETAL - Asrock H370m - NIC: 1 x Giga PHY Intel® I219V, 1 x GigaLAN Intel® I211AT - Additional comments: HANGS SHORTLY AFTER BOOTING. NO NETWORK ON ANY NIC, NO KEYBOARD LIGHTS Hi All, So i currently have a intel i3-8100 processor, Asrock H370m motherboard based DS3617xs xpenology system running Junls 1.02b loader with DSM 6.1.7-15284 Update 2 and the extra ramdisk(some version from 2018) Trying to get it to upgrade to 6.2.2 using the 1.0.3b loader and the extra kernel for 6.2.x. However looks like that even without the disks connected, the system is kernel panicing shortly after the 1.03b loader boot. While i havent checked via serial console, if its indeed a kernel panic. But looks like that is the case, as shortly after the boot the keyboard lights go off. I get no network connection etc.... NOTE: i have already upgraded my second xpenology box that has an older/different hardware successfully to 6.2.2 using the steps on page 1 of this thread, So im famialir with the requirements. This is the Asrock board and its specs.. No extra add on adapters/controllers etc... Any ideas? Is it known to be not compatible. https://www.asrock.com/MB/Intel/H370M-ITXac/index.asp#Specification Edited April 18, 2020 by alirz1 Quote Link to comment Share on other sites More sharing options...
IG-88 Posted April 18, 2020 Author Share #630 Posted April 18, 2020 31 minutes ago, Eduardo said: Interesting. Should it work when SHR used? afair yes but its not going to make things worse, you would disconnect all (dsm) disks install ovm onto one separate disk and after its installed you shut down, reconnect all disk (boot from the ovm disk) and you will see if it discovers your (shr) volume (it will not discover the dsm system raid1 partitions - at least it did not as i tested it 2-3 years ago - i'm much more resilient to dsm problems now and i'm not using the "latest" dsm on my "live" system - its still running dsm 6.1 and i'm not "exposing" it to the internet) 1 Quote Link to comment Share on other sites More sharing options...
djvas335 Posted April 19, 2020 Share #631 Posted April 19, 2020 Use 1.03b loader and upgrade directly to DSM 6.2.3, do not use extra.lzma, it's no longer compatible with newer DSM, they reverted their driver support to old version of drivers, so old drivers from original loader work. 14 hours ago, alirz1 said: - Outcome of the update: FAILED - DSM version prior update: DSM 6.1.7 UPDATE 2 - CURRENT Loader version and model: JUN'S LOADER v1.02b - DS3617xs..... Trying upgrade using 1.03b with new dsm kernel file - Using custom extra.lzma: YES - Installation type: BAREMETAL - Asrock H370m - NIC: 1 x Giga PHY Intel® I219V, 1 x GigaLAN Intel® I211AT - Additional comments: HANGS SHORTLY AFTER BOOTING. NO NETWORK ON ANY NIC, NO KEYBOARD LIGHTS Hi All, So i currently have a intel i3-8100 processor, Asrock H370m motherboard based DS3617xs xpenology system running Junls 1.02b loader with DSM 6.1.7-15284 Update 2 and the extra ramdisk(some version from 2018) Trying to get it to upgrade to 6.2.2 using the 1.0.3b loader and the extra kernel for 6.2.x. However looks like that even without the disks connected, the system is kernel panicing shortly after the 1.03b loader boot. While i havent checked via serial console, if its indeed a kernel panic. But looks like that is the case, as shortly after the boot the keyboard lights go off. I get no network connection etc.... NOTE: i have already upgraded my second xpenology box that has an older/different hardware successfully to 6.2.2 using the steps on page 1 of this thread, So im famialir with the requirements. This is the Asrock board and its specs.. No extra add on adapters/controllers etc... Any ideas? Is it known to be not compatible. https://www.asrock.com/MB/Intel/H370M-ITXac/index.asp#Specification Quote Link to comment Share on other sites More sharing options...
darkknigt Posted April 19, 2020 Share #632 Posted April 19, 2020 (edited) 18 hours ago, IG-88 said: just be patient until romorrow, i'm working on it i could send you a link for a test i did that will work for systems using realtek nic and ahci for storage (like most mITX boards with apollo or gemini lake) i guess that can be misleading, for hp microserver you will need broadcom driver (onboard) and "no extra.lzma" can mean you used jun's default extra.lzma (part of the loader) or you deleted the extra.lzma completely from the loader the driver inside jun's default extra.lzma might work with 6.2.3 in some (lot's) cases but its not that universal to copy back jun's extra.lzma, depending on the hardware it might end in success but can also fail there will be cases where storage is not working or where network does not work (i've seen problems here with a igb.ko based network adapter, e1000e and realtek did work) Thanks, but incredibly it has been solved using the original Jun's loader, without changing the extra.lzma Now with Asrock J4105 and DSM 6.2.3 Works Ok with original Jun's loader Edited April 19, 2020 by darkknigt Quote Link to comment Share on other sites More sharing options...
alirz1 Posted April 19, 2020 Share #633 Posted April 19, 2020 2 hours ago, djvas335 said: Use 1.03b loader and upgrade directly to DSM 6.2.3, do not use extra.lzma, it's no longer compatible with newer DSM, they reverted their driver support to old version of drivers, so old drivers from original loader work. I dont know whats going on. But i burnt stock 1.03b loader on a new USB. Updated the grub config. yet, it looks like the box still kernel panics within seconds after booting from the loader. no network, no keyboard lights etc....again, everything works fine with 1.02 loader. Quote Link to comment Share on other sites More sharing options...
djvas335 Posted April 19, 2020 Share #634 Posted April 19, 2020 You probably are using modified loader 1.03 with updated extra.lzma, check the extra.lzma on partition 2 of flash drive, it needs to be about 2mb in size, if its 4.5mb you are using modified loader 1 hour ago, alirz1 said: I dont know whats going on. But i burnt stock 1.03b loader on a new USB. Updated the grub config. yet, it looks like the box still kernel panics within seconds after booting from the loader. no network, no keyboard lights etc....again, everything works fine with 1.02 loader. Quote Link to comment Share on other sites More sharing options...
alirz1 Posted April 19, 2020 Share #635 Posted April 19, 2020 (edited) 15 minutes ago, djvas335 said: You probably are using modified loader 1.03 with updated extra.lzma, check the extra.lzma on partition 2 of flash drive, it needs to be about 2mb in size, if its 4.5mb you are using modified loader No, I burnt stock 1.03b downloaded from MEGA, Juns download link. As a test, I burnt stock 1.02b and box boots fine with one. EDIT. extra.lzma is 1.8MB. Edited April 19, 2020 by alirz1 Quote Link to comment Share on other sites More sharing options...
djvas335 Posted April 19, 2020 Share #636 Posted April 19, 2020 Maybe check your mainboard bios version and update if not latest ? 36 minutes ago, alirz1 said: No, I burnt stock 1.03b downloaded from MEGA, Juns download link. As a test, I burnt stock 1.02b and box boots fine with one. EDIT. extra.lzma is 1.8MB. Quote Link to comment Share on other sites More sharing options...
alirz1 Posted April 19, 2020 Share #637 Posted April 19, 2020 7 minutes ago, djvas335 said: Maybe check your mainboard bios version and update if not latest ? Already on latest Bios. FYI. Bios boot is set to be CSM. Which also allows non UEFI only boot. Quote Link to comment Share on other sites More sharing options...
djvas335 Posted April 20, 2020 Share #638 Posted April 20, 2020 (edited) alirz1 I didn't pay attention at first, you say you run DS3617xs, try DS3615xs, DS3617xs is not quite stable Edited April 20, 2020 by djvas335 Quote Link to comment Share on other sites More sharing options...
djvas335 Posted April 20, 2020 Share #639 Posted April 20, 2020 alirz1 I didn't pay attention at first, you say you run DS3617xs, try DS3615xs, DS3617xs is not quite stable 13 hours ago, alirz1 said: Already on latest Bios. FYI. Bios boot is set to be CSM. Which also allows non UEFI only boot. Quote Link to comment Share on other sites More sharing options...
alirz1 Posted April 20, 2020 Share #640 Posted April 20, 2020 6 hours ago, djvas335 said: alirz1 I didn't pay attention at first, you say you run DS3617xs, try DS3615xs, DS3617xs is not quite stable Thanks i was able to make it boot. Had to set the USb boot mode to legacy and not UEFI. Quote Link to comment Share on other sites More sharing options...
alirz1 Posted April 20, 2020 Share #641 Posted April 20, 2020 Question about LAN drivers. The drivers list/excel sheet on the first page shows both Intel 1219V and 1211 supported for DS3615. Shouldnt both work for DS3617 also? I only have one Nic work for my 3617. Ive seen other posts from other people that have the same board as me(Asrock h370m) complaining about only 1 nic working. Quote Link to comment Share on other sites More sharing options...
smartire Posted April 20, 2020 Share #642 Posted April 20, 2020 Hi everyone, I just got this Dell PowerEdge R420 and I've been trying to install using jun 1.04b for DSM6.2.2 DS918+ since Saturday morning with no success on getting it in the network. Unfortunately, I'm not able to find NIC that would work with jun 1.04b for DSM6.2.2 DS918+ on this device. -Type: BAREMETAL -CPU: Intel Xeon E5-2407 2.20GHz, 10 M Cache, 6.4GT/s QPI, No Turbo , 4C, 80W -RAID Controller: PERC H710 Integrated -RAM: 2 X 8GB 1600 MHZ DDR3-1600/PC3-12800 ECC REGISTERED -Nic: On-Board Dual Port: Broadcom 1 Gigabit Ethernet BCM5720. (I have ordered another Dell Broadcom 57810S Dual Port DA/SFP+ 10Gb that should be delivered today or tomorrow) I've tried several other Nics but the same results, no network connectivity, Intels, and Broadcoms. One dual 1 GB intel I know for sure that worked with DS918+ when I tested it on another server but this one does not. The jun 1.03b / DS3617 detects this Nic BCM5720 and works fine. I appreciate any help or guidance on this project. Quote Link to comment Share on other sites More sharing options...
alirz1 Posted April 20, 2020 Share #643 Posted April 20, 2020 While not a direct answer to your question. But why not stick with 3617? It has better package DSM packages support from what i know.I've been using it for years. Quote Link to comment Share on other sites More sharing options...
smartire Posted April 21, 2020 Share #644 Posted April 21, 2020 13 hours ago, alirz1 said: While not a direct answer to your question. But why not stick with 3617? It has better package DSM packages support from what i know.I've been using it for years. You maybe right about the DS3617, until now I had no luck with DS918, I’m probably missing something since I'm very to this. But thank you Alirz1 for the suggestion. Quote Link to comment Share on other sites More sharing options...
alirz1 Posted April 21, 2020 Share #645 Posted April 21, 2020 (edited) so F me. I did all pre testing in Vm environments and also on my live production baremetal xpenology, with a separate USb and a separate disk drive to make sure my upgrade from jun 1.02b DSM 6.1.7 for my DS3617 would go smooth to 6.2.3 using 1.03b loader. Everything looked normal for days. So i decided to pull the trigger. I upgrade, box boots up fine, goes into dsm 6.2.3, using 1.0.3 stock loader. However i have strange glitches in my gui, my installed packages are not starting. My data shares are not mounting. I can see that in the storage manager the file shares are there, my HDD and volumes are all good!! Its like none of the services are starting!!!! Every page and control panel item i visit and try to change a config. I get error "operation failed. please login to dsm and try again".I thought maybe its related to 2-step verificaiotn somehow, but doesnt look like it. I assume its not easy to downgrade back to 6.1.7 and keep all settings/data now? any ideas if i can fix the system in its current state. Edited April 21, 2020 by alirz1 Quote Link to comment Share on other sites More sharing options...
IG-88 Posted April 22, 2020 Author Share #646 Posted April 22, 2020 On 4/20/2020 at 6:46 PM, smartire said: -CPU: Intel Xeon E5-2407 2.20GHz, 10 M Cache, 6.4GT/s QPI, No Turbo , 4C, 80W sand bridge, so old for 918+, it need 4th gen intel (haswell) as minimum do 3615/17 is your way On 4/20/2020 at 6:46 PM, smartire said: Nic: On-Board Dual Port: Broadcom 1 Gigabit Ethernet BCM5720. (I have ordered another Dell Broadcom 57810S Dual Port DA/SFP+ 10Gb that should be delivered today or tomorrow) both are supported with juns default drivers in 1.03b Quote Link to comment Share on other sites More sharing options...
mysy Posted April 22, 2020 Share #647 Posted April 22, 2020 (edited) On 4/16/2020 at 2:34 AM, IG-88 said: sure? SAS3408 is dev id 00af https://pci-ids.ucw.cz/read/PC/1000 and that supported with the driver in the 0.5 extra.lzma for dsm 6.2.2 3617, mpt3sas.ko (not with 3615 or 918+) only sas38xx/39xx is not supported (at least when it comes to the device list from the driver vendor 1000 devices in 3617 dms 6.2.2 (Reveal hidden contents) pci:v00001000d00000064 pci:v00001000d00000065 pci:v00001000d0000006E pci:v00001000d00000072 pci:v00001000d00000074 pci:v00001000d00000076 pci:v00001000d00000077 pci:v00001000d0000007E pci:v00001000d00000080 pci:v00001000d00000081 pci:v00001000d00000082 pci:v00001000d00000083 pci:v00001000d00000084 pci:v00001000d00000085 pci:v00001000d00000086 pci:v00001000d00000087 pci:v00001000d00000090 pci:v00001000d00000091 pci:v00001000d00000094 pci:v00001000d00000095 pci:v00001000d00000096 pci:v00001000d00000097 pci:v00001000d000000AA pci:v00001000d000000AB pci:v00001000d000000AC pci:v00001000d000000AD pci:v00001000d000000AE pci:v00001000d000000AF pci:v00001000d000000C0 pci:v00001000d000000C1 pci:v00001000d000000C2 pci:v00001000d000000C3 pci:v00001000d000000C4 pci:v00001000d000000C5 pci:v00001000d000000C6 pci:v00001000d000000C7 pci:v00001000d000000C8 pci:v00001000d000000C9 pci:v00001000d000000D0 pci:v00001000d000000D1 pci:v00001000d000000D2 pci:v00001000d000002B0 I try the 0.5 extra with ds3617 loader, system could find the HDD through LSI 9400 HBA card, but other problem is only find 6 of 8 HDD. robert@vDSM6:/$ lspci -nn 0000:00:00.0 Class [0600]: Device [8086:7190] (rev 01) 0000:00:01.0 Class [0604]: Device [8086:7191] (rev 01) 0000:00:07.0 Class [0601]: Device [8086:7110] (rev 08) 0000:00:07.1 Class [0101]: Device [8086:7111] (rev 01) 0000:00:07.3 Class [0680]: Device [8086:7113] (rev 08) 0000:00:07.7 Class [0880]: Device [15ad:0740] (rev 10) 0000:00:0f.0 Class [0300]: Device [15ad:0405] 0000:00:11.0 Class [0604]: Device [15ad:0790] (rev 02) 0000:00:15.0 Class [0604]: Device [15ad:07a0] (rev 01) 0000:00:15.1 Class [0604]: Device [15ad:07a0] (rev 01) 0000:00:15.2 Class [0604]: Device [15ad:07a0] (rev 01) 0000:00:15.3 Class [0604]: Device [15ad:07a0] (rev 01) 0000:00:15.4 Class [0604]: Device [15ad:07a0] (rev 01) 0000:00:15.5 Class [0604]: Device [15ad:07a0] (rev 01) 0000:00:15.6 Class [0604]: Device [15ad:07a0] (rev 01) 0000:00:15.7 Class [0604]: Device [15ad:07a0] (rev 01) 0000:00:16.0 Class [0604]: Device [15ad:07a0] (rev 01) 0000:00:16.1 Class [0604]: Device [15ad:07a0] (rev 01) 0000:00:16.2 Class [0604]: Device [15ad:07a0] (rev 01) 0000:00:16.3 Class [0604]: Device [15ad:07a0] (rev 01) 0000:00:16.4 Class [0604]: Device [15ad:07a0] (rev 01) 0000:00:16.5 Class [0604]: Device [15ad:07a0] (rev 01) 0000:00:16.6 Class [0604]: Device [15ad:07a0] (rev 01) 0000:00:16.7 Class [0604]: Device [15ad:07a0] (rev 01) 0000:00:17.0 Class [0604]: Device [15ad:07a0] (rev 01) 0000:00:17.1 Class [0604]: Device [15ad:07a0] (rev 01) 0000:00:17.2 Class [0604]: Device [15ad:07a0] (rev 01) 0000:00:17.3 Class [0604]: Device [15ad:07a0] (rev 01) 0000:00:17.4 Class [0604]: Device [15ad:07a0] (rev 01) 0000:00:17.5 Class [0604]: Device [15ad:07a0] (rev 01) 0000:00:17.6 Class [0604]: Device [15ad:07a0] (rev 01) 0000:00:17.7 Class [0604]: Device [15ad:07a0] (rev 01) 0000:00:18.0 Class [0604]: Device [15ad:07a0] (rev 01) 0000:00:18.1 Class [0604]: Device [15ad:07a0] (rev 01) 0000:00:18.2 Class [0604]: Device [15ad:07a0] (rev 01) 0000:00:18.3 Class [0604]: Device [15ad:07a0] (rev 01) 0000:00:18.4 Class [0604]: Device [15ad:07a0] (rev 01) 0000:00:18.5 Class [0604]: Device [15ad:07a0] (rev 01) 0000:00:18.6 Class [0604]: Device [15ad:07a0] (rev 01) 0000:00:18.7 Class [0604]: Device [15ad:07a0] (rev 01) 0000:02:01.0 Class [0106]: Device [15ad:07e0] 0000:02:02.0 Class [0c03]: Device [15ad:0774] 0000:02:03.0 Class [0c03]: Device [15ad:0770] 0000:03:00.0 Class [0107]: Device [1000:00af] (rev 01) 0000:0b:00.0 Class [0200]: Device [8086:10d3] 0000:13:00.0 Class [0200]: Device [8086:10ed] (rev 01) 0001:00:02.0 Class [0000]: Device [8086:6f04] (rev ff) 0001:00:02.2 Class [0000]: Device [8086:6f06] (rev ff) 0001:00:03.0 Class [0000]: Device [8086:6f08] (rev ff) 0001:00:03.2 Class [0000]: Device [8086:6f0a] (rev ff) 0001:00:1f.0 Class [0000]: Device [8086:8c54] (rev ff) 0001:00:1f.3 Class [0000]: Device [8086:8c22] (rev ff) 0001:06:00.0 Class [0000]: Device [1b4b:1475] (rev ff) 0001:08:00.0 Class [0000]: Device [1b4b:9235] (rev ff) 0001:09:00.0 Class [0000]: Device [8086:1533] (rev ff) 0001:0c:00.0 Class [0000]: Device [8086:1533] (rev ff) 0001:0d:00.0 Class [0000]: Device [8086:1533] (rev ff) The parameter of bootloader DiskIdxMap=0901 SataPortMap=4 SasIdxMap=0xFF Edited April 22, 2020 by mysy Quote Link to comment Share on other sites More sharing options...
mk13139 Posted April 22, 2020 Share #648 Posted April 22, 2020 On 4/18/2020 at 6:03 PM, IG-88 said: i'm asolute sure about what you did you emptied your updated drivers and firmware on the already installed system (6.2.2->6.2.3 updated) you removed the drivers from the extra.lzma? repacked it and put it on you loader? and added the new firmware files to your (already installed) system and it works for you that would be in the direction what i had in mind but with a more universal touch as it would be interesting to not have to manually clean the driver and firmware (0 byte long files overwriting the files there will do the trick) - but we might not need all this in doing your experiments and questions you also did something else and that was what my question about the driver version was about - you used a 0.5 extra.lzma of mine, that version that worked before 6.2.2 (the kernel config change about "CONFIG_PCIEASPM") and would not have worked with 6.2.2 but it worked with 6.2.3 that implies there is no big change in kernel source 25423 that prevents us from making new drivers, it might be just that synology reverted the change of the kernel config made in 6.2.2 (maybe because they found a better solution like a newer driver) as a quick check i took the original 1.04b loader (jun's extra.lzma made for 6.2.0) added the new kernel (not needed) and it booted up (using the new kernel) and installed dsm 6.2.3 the only mismatch now are jun's newer backported i915 drivers, but with synololgys new own backported driver we dont need it anymore it now seems simple to build a new extra/extra2 for 6.2.3 that will have all drivers working as before, i will just remove i915 drivers, add the new firmware (there is one file different from what jun's i915 driver used) adn recompile drivers the old (pre 6.2.2) way - if there are no new obstacles that can be done by tomorrow Hi IG-88, I'm planning to build a new Xpenology system soon which has an onboard Realtek NIC. If I understand you correctly, you are planning to compile new extra.lzma/extra2 for 6.2.3, as the current v0.5 is only compatible with 6.2.2? Just to make sure, before I put on 6.2.2 with v0.5 driver extension.. 😉 Quote Link to comment Share on other sites More sharing options...
smartire Posted April 22, 2020 Share #649 Posted April 22, 2020 14 hours ago, IG-88 said: sand bridge, so old for 918+, it need 4th gen intel (haswell) as minimum do 3615/17 is your way both are supported with juns default drivers in 1.03b Perfect! DS3617 it's, one more question should I use RAID or HBA/Passthrough? Thank you very much for the information and support. IG-88 You Rock!!!!!! Quote Link to comment Share on other sites More sharing options...
IG-88 Posted April 22, 2020 Author Share #650 Posted April 22, 2020 2 hours ago, smartire said: Perfect! DS3617 it's, one more question should I use RAID or HBA/Passthrough? HBA/Passthrough, dsm is build upon software raid and can't handle hw-raid Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.