Leaderboard

Всем привет. Долгое время мучался с кривой загрузкой системы на MB из темы. Вроде нашел решение, описал в основной теме по установке.

Всем доброго здравия, может информация будет полезна пользователям, я вроде разобрался с проблемой xpenology на плате asrock J4105-ITX Проблему описывал в этом топике выше. Переустанавливал, менял диски, все бесполезно, в 90% случаем просто не загружается и ошибка по UART как на скрине из цитируемого сообщения. Заметил особенность, что не загружается только при ПОЛНОЙ нагрузке по HDD, т.е. на MB всего 4 порта и все 4 заняты. Если один диск - загружается отлично. Решение При создании USB-флешки загрузочной, надо указать конфигурацию SATA контроллеров на плате, я указывал всегда 4. На Asrock J4105-ITX 2 порта организованы основным чипом, а два порта внешним чипом ASMedia ASM1061! Система стала устойчиво работать и нормально загружаться, когда в конфигурации grub/grub.cfg поменял set sata_args='SataPortMap=4' на set sata_args='SataPortMap=22' Где 22 - 2 чипа по 2 порта. Всем правильных CRC бэкапов!

Ah okay. Forget that I ever mention my observation regarding Ryzen cpus and old kernels

@Orphée Photo Detection works on my System. Do you have only one Core set for your VM? The divide error i have only with one Core. If yes set more cores, deactivate und reactivate the Person Album.

I have these containers working without problems for 8 days that was my last test changing the loader. Asrock J1900 8 Gb 7.0.1 918+ Docker version is 20.10.3-1239 https://archive.synology.com/download/Package/Docker/20.10.3-1239

Hello, I am on DS918+ Apollolake 7.01 (J3455-ITX - ASRock, with 8 drives) thanks to you ! Everything works perfectly expect poweron : and no access to this tab : Is it the same for you ? Thanks.

Continuation of questions starting from mid-page 37 (forum doesn't allow for more than 50 quotes per post): You cannot change that - that will require rebuilding of the kernel which isn't possible (as syno doesn't share compilable sources of the kernel). You theoretically can use mknod but this causes problems with v7 (synoboot used to be done this way on 918+). Stay tuned: we will figure this out Yeah, Linux and md doesn't care - only the DSM has some hardcoded assumptions for paths which we need to emulate You don't need a real S/N to run it. Some services (e.g. faces detection in photos) need it but rest of the things don't. What's important is not using the same S/N for multiple people because sooner than later they will start blacklisting them. Today's update should make ESXi working. [will be posted on GH after we finish writing all of the posts] Do not use ready-made images. You don't know what's in them nor we can help with those. Additionally, posting them here is a substantial risk as, unlike the generator, full images contain copyrighted materials which cannot be distributed legally. We will not go into details but the RP project started in a different thread... with different repos... by a different author... none of that is accessible anymore. Add 2 and 2 yourself. We only see a one big problem here - an EFI is being added on the side but nobody opens a PR for it. Instead, there are random zips flying around. Nothing against you (your help with docker is amazing!). However, soon we will not be able to help with issues as some of them stem from people running a modified version grabbed from an attachment... Do you have details how you triggered that error? We didn't look into 7.0.1 yet. It should be working with the new release today [will be posted on GH soon after we finish all posts] It does now - today's update adds this. That is perfectly normal when compiling modules against kernel sources which weren't compiled in that directory. In essence, it means that the kernel cannot determine dependencies between multiple modules (which is important for e.g. distributing a driver for Ubuntu, but here it doesn't matter at all). Fixed in today's release - that warning is actually an old GCC artifact but we worked around it with a slightly different syntax. Try the port INSIDE of the case. HPE bios on microserver is strange sometimes. S/N must be unique (can be generated but must be unique); MAC is needed for DHCP. You should not edit the grub config manually. You need to put it as a disk image, not an ISO image. These are quite different - that's one. Second you have a syntax error somewhewre but the forum replaced bunch of characters. You need to post in a code block tag so the forum doesn't replace anything. What CPU do you have? If it just hard-reboots it means the CPU just crashed, which usually means that it doesn't support some instructions. If you dd the raw image (dd if=file.img of=/dev/rdiskX => make sure you sure rdisk and not disk) you don't need to manually modify the partition. Before you do that you should check the disk with diskutil list to get the number and unmount all existing partitions using diskutil unmount (not eject from the Finder). This is actually posted in the research repo. However, we strongly advise against manually tinkering with the rd.gz file - the loader generator can copy files where needed. It's better to compile modules against synology's source published on sourceforge as they modify structs. Building against vanilla kernel sources may have catastrophic consequences, especially if you're trying to build some driver. We're working on a solution for drivers. This is currently what's stopping us from formally calling it a beta Yes.... Intel decided to add a single instruction (MOVBE) to only the Atom line... then a few years later they've added it to the Xeons. Go figure... that's why 918+ requires a newer CPU with MOVBE support. If you search for "MOVBE intel cpu" you will find many topics not related to xpenology as this is a much bigger problem. As for the SN/MAC: the mac needs to match your real ethernet adaptor. As for the S/N you can google "xpenology s/n generator" and there are tools prepared by the community. You need to use a serial console on your hypervisor, login as root:[no password] and check the /var/log/messages - it will say what went wrong somewhere on the bottom. Did you try updating the BIOS? We've seen such errors on Debian on an Asus motherboard and updating the BIOS solved the issue. That is a bug in the DSM itself (JS error on the page...). It happens on a real hardware as well... albeit not always hmmm. However the only broken page is the Info Center => General. Yay! A nice fix We will add this to the main loader generator. These errors are normal. If you look at them just below it the array is mounted. It jus first tries one thing, failes, and then tries another thing and succeeds. You can generate it with the loader generator. Please, do not use premade images. Your vid/pid combination is most likely invalid, or you connected the usb flash drive to a USB3 port. Try doing "dmesg | grep usb_boot_shim" - it will tell you what drives it saw and if any was shimmed as boot disk. Are you sure your RAM is ok? Are you running ECC there? Check the iLO log as well. Try disabling HPET as well. You should define both. DSM is... hacky... in terms of ethernet interfaces. All of them should be accounted for with different MAC addresses. Are you able to connect to the machine using a serial port? Please add them to your user config under extra_cmdline and rebuild the loader image. Correct, this table still applies. This is due to how syno builds their kernels and how Intel artificially limits instruction sets on some CPUs [fun fact, some older Xeons have the MOVBE in the microcode but it's disabled] So what exactly fails with the upgrade? Are you able to recover the log? In order to see any logs you must attach a serial/COM port. Syno kernel doesn't support VGA output (so as soon as the grub passes the control to the kernel nothing is passed to the GPU). If you boot with ttyS0 iLO should be able to access that port. When you log in to the iLO using ssh (use the same credentials as for the web) there's a virtual serial port emulator (vsp command IIRC from memory). Connect to it before booting and you should start seeing messages right after the screen says "Booting the kernel". You can put it in your user_config.json and it should work... how did you get that S/N? Do not use strip on kernel modules - there are many problems with that. Some options will strip e.g. modinfo which will make the module useless for the kernel. Yes, the built-in card was broken only for a short while. 6.2.3 restored the driver. We didn't test if v7 removed it again (hopefully not). If your loader is at /dev/vda1 then something is very wrong... it shouldn't be. It should be at /dev/synobootN. Editing the grub.cfg manually is not (and will not be) supported. VMM doesn't allow for virtual USB drive. You need to use SATA boot. However, if you're using VMM you should probably install the official VDSM image. NC360T is a good and solid card, even outside of the DSM ecosystem. It's a HP product but it's cheap and readily available (even new). We have probably 30+ of these cards in different servers. After you build the loader the correct PAT file will be in the "cache" folder. You don't need to download it manually from syno. We will like to but we don't have permissions to edit old posts Who should we contact on the form regarding that? v7 should be considered a beta (even if syno says it's stable) on any hardware, including that sold by synology. There are nasty bugs in it unrelated to xpenology. That smells like an ancient docker version in the DSM itself... we saw this before and they fixed the issue after like 6-7 months. It may be the case again. Fixed in the new release (bug in memory handling). It's a shame that Intel artificially limited MOVBE instruction to Atoms and then enabled it again only in new Xeons. That's actually the only reason why 918+ doesn't work on older CPUs. Yes, add them as key:value pairs to "extra_cmdline" key in your user_config.json You can't get them - syno didn't publish them yet... the only way to compile modules is to do it with their toolchain sources. -------------------------------------------------------- [to be continued in a next post due to forum limits]