Leaderboard


Popular Content

Showing content with the highest reputation since 06/13/2017 in all areas

  1. 30 points
    Hi! I made a little tool which can help you to get your XPEnology up & running without installing any software. It contains (as portable versions): - Nirsoft's USB device view (helps to identify the VID & PID of your USB boot media) - V2.76 - XPEnology Serial Generator for DS3615XS, DS3617XS and DS916+ (a converted version of the HTML site) - Win32 DiskImager (to write your modified synoboot.img to your USB boot media) - V1.0 (only available in V1.4.1) - OSFMount x64 (to mount the synoboot.img and modifiy it) - V1.5 - Notepad++ (best editor for changing values inside grub.cfg) - V7.5.3 - Synology Assistant (useful tool from Synology to find your XPEnology and install DSM) - V6.2-23733 - TFTP/DHCP portable (a small TFTP, DHCP and Syslog server by Ph. Jounin) - V4.6.2 - MiniTool Partition Wizard 10 (helps assigning already formatted/written USB devices to modify existing grub.cfg) - V10.3 - SoftPerfect Network Scanner - V6.2.1 - USB Image Tool - V1.75 - New: Rufus - V3.3 In the section "Downloads" all links open corresponding websites to download the files. For beginners I added a small HowTo for bare-metal installation. Update New link for download: https://mega.nz/#F!BtViHIJA!uNXJtEtXIWR0LNYUEpBuiA You'll have to run it "As Administrator" because some of these tools (like Win32 DiskImager) need to be executed with higher rights. It's possible that the SmartScreen filter will give you a warning, because the EXE isn't signed. Bug reports and comments are welcome Cheers Current version: V1.4.2 (2018-11-19)
  2. 17 points
    Перед тем как что-то менять в своей работающей системе, настоятельно рекомендуется сделать резервные копии своих особо ценных данных, чтобы потом не жалеть об их безвозвратной потере. Все, что вы творите - это ваш страх и риск, никто не побуждает вас это делать. Самый простой и надежный способ безопасно попробовать - выключить хрень, отключить все диски и загрузочную флешку от действующей системы, взять чистый диск и другую флешку и попробовать установить новую версию загрузчика и системы, если прокатило, то делать уже на действующей системе. 1. Как установить (подготовительные работы описаны для компа с Windows): а) скачать образ загрузчика 1.04b (исходная тема тут), создать каталог в корне диска без символов на кириллице, например, c:/918/ и поместить туда образ загрузчика б) определить VID/PID флешки или картридера в который она вставлена (Панель управления - Диспетчер устройств - Контроллеры USB - Ваша флешка/ридер - Свойства - Сведения - ИД оборудования, нужно для того, чтобы система DSM опознала этот диск и не пыталась устанавливать себя на него, если неправильно определите и пропишите эти параметры, то система будет вылетать по ошибке 13 при установке в) скачать, установить и запустить программу OSFmount, смонтировать Partition 0 (15 Mb) из файла загрузчика, перед монтированием убрать галку Read-only drive г) скачать, установить и запустить программу Akelpad, открыть файл grub/grub.cfg на ранее смонтированном диске, правим, сохраняем: set vid=0xA234 #VID флешки/ридера set pid=0xB678 #PID флешки/ридера set sn=1780PDN123456 #sn set mac1=001132123456 #mac первой сетевой карты set mac1=001132123457 #mac второй сетевой карты, второй и последующий отличаются от первого на +1 в последнем разряде в шестнадцатеричной системе ... set netif_num=2 #количество сетевых карт ... set sata_args='SataPortMap=6' #контроллер sata, значения: 6 - 1 контроллер на 6 портов; 22 - 2 контроллера по 2 порта; 42 - 2 контроллера, первый на 4 порта, второй на 2 и т.п. Где брать sn и mac - ваша головная боль, гугл в помощь, система установится и будет работать с теми, которые изначально прописаны в загрузчике, но с ограничением функционирования некоторых сервисов и модулей, таких как: QC, пуш уведомления, активация кодеков для транскодинга, установка лицензий syno... Но для большинства и без них будет достаточно. На форуме писали, что прокатывало с sn и mac от других реальных моделей syno, но так не пробовал, поэтому утверждать не буду, кто хочет - дерзайте. д) размонтировать диск в OSFmount е) скачать, установить и запустить программу Rufus и записать ранее подготовленный образ на флешку з) вставить флешку в машину, на которой планируете запустить хрень, подключить диски, включить питание ж) отключить брандмауэр в антивирусе, в браузере набрать http://find.synology.com или установить Synology Assistant с сайта syno и найти вновь установленную хрень в вашей сети и) установить DSM установить хрень следуя инструкциям программы установки и приступить к настройке (как это делать здесь не описываю, ибо все ответы есть в базе знаний syno) Для ленивых есть утилита, где собраны основные проги для Windows x64 2. Если хрень не обнаружилась в сети, то скорее всего в загрузчике нет драйверов для ваших сетевых карт и/или для sata контроллеров. a) запустить программу OSFmount, смонтировать Partition 1 (30 Mb) из файла загрузчика, перед монтированием убрать галку Read-only drive б) скачать extra.lzma из этой темы и перезаписать в смонтированном диске в) размонтировать диск и перезаписать образ с добавленными драйверами на флешку г) попробовать запустить и найти хрень в сети, если не получилось, то увы и ах, либо просить, чтобы добавили дрова для ваших устройств в этой теме или самому их добавлять - теория тут 3. Транскодинг (нужны sn и mac от реальной железки) С наибольшей степени вероятности запустиnся на процессорах Intel начиная с 4го поколения (Haswell), но есть нюансы с моделями материнских плат и биосами. Проверяем следующим образом: hardware (hw) транскодинг - в корне системы должен быть каталог /dev/dri с тремя подкаталогами внутри, если его нет, но нет и hw транскодинга, чтобы проверить - ищем каталог в терминале/ssh командой cd /dev/dri. software (sw) транскодинг - должны подняться соответствующие кодеки, проверить можно командой в терминале/ssh cat /usr/syno/etc/codec/activation.conf Если результат такой, то он есть: {"success":true,"activated_codec":["hevc_dec","h264_dec","h264_enc","mpeg4part2_dec","ac3_dec","vc1_dec","vc1_enc","aac_dec","aac_enc","mpeg4part2_enc"],"token":"абракадабра"} Если ничего похожего нет, то нет и транскодинга. P.S. Просьба к админам прибить тему в шапке и дать мне доступ на редактирование первого поста этой темы, буду добавлять по мере поступления вопросов, ибо задолбали оленеводы, которые задают вопросы по установке, во всех подряд темах.
  3. 8 points
    its an old script bug due to my oversight, I am uploading a new version to fix it, hopefully without introduce new bugs
  4. 7 points
    Which DSM version shall I use? This is an oft-repeated question, complicated by the fact that different loaders support different DSM versions AND hardware platforms. In simple terms, DS3615/DS3617 has the widest support for hardware and packages, and DS916/DS918 has support for newer, low-cost CPU's, transcoding and NVMe cache (DS918 only). But the real questions are, what hardware do you have? What hardware do you want to buy in order to support what you want to do? And how does a DSM loader and platform support this? In order to answer, it's useful to understand what hardware is natively supported by DSM. Each DSM version is different as Synology does not need to support many types of hardware, as they build up a specific DSM for each hardware platform they sell. Fortunately, the base Linux kernel has much broader support for hardware than they intend. Most of us guessed at the hardware requirements and made (hopefully) intelligent selections on DSM versus hardware. Some build systems and then are distressed when the hardware isn't fully supported by the DSM platform they choose (sometimes this can be fixed by extra.lzma, and sometimes not). Unfortunately, Synology hardware knowledge is often imperfect, as the main boards are custom designed. Refer to the example below for DS3615 (I hope it will be completed more precisely in the future). DS3615xs Reference Hardware: CPU: Intel Core i3-4130 (Haswell) Chipset: Intel C20x? 4x1Gbe Ethernet: ??? Secondary SATA: ??? 10Gbe OEM: E10G18 (Aquantia AQC107) E10G17 (Mellanox Connect X-2/3/4) E10G15 (Tehuti) With even this information, we can make some good guesses on what hardware might be supported. We certainly can act on the 10Gbe cards since those are well known. Wouldn't it be great if we knew ALL the different drivers that are natively supported? Unfortunately this is a fairly difficult process if you are not a Linux guru (and a bit laborious even if you are). There are "user-reported" hardware compatibility threads out there, but many don't understand that those reports are both DSM version and platform specific. Furthermore, with the way hardware manufacturers reissue hardware with the same name but new PCI device number (such as the Intel PHYs on desktop motherboards), often not enough information is reported to confirm whether a specific piece of hardware is suitable for use. If you aren't sure if your hardware is supported, this post and the complementary DS918 driver guide aim to help you. Download the appropriate Excel spreadsheet to see key driver support in the DS3615 6.1.7 or 6.2.1 Synology custom kernel, and via loadable modules supplied with DSM. Hopefully it will help you select the best DSM platform for your purposes, and possibly inform your hardware purchases. DSM 6.1.7 DS3615 V1.04 2019-Feb-04.xls DSM 6.2.1 DS3615 V1.0 2019-Feb-04.xls
  5. 6 points
    kernel modules/drivers are specifically compiled for a kernel (-versions) and even distributions it's not like windows where you can download a driver somewhere and just put it in so don't take any *.ko file, stick it in and expect it to work if you haven't build the *.ko yourself or don't know exactly where it came from, expect it to fail I'm no expert but as there is no how-to here in the forum - lets start one hopefully other will correct and help refine or take over and rewrite it some steps are made in windows (osfmount) but will also possible in the chroot environment on linux basic knowledge about using a linux console and command-line tools (or midnight commander) is needed, if you never used this you should not start with this how-to, choose something easier or invite someone who is able to help (do a workshop) doing all this from scratch will take at least 1-2 hours, in most cases (re-read, google, try, google, try again, ...) much longer, maybe plan a weekend of text-adventure fun edit: i think it also will do for 6.0.2 and loader 1.01 (not tested), kernel sources are available: https://sourceforge.net/projects/dsgpl/files/Synology%20NAS%20GPL%20Source/8451branch/bromolow-source/linux-3.10.x.txz/download, extra.lzma is a little differently placed (boot.img\image\DS3615xs\) but the steps will be the same 1. building the kernel module (driver) 1.1 what driver/module i need you will have to find out (google) what the name of the driver/module is that your hardware needs or you will have to know where to find the rigt option in the menu-system of the kernel when configuring it example: nForce 630 chipset with RTL8211E, you might expect it to be a realtek driver like rtl*.ko but it's not its "forcedeth.ko" because the RTL8211 is not a fully working PCIe Network Chip in some cases you might be forced to find out by booting a linux distribution and look in /var/log/, use lspci or other tools it also helps if the hardware provider has already compiled packages for specific distributions like redhat, you can look inside these packages for *.ko files you also can look in the .config file of the kernel (more below) with a text editor to find a section where the module is mentioned, this will also give you a hint where to find it in the menu-system when configuring the kernel 1.2 you need the kernel source in the case of synology that seemed sometimes difficult but at the moment there is kernel source for dsm 6.1 https://sourceforge.net/projects/dsgpl/files/Synology%20NAS%20GPL%20Source/ 15047 is the synology build version and tells you about what dsm version it is (15057 = dsm 6.1) and what kernel was used to build the modules, it !!!might!!! change in a later version so always check for what version your bootloader from usb stick is made for (jun 1.02 is for 15047) edit: dsm 6.1.1 has a new build number 15101 but seems to use the same kernel 3.10.102 as 6.1 so it should work with 6.1.1 too as i write this for ds3615xs it's bromolow as a platform, for ds3617xs it's broadwell and ds916+ is braswell (you usually see that name on the update files for a synology system like "synology_broadwell_3617xs.pat") so for ds3615xs we use this: https://sourceforge.net/projects/dsgpl/files/Synology%20NAS%20GPL%20Source/15047branch/bromolow-source/linux-3.10.x.txz/download edit: it looks like as for building the modules there is no difference for kernels modules build for 3615 and 3617 even if https://sourceforge.net/projects/dsgpl/files/Synology%20NAS%20GPL%20Source/15047branch/ has extra kernel sources for bromolow and broadwell, there are all intel x86_64, same might go for the 916+ (not testet yet), at least a evdev.ko build from 3615 kernel source did load without problems in a vm with the 3617 image 1.3 setting up a DSM 6.1 ds3615xs test environment with virtualbox (its free) or whatever works with juns loader look in the forum to find something that works, basics for virtualbox are - mac of the nic (intel pro 1000 desktop) in vm and grub.conf need to be the same - boot controller for jun's image (vmdk with reference to img file) is ide, controller for dsm disks is scsi lsi (!!!) - choose esx server option in grub menu 1.4 installing chroot put in http://packages.synocommunity.com for custom packages and change the setting that beside synology packages trusted ones are also to install install debian-chroot plugin (https://synocommunity.com/package/debian-chroot) from community section (some info's about it: https://github.com/SynoCommunity/spksrc/wiki/Debian-Chroot#configure-services) you might also install midnight commander if you are on it, makes things easier if you're not a command-line junky and more used to a graphical environment that give you clues activate ssh in dsm connect with ssh/putty to you dsm, login with user admin (and if you want to be root use "sudo -i") start the chroot with: /var/packages/debian-chroot/scripts/start-stop-status chroot after that you are inside the chroot, check with ls and you won't see "/volume1" or other sysnology specific directory's from the dsm environment, you can leave the chroot environment with "exit" later if you want now we have to update and install tools: apt-get update apt-get upgrade apt-get install locales dpkg-reconfigure locales dpkg-reconfigure tzdata apt-get install mc make gcc build-essential kernel-wedge libncurses5 libncurses5-dev libelf-dev binutils-dev kexec-tools makedumpfile fakeroot linux-kernel-devel lzma bc after that we create a directory (lets say "test") 1.5 copying kernel files and create kernel modules copy the downloaded kernel (linux-3.10.x.txz) to a share on the dsm, open a 2nd putty and copy the linux-3.10.x.txz (/volume1/...) to /volume1/@appstore/debian-chroot/var/chroottarget/test/ (that's where the "test" directory of the chroot environment is located in your real system) change back to your first putty where you are in chroot (the same way can be used to get the created files back to your shared folder on your volume1 which can be accessed from windows) change into "test", extract the linux-3.10.x.txz to a directory named "linux-3.10.x" and change into it the following copy's the kernel config file from synology to the right place for use/build cp synoconfigs/bromolow .config we make a fallback copy make ARCH="x86_64" oldconfig we start the ascii art menu and search for the missing driver to activate cursor/return are your friend in navigating, space selects, we activate the driver to an "M" so its build as module (*.ko file we need) there will be tons of descriptions how to do it, just google if needed make ARCH="x86_64" menuconfig on exit we save the configuration and with the following we make/create the modules (will take a while) make ARCH="x86_64" modules now you have to find your *.ko file (use some nice ls options, to be expanded later) usually you will have to look in /test/linux-3.10.x/drivers/scsi or block copy that file to /test for easy access when we put it in the boot image 2. modify the "synoboot.img" use osfmount (windows) to extract the "extra.lzma" (see dsm 5.2 to 6.0 guide, used there to edit grub.cfg in synoboot.img) in "extra.lzma" are the additional *.ko files and a config file where the files to be loaded on boot are named -> see forum thread "dsm 5.2 to 6.0" with howto to modify jun's loader for usb vid/pid and mac, its basically the same you just open the other partition (30MB) and extract the "extra.lzma" copy the "extra.lzma" to the share of the dsm so we have local access in a putty session on dsm in putty session #2 ("normal" session without chroot) we copy the "extra.lzma" to the "test" directory in the chroot environment go to putty session#1 (in chroot) decompress "extra.lzma" to "extra" ("extra.lzma" is a compressed cpio file) with: lzma -d extra.lzma with ls we can check that "extra.lzma" is now just ""extra" (a cpio file without the extension cpio) create a new directory, copy the "extra" there, change into it and extract it with: cpio -idv < extra delete the remaining file "extra" inside this directory we copy the *.ko file into usr/lib/modules/ and in /etc we edit the file rc.modules (easy with midnight commander, go to file, press F4, internal editor) network drivers seems to be added under EXTRA_MODULES, storage drivers under DISK_MODULES, just go to the end of the line and fill in the name of the *.ko file without the ".ko", what you add is basically a blank and the name rc.modules looks like this: EXTRA_MODULES="mii mdio libphy atl1 atl1e atl1c alx uio ipg jme skge sky2 ptp_pch pch_gbe qla3xxx qlcnic qlge netxen_nic sfc e1000 pcnet32 vmxnet3 bnx2 libcrc32c bnx2x cnic e1000e igb ixgbe r8101 r8168 r8169 tg3 usbnet ax88179_178a button evdev ohci-hcd" DISK_MODULES="BusLogic vmw_pvscsi megaraid_mm megaraid_mbox megaraid scsi_transport_spi mptbase mptscsih mptspi mptsas mptctl ata_piix megaraid_sas mpt2sas mpt3sas" EXTRA_FIRMWARES="bnx2/bnx2-rv2p-09ax-6.0.17.fw bnx2/bnx2-rv2p-09-6.0.17.fw bnx2/bnx2-rv2p-06-6.0.15.fw tigon/tg3_tso5.bin tigon/tg3_tso.bin tigon/tg3.bin" if your controller or nic needs a firmware, you add the file under usr/lib/modules/firmware/ and add the appropriate line in EXTRA_FIRMWARES, if a extra directory inside "firmware" is used it has to be added to the name, see the bnx2 firmware files after everything is in place we recreate the cpio file, re-compress it as lzma and write it in the directory above as "extra.lzma" the command is used inside the directory where we extracted the file "extra" (command line taken from https://github.com/kref/scripts, its what jun uses to create it): (find . -name modprobe && find . \! -name modprobe) | cpio --owner root:root -oH newc | lzma -8 > ../extra.lzma in putty session #2 (without the chroot) we copy "extra.lzma" from the chroot position in filesystem to the location where we can access it from windows if you still have osfmount open to the "synoboot.img" replace the "extra.lzma" with the new one, dismount and close osfmount - our new "synoboot.img" is ready to test it ps: i was asked to make a video - thats much harder to change and i'm to old for this
  6. 5 points
    Господа модераторы! Какого ХРЕНа вы опять забанили нашего комрада 39911-архип, ранее он был известен как 5213-bob-the-builder, забаньте для кучи и меня, мы тогда с ранее упомянутым комрадом подумаем как увести русскою ветку и не только на другой форум. Или вам покоя не дает, то что кто-то набрал баллов лайков больше вас?! Детский сад Ё-моё. По-этому: 1. Прошу восстановить 39911-архип в правах и приплюсовать, то что было у 5213-bob-the-builder 2. Не трогать этот пост, пусть собирает лайки, они мне не нужны, это для Архипа/Boba.
  7. 5 points
    Все кто "обделен" файлами, просьба повторно написать в ЛС. Вас очень много, и все шлют не по одному сообщению. Понять кто получил а кто нет из за этой каши проблематично. Вас уже около сотни. Из этой толпы почти половина даже спасибо не сказали. Получили желаемое и досвидос. В общак выложить могу, но только с разрешения Администрации.
  8. 5 points
    Тестирую новый генератор SN. Могу в ЛС поделиться SN + MAC для 3617 и 916, валидацию на сино проходят.
  9. 4 points
    Salut à tous, Ici je vais vous expliquez comment faire tourner le DSM 6 Xpenology sur Hyper-V. Téléchargez les VHDX (uploadés par moi même) prévues à cet effet : https://1drv.ms/u/s!Anih4xuqH7tysAOHkDHOqgim2CZ_ Créer une nouvelle machine virtuelle en respectant scrupuleusement les mêmes paramètres que ce screenshot : Appliquez les paramètres comme l'image ci-dessus. N'ajoutez pas votre VHDX de données tout de suite. Démarrez la machine virtuelle attendez 3 à 5 minutes le temps quelle démarre, et configurez là via http://find.synology.com/ Une fois quelle est démarrée et que tout est OK, éteignez-là et ajoutez votre disque VHDX de données : Démarrez de nouveau la machine virtuelle, est vous pouvez allez commencer à créer votre volume dans le Gestionnaire de disque. N'appliquez pas les mises à jour du DSM ! Enjoy !
  10. 4 points
    Massive thanks to jun! Hardware acceleration is now working on my 8th gen i7-8700K. Using new ds918 loader 1.04b. Bare metal on DSM 6.2.1. Even with Plex running inside a Docker container it is detecting the hardware (for anyone wondering, this required the plex user having ownership of /dev/dri/* and setting the device flag + mounting /dev/dri in the container). This is really super... I thought it would only be possible with another big kernel upgrade from Synology. Fantastic to have it working with these CPU's. Thanks again for the amazing work jun 👌
  11. 4 points
    virtio drivers are supported in my loader which will be released once I iron out ESXi upgrades. KVM and baremetal are solid though. Also performance is great as iperf3 has proved great performance. DiskStation> iperf3 -c 192.168.0.2 -i 1 -t 20 -R Connecting to host 192.168.0.2, port 5201 Reverse mode, remote host 10.1.0.2 is sending [ 4] local 192.168.0.212 port 44805 connected to 10.1.0.2 port 5201 [ ID] Interval Transfer Bandwidth [ 4] 0.00-1.00 sec 844 MBytes 7.08 Gbits/sec [ 4] 1.00-2.00 sec 879 MBytes 7.38 Gbits/sec [ 4] 2.00-3.00 sec 898 MBytes 7.53 Gbits/sec [ 4] 3.00-4.00 sec 768 MBytes 6.44 Gbits/sec [ 4] 4.00-5.00 sec 883 MBytes 7.41 Gbits/sec [ 4] 5.00-6.00 sec 899 MBytes 7.54 Gbits/sec [ 4] 6.00-7.00 sec 900 MBytes 7.55 Gbits/sec [ 4] 7.00-8.00 sec 878 MBytes 7.37 Gbits/sec [ 4] 8.00-9.00 sec 907 MBytes 7.61 Gbits/sec [ 4] 9.00-10.00 sec 883 MBytes 7.40 Gbits/sec [ 4] 10.00-11.00 sec 906 MBytes 7.60 Gbits/sec [ 4] 11.00-12.00 sec 828 MBytes 6.94 Gbits/sec [ 4] 12.00-13.00 sec 898 MBytes 7.54 Gbits/sec [ 4] 13.00-14.00 sec 910 MBytes 7.64 Gbits/sec [ 4] 14.00-15.00 sec 758 MBytes 6.36 Gbits/sec [ 4] 15.00-16.00 sec 753 MBytes 6.32 Gbits/sec [ 4] 16.00-17.00 sec 841 MBytes 7.05 Gbits/sec [ 4] 17.00-18.00 sec 960 MBytes 8.05 Gbits/sec [ 4] 18.00-19.00 sec 858 MBytes 7.20 Gbits/sec [ 4] 19.00-20.00 sec 933 MBytes 7.83 Gbits/sec - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bandwidth Retr [ 4] 0.00-20.00 sec 17.0 GBytes 7.29 Gbits/sec 0 sender [ 4] 0.00-20.00 sec 17.0 GBytes 7.29 Gbits/sec receiver iperf Done. And it is better to use synoboot.img as virtual USB drive because then it properly works with upgrades.
  12. 3 points
    Before you begin to change something in your working system, it is strongly recommended to make backups of your most valuable data, so you do not regret about their irretrievable loss. Everything you do is your fear and risk, no one encourages you to do it. The easiest and most reliable way to safely try to do it, turn off all the disks and the boot flash drive from the current system, take a clean disk and another USB flash drive and try to install a new version of the bootloader and the system, if it rolled, then do already on the current system. 1. How to install (described for a computer with Windows): a) download the 1.04 b boot loader image (the original theme is here), create a directory in the root of the disk, for example, c:/918/ and put the bootloader image there b) determine the VID/PID of the flash drive or card reader into which it is inserted (control Panel-Device Manager-USB Controllers-Your flash drive/reader-Properties-Information-hardware ID, you need to ensure that the DSM system recognizes this disk and does not try to install itself on it, if you incorrectly define and register these parameters, the istall process will crash by mistake 13) c) download, install and run the OSFmount program, mount Partition 0 (15 Mb) from the bootloader file, remove the "Read-only drive" checkbox before mounting d) download, install and run Akelpad, open grub/grub file.cfg on previously mounted disk, edit and save: set vid=0xA234 #VID flash drive/reader set pid=0xB678 #PID of flash drive/reader set sn=1780PDN123456 #sn set mac1=001132123456 #mac of the first network card set mac2=001132123457 #mac of the second network card, the second and subsequent differ from the first by +1 in the last bit in the hex system ... set netif_num=2 #number of network cards ... set sata_args= 'SataPortMap=6' # sata controller, values: 6 - 1 controller on 6 ports; 22-2 controllers on 2 ports; 42-2 controllers, the first on 4 ports, the second on 2, etc. Where to get sn and mac - is your headache, Google will help you, the system will be installed and will work with those that are initially registered in the bootloader, but with the restriction of the functioning of some services and modules, such as: QC, push notifications, activation of codecs for transcoding, installation of syno licenses... e) unmount the disk in OSFmount f) download, install and run the Rufus program and record the previously prepared image on a flash drive g) insert the flash drive into the computer on which you plan to run xpen, connect the drives, turn on the power h) disable the firewall in the anti-virus, in the browser type http://find.synology.com or install Synology Assistant from the syno website and find the newly installed xpen on your network j) install DSM following the instructions of the installation program and start setting up (how to do it here is not described, because all the answers are in the syno knowledge base) There is a utility where the main programs for Windows x64 are collected 2. Transcoding (needs sn and mac from real syno hardware) Most likely to run on Intel processors starting from the 4th generation (Haswell), but there are nuances with motherboard models and BIOS. Check as follows: hardware (hw) transcoding - at the root of the system should be a directory /dev/dri with subdirectories in it, if not, but there is no HW transcoding to check - look for the directory with the terminal/ssh command cd /dev/dri . software (sw) transcoding - some codecs must run in DSM, you can check it with the command in the terminal / ssh cat /usr/syno/etc/codec/activation.conf If the result is the same, sw transcoding will ran {"success":true,"activated_codec":["h264_dec","h264_enc","mpeg4part2_dec","hevc_dec","aac_dec","aac_enc","ac3_dec","vc1_dec","vc1_enc"],"token":"123456789987654abc"} If there is nothing similar, there is no sw transcoding. 3. Perhaps the most optimal budget solutions with transcoding will be the following: ASRock J4105-ITX Asrock J5005-ITX Who wants more - use mb with the latest generation of Intel processors with Intel i210 or realtek 8111 . But this is already determined by the size of the your wallet and the functionality that you additionally want to get from xpen. P.S. Sorry for my english 😂
  13. 3 points
    Hello @FOXBI. Is it possible to update your tool so that it is fully functional with the latest release of DSM 6.2? Thanks.
  14. 3 points
    Надо понимать, что MTU должно быть одинаковым на всем пути прохождения пакета. Сервер, свичи, роутеры, клиенты. В домашних сетях это большая редкость. Например если напрямую есть соединение VMWare сервер-NAS и между ними только кабель или свитч с поддержкой (и настроенным) больших MTU, то большие файлы (виртуальные диски) МОГУТ копироваться чуть быстрее между этими устройствами, для всех остальных будет как минимум небольшое замедления из-за фрагментации пакетов или, чаще, заметное ухудшение. Если не уверены что такое MTU и как ВАМ это поможет, оставьте это значение по умолчанию - 1500 для Ethernet. Представите себе огромный грузовик (БеЛАЗ?) с гигантским кузовом. Для перевозки больших обьемов грузов, если позволяет дорога, между карьером и отвалом/складом, может быть полезно. Для городских развозов обычных габаритных грузов, лучше пользоваться стандартными грузовиками по стандартным дорогам.
  15. 3 points
    Нас уже трое ) ok, кидайте мне в лк, кто сколько может на пиво и будет вам номерок и мак в придачу + в довесок белый ddns ovh
  16. 3 points
    Hello, my first post and I really want to say thank you to all the community I've upgraded with success from 5.2-5967.1 update 3 to 6.1.2-15132 with loader 1.02b esxi 6.0 update 2 on Microserver gen8 with xeon E3 1220L v2 1 ssd for datastore on internal controller and passthrough of a LSi 9211-8i flashed in IT mode with 4 HDDs migration, no clean install and volume repair what I've done: 1) download the image file from first post here (I've used loader 1.02b ds3615) 2) edit settings of your current vm with xpenoboot 5.2 and write down MAC address 3) login to your DSM 5.2 web interface and write down serial number; shutdown the vm 4) download and install OSFmount, then mount the image file downloaded at point 1 (untick "read-only drive"); choose partiton 0 15MB 5) with notepad++ or similar edit grub.cfg with serial and MAC address from point 2 and 3, you can also change the default timeout; I haven't changed anything related to vid and pid 6) download and install StarWind V2V Image converter; convert the image file with modified grub.cfg (choose VWware ESX server image) 7) this will result in 2 files synoboot.wmdk and synoboot-flat.wmdk 8) upload them to the same datastore where you have xpenoboot.wmdk; you can use datastore browser to upload files 9) edit settings of the vm and delete the hard disk pointing to xpenoboot.vmdk virtual disk 10) add new hard disk scsi 0:0 independent non persistent pointing to synoboot.vmdk 11) I haven't added any serial port 12) start the vm and open immediately the console, because you have to select the third entry of the boot menu, the one related to esxi (I wasn't enough quick and needed a vm reset..) 13) open a web browser to find.synology.com 14) connect, install, migrate, manual install with the latest pat file you can download from links here https://xpenology.com/forum/topic/7294-links-to-dsm-and-critical-updates/ 15) in my case the ip was changed, so log in and update it, then update packeges in the package center... backup and replication is now called hyperbackup hope this helps someone bye
  17. 2 points
    Einfachste Vorgehensweise: - System herunterfahren und alle HDDs abklemmen - eine einzelne leere HDD anschließen - System wieder hochfahren und aktuelles DSM installieren - testen, ob alles funktioniert; besonders die Netzwerkverbindung - System wieder herunterfahren, alte HDDs dran und dann upgraden
  18. 2 points
    У меня стоит MidnightCommander из репозитория Synocommunity. Соответственно захожу через putty по ssh под учётной записью админа, далее ввожу sudo su и запускаю Миднайт - mc. В нем есть редактор по F4. Можно ещё редактор nano поставить, может ещё какой можно линуксовый.
  19. 2 points
    Please see this for loaders vs. versions. 6.2.x has a number of hardware constraints on it, so you may need to pick your loader and platform carefully, referencing your hardware.
  20. 2 points
    très bien , contacter moi mercredi ou jeudi je vous donnerais les info pour l'envoie etc ......
  21. 2 points
    Que dire à ta question.... : http://www.reseau-des-marabouts.com/
  22. 2 points
    Решил позволить себе жить с размахом(с) и взял в рассрочку на год Asrock J4105-ITX и две планки памяти DDR4 Crucial 4Gb 2666Mhz (BLS4G4S26BFSD) вышло чуть больше тысячи месяц - могу себе позволить ))) Перекинул жесткий диск на неё, сделал флешку с 1.04 и мигрировал с 6.2 3617 на 6.2.1 918. Всё встало, папка dev/dri появилась, но транскодинг нормально не заработал - при этом в dmesg было примерно такое: Форматнул на жестком первые два раздела, сделал заново флешку - та же хрень. А всё почему? - потому что не надо было трогать настройки биоса - влючил зачем то vt-d. Вернул всё в дефолт и всё заработало без переустановки, думаю и смиграцией бы срослось если не лазил бы. Да - биос 1.4 сразу был на борту. Обратите внимание на скрине выше какаят о ошибка про gen8, а в 4105 - gen9, то есть драйвер не заточен так скзть под проц полностью. Теперь о транскоде вот такого видео hevc, 77272.2 Kbps, 3840 x 2160, кадров 59.940 Профиль Main Level 153: в VideoStation проц на одном этом видео в районе 15-20%, Emby - аналогично, через "Сервер мультимедиа" по DLNA так же, и теперь мои древние Соньки могут видеть всё - сэкономлю на приставке ))) А с плексом какая то дурь, аппаратный работает, но существенно сильнее грузит проц на 100%: Да, по поводу установки - я ставлю PAT файл DSM_DS918+_23824.pat "ручками", но после установки система стоит уже 6.2.1 u4 - во время установку, бутается она два раза - после того как счетчик процентов дойдет до 100 и пойдет обратный таймер, и один раз сама во время обратного отсчета 10 минут, - видимо как раз и ставит обновы. Система грузится меньше минуты, скорость по сети не максимуме - 109-112 мб/сек. Вобщем рекомендую к покупке )
  23. 2 points
    OVA for DSM 6.2-23739 Update 2 • DS3617XS • VM HW Level 10 (ESXi 5.5 or newer, only imports on 6.5 and 6.7, use OVFtool with --shaAlgorithm=sha1 to convert for 5.5 or 6.0) • PVSCSI • VMXNET3 https://mega.nz/#!M1kX0TjR!S87LHngw1C3wa3i-3p-r9WyWCmFO4A9t3THhMWeea_w All DS3617XS OVAs use Jun v1.03b bootloader, DS918+ uses Jun v1.04b bootloader. Some instructions for the Intel passthrough VIB above, it puts "8086 ffff d3d0 false" (ffff = wildcard) in /etc/vmware/passthru.map. Put it on a datastore and goto the shell: esxcli software vib install -v /vmfs/volumes/myDatastore/intel-passthrough-1.0.0-01.x86_64.vib --no-sig-check -f Or when you want the latest ESXi ISO with it integrated using ESXi-Customizer-PS, put in in a folder and add: -pkgDir C:\myFolder -nsc -force
  24. 2 points
    ffmpeg не нужен совсем! вот актуально как запускаем если из консоли: docker run -d --privileged --net=host --name=ace86f -e TZ=Europe/Moscow sybdata/ace86fed:v3133 # OS fedora docker run -d --privileged --net=host --name=ace86a -e TZ=Europe/Moscow sybdata/ace86a37 # OS alpine docker run -d --privileged --net=host --name=ace86u -e TZ=Europe/Moscow sybdata/aceubase:v3133.1 # OS ubuntu
  25. 2 points
    - Outcome of the installation/update: SUCCESSFUL - DSM version prior update: DSM 6.1.7-15284 u2 - Loader version and model: JUN'S LOADER v1.02b - DS3615xs - Using custom extra.lzma: YES - Installation type: BAREMETAL - Microserver Gen8 - Additional comments: Need Reboot
  26. 2 points
    - Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.1.7-15284 Update 2 - Loader version and model: Jun's loader v1.02b - DS3615xs - Using custom extra.lzma: NO - Installation type: BAREMETAL - Microserver Gen8 - Additional comments: REBOOT REQUIRED
  27. 2 points
    at the end!!! 😁😁, my N54L with DSM 6.2.1U4 it shutdown correctly from the DSM OS and reboot perfectly. After differents test I'm not sure what is exactly the real solution: or it's the U4 or the ACPI version 1.0. With 2.0 and 3.0 not works. My bios version is from 2011 too. I hope this help to other people. I've disabled the embedded NIC Port 1 control, too.
  28. 2 points
    завтра-послезавтра ожидаю этот девайс. по заявлениям испытавшего его товарища - 100% рабочее решение на 918+. испытаю сам, сразу отпишу.
  29. 2 points
    Before I ran FOXBI's script, the specs said 4 cores for Xeon D-1527, which is the CPU in the DS3617xs: Note this is the number of cores, NOT threads which would be 8 for this CPU! Check Intel's datasheet here. So DSM is always meant to show physical cores, not logical ones. Therefore this is a small bug in the script....
  30. 2 points
    а и не надо из ассистента ставить, всё надо из вебморды делать
  31. 2 points
    - Outcome of the installation/update: SUCCESSFUL - DSM version prior update: DSM 6.2-23739 Update 2 - Loader version and model: JUN'S LOADER v1.03b - DS3615xs - Using custom extra.lzma: NO - Installation type: BAREMETAL - HP Microserver GEN 8 - Additional comments: On-board NIC no longer works after this update. Had to throw in a 4-port PCIe NIC (Intel Corporation I350 Gigabit Network Connection)
  32. 2 points
    (use the opposite of what you have installed currently) so if you have loader for 3617 then use files from 3615 and if loader is 3615 then use files from 3617
  33. 2 points
    I was finally able to get v1.03b to work successfully after a lot of runarounds with ESXI 6.7. No Diskstation found within LAN: I've created a new VM and set my modified synoboot (updated VID/PID/SN/MAC) as an SATA HDD. Booted the 3rd option (Vmware/ESXI) and it detected on the network. Once it was detected, I could then migrate to 6.2. After migration was completed, all of my packages would close within minutes of the system booting up. To resolve this, I had to delete the hidden .xpenoboot that was located at root. Open SSH and use Putty to remove the .xpenoboot folder. Rebooted the system and all the packages would now stay up and running. Hope this helps other users!
  34. 2 points
    get yourself stuff like debugger, IDA, ... reverse engineer jun's "patch" (its part of the loader) and redo it for the other systems (kernels, the loader is pretty much the same, the hack is specific for every platform aka kernel) i guess the 918+ is just the test to see if all protections are gone and the patch is 100% working, investing work on two other platforms and having to redo it because something was missing in the 1st try is not much fun i guess, if everything with 918+ goes well for a while i expect jun will release more just give it a while i guess its like solving a problem (doing one/1st platform patch) is fun and maintaining stuff (doing more platforms) is work, to make it useful for many people you will have to do both but you want to minimize the 2nd part, i think (just logic) jun will at least do a patch for 3617 later to see if potential problems are found, if 3617 can handle all hardware like 3615 it makes not much sense to maintain 3615 further, the update support of synology will end earlier for 3615, but i don't know anything about how jun's point is there so its pure speculation based on things i've catched here in the forum so be patient or start hacking (an if you are on hacking, just have a look for the sata kernel mod's synology did so we can have sata_*.ko/pata_*.ko drivers)
  35. 2 points
    Does anybody know if Jun will be looking at an upgraded loader for the DS3615xs? My cpu is too old to run the 918+ loader.
  36. 2 points
    @agent47SG1 or @Bi0 if you can post the copy of the VM would be appropriate no clue what i doing wrong to get 6.2 up to test and look at.
  37. 2 points
    Tested on a VM on a ESXi 6.7 on a Gen8 with Xeon E3-1220 V2 and it is not working. It gets stuck on this screen (as expected) but the network interface is not recognized so i am not able to trigger the setup (and yes i selected the E1000 as network card). I think it's dependant on the instructions library missing on older CPU like someone said before.
  38. 2 points
    Hi, do you have paypal account? I would like send you little money - beer, coke, … coffee. Thank you so much for your job Robert from Czech Republic
  39. 2 points
    Системные разделы есть на каждом внутреннем диске. Все диски содержат зеркало системы для отказоустойчивой загрузки. Когда все нормально, диски показаны как Иницилизированны. У вас на одном диске новая система а на остальных старая. Востановление должно обновить систему на всех дисках со старой системой в соответствии с последней установленной версией. Эта операция просто клонирует систему на все диски (в системный раздел) без затрагивания данных, которые лежат отдельно на разделе пользовательских данных и организованны (В Вашем случае) в RAID group 2.
  40. 2 points
    that's a little bit more then just "a file", but it's already done, the realtek drivers are part of my extra.lzma https://xpenology.com/forum/topic/9508-driver-extension-jun-102bdsm61x-for-3615xs-3617xs-916/ that's not going to work, its not like windows, the driver has to be compiled specific for the kernel and in our case its not just kernel 3.1.102, its a sysnology modified kernel of this version so it hast to be compiled against the source from synology i wrote a how to about that, but you can just use the extra.lzma from above, no need to build your own driver https://xpenology.com/forum/topic/7187-how-to-build-and-inject-missing-drivers-in-jun-loader-102a/
  41. 2 points
    Here's Synology's actual information about Meltdown/Spectre: https://www.synology.com/en-us/support/security/Synology_SA_18_01
  42. 2 points
    hi, i uploaded new 4.1 versions change is mainly that i took whats already was in 4.0 and copy over the freshly extracted drivers from jun's 1.02b loader in case I've overwritten some drivers with newly compiled ones or accidentally copied a wrong version i added modules like mpt2sas/mpt3sas because they where in rc.modules but not present in jun's extra.lzma (extracted them from dsm 6.1.3) in that process i was overthinking what can go wrong and also started comparing jun's three loaders with each other and compared rc.modules with whats in the extra.lzma when it comes to installing dsm it does not matter whats inside the dsm file itself, if the loader it booted only drivers in that loader (and the extra.lzma) will be able to detect hardware, leaving drivers network and storage drivers that are part of the dsm file out of the loader would result in cases where the hardware is not detected by the loader but if dsm is already running then the hardware will be detected example: dsm for 3615 contains bnx2x.ko and no driver for e1000.ko the loader only provides e1000.ko (as there seems no need for bnx2x,ko as its already part of dsm) result will be a system with a onboard intel nic and additional boradcom netxtreme II will be able to install dsm as the intel is found and after installation the broadcom driver is loaded and you will see the 2nd nework adapter in case there is only a broadcom netextreme II (like hp or dell server having them as onboard) the booting the loader will not find the nic and you can't install dsm at all the same gos for storage drivers so mpt*.ko has to be part of the bootloader also there may be errors in the whole approach in using the source of 6.1.3 as jun's loader s is based on 6.1.0 (15047) my drivers are compiled with the source of 6.1.3 (15152), when looking for the "destination" of using 6.1.3 that's good but it might collide with the base of the bootloader as there are differences in source that can matter (like unknown symbols when loading a driver from 6.1.3 on a 6.1.0 base/kernel)
  43. 2 points
    долгое время болтались две baremetal машинки на загрузчике 5.2.5644.5 и с апдейтом до 5.2.5967 (делал давно). видя позитивные отзывы участников об успешных последних обновлениях под загрузчиком 5.2.5967.1 решил перед апдейтом системы сначала накатить последний загрузчик, но вытаскивать машинки из шкафа для перезаливки флешек очень нехотелось. полистал форум и сделал так (может пригодится кому-то такому же ленивому и дремучему, как я): 1. смонтировал загрузочную флешку на работающей системе в SSH: [информация отсюда] > mkdir -p /mountUSB > losetup -f /dev/loop0 > losetup -o 32256 /dev/loop0 /dev/synoboot > mount -t vfat /dev/loop0 /mountUSB 2. скачал загрузчик 5.2.5967.1 [ links-to-loaders ], извлёк из него файлы, сравнил с теми, что находятся в /mountUSB, и убедился, что единственные различия - файлы zImage и syslinux.cfg. 3. перезаписал в /mountUSB файл zImage от нового загрузчика, и, чтоб в будущем не путаться, исправил номера версий в текстовом меню-файле /mountUSB/syslinux.cfg, не трогая ранее прописанные параметры. 4. после успешной перезагрузки запустил из web-консоли обновление до DSM 5.2-5967 Update 6. после непродолжительного обратного отсчёта машина перезагрузилась, и тут же успешно стартанула. так же успешно, без проблем, повторил эту процедуру со второй машинкой. обе работают без нареканий. подобного не замечено. открывается шустро, как и прежде.
  44. 2 points
    поздравляю с успехом! на будущее (мож ещё кому пригодится): если нужно только прочитать данные - можно попробовать UFS Explorer Professional Recovery тестировал под виндой чтение стандартных рейдов, создаваемых из-под Synology, и она показала себя очень хорошо. SHR не тестировал, работает ли с ним - не знаю.
  45. 2 points
    Generally the rackstations which have larger expansion capacity use SAS HBAs and therefore are not limited by the sd(x) issue; as rackstations have SAS HBas this is one of the reasons why we do not have a rackstation image... For what its worth, a rackstation image with native LSI SAS drivers would probably allow for proper drive sequencing on LSI cards as well as large expansion potential.
  46. 2 points
    very easy to use a usb to boot from Probably best to use the latest Syno release 6.1+ to install DEf do your bios firmware updatye before loading anything else on your box Even tho I would check that the bios update does something you need /desire otherwise leave alls well that stays well. pointing you to a good guide to installing is xpenology is a moving target. If you did the install to your N40l you should be ok BUT the Bios on the gen8 requires you to set your disks up first SUmmary update BIos if necessary create bootable usb stick (with NanoBoot or other software on it) insert usb stick into gen8 boot gen8 (takes afew minutes 5-10) use find.synology.com or synology web assistant to find your new xpeno on your lan. point installation to your PAT file (probably stored on your PC) have some nice fresh disk installed point installtion to your disk after some minutes you will have nice fresh installtion. I am lucky in that I have an old 19in monior (+kyb) attached to the gen8 so setting the bios , following all the prompts and watching the boot progress is much easier. My usb stick stays in the gen8 but the monitor can be safely stowed away when all is hunkydory. You could update your CPU to i3 or xeon, also you should be able to "import" you old n40l disks to your new installation you could also import your configuration if you save it on the n40l.
  47. 2 points
    Removing the boot loader will simply prevent DSM from booting... There is a reason why it's called a "boot loader". Also I don't think using Jun's boot loader 1.02b will work on a laptop as I believe the modules are not included. Also be advised that even if it works you would need to access DSM from a different computer. DSM is a server OS and therefore is not meant to have a display attached to it. It is meant to be accessed through the network. In any case that black screen and a cursor tells me that the usb boot loader did not boot, perhaps because you removed it in the first place...
  48. 2 points
    Hello again! It seems that I have found the sollution after all. After looking for any "BACKUP" entry in any file on the DSM through the console ( find / -type f -exec grep -H 'BACKUP' {} \; ) I found 2 refferences to the mentioned name in the /etc/samba/smb.conf file. [BACKUP] invalid users=nobody,nobody valid users=nobody,nobody comment="Backup D1" path=/volume3/BACKUP guest ok=yes browseable=yes fileindex=no mediaindex=no edit synoacl=yes win share=yes skip smb perm=yes enable recycle bin=no recycle bin admin only=no hide unreadable=no ftp disable list=no ftp disable modify=no ftp disable download=no read list=nobody,nobody write list=nobody,nobody writeable=yes [BACKUP 2] invalid users=nobody,nobody valid users=nobody,nobody comment="Backup disk 2" path=/volume1/BACKUP 2 guest ok=yes browseable=yes fileindex=no mediaindex=no edit synoacl=yes win share=yes skip smb perm=yes enable recycle bin=no recycle bin admin only=no hide unreadable=no ftp disable list=no ftp disable modify=no ftp disable download=no read list=nobody,nobody write list=nobody,nobody writeable=yes I then tried creating a new shared folder, and found out that there are 2 files that store information about the current SMB shares, the "smb.conf" and "smb.share.conf". But the newly created file is only visible in the smb.share.conf file. The other file smb.conf was probably the file used in the previous version of DSM. (In my case DSM 5.2) So it seems that DSM reads the samba configuration from both files, but only edits one of them. After I removed the "BACKUP" and "BACKUP2" from the smb.conf file, both of these shared folders were no longer visible on any client using samba/smb protocoll. I`m not sure if this is just a local bug on my DSM, but if not, i immagine that this will happen to a lot of people when they try to delete a shared folder that was created on a older version of the DSM. Hope this helps someone. @admins: Not sure how i can mark this topic as solved, so could you please do it? Thanks!
  49. 2 points
    Might be an esx issue; read about it here, there is also an easy fix; read at least the last 3 pages : https://homeservershow.com/forums/topic/9602-esxi-notes/?page=10 this is the solution, from that topic (working for me with esxi 6.5): " downloaded the hpvsa-5.5.0-88.zip archive (as per HP advisory) and uploaded the vib to the datastore. eg /datastore1/patch/scsi-hpvsa-5.5.0-88OEM.550.0.0.1331820.x86_64.vib via the ESXi web interface http://h20564.www2.hpe.com/hpsc/doc/public/display?docId=c05026755 8. remove the exsisting scsi-hpvsa_5.5.0.102-1O driver (via SSH) (enable maintenance mode first) # esxcli software vib remove -n HPE:scsi-hpvsa Removal Result Message: The update completed successfully, but the system needs to be rebooted for the changes to be effective. Reboot Required: true VIBs Installed: VIBs Removed: HPE_bootbank_scsi-hpvsa_5.5.0.102-1OEM.550.0.0.1331820 VIBs Skipped: 9. Install the scsi-hpvsa-5.5.0-88 downgraded driver # esxcli software vib install --viburl=/vmfs/volumes/datastore1/patch/scsi-hpvsa-5.5.0-88OEM.550.0.0.1331820.x86_64.vib Installation Result Message: The update completed successfully, but the system needs to be rebooted for the changes to be effective. Reboot Required: true VIBs Installed: Hewlett-Packard_bootbank_scsi-hpvsa_5.5.0-88OEM.550.0.0.1331820 VIBs Removed: VIBs Skipped: 10. Disable ESXi vmc_ahci module (if not completed, ahci is used by default. eg array is not initialised via hpvsa and ahci initialises disks as 4 separate physical disks) # esxcli system module set --enabled=false --module=vmw_ahci 11. Reboot Server 12. Re-test file write speed to local data store (disable maintenance mode and enable TSM-SSH first) # cd /vmfs/volumes/datastore1 # time dd if=/dev/zero of=tempfile bs=8k count=1000000 1000000+0 records in 1000000+0 records out real 1m 40.79s user 0m 3.70s sys 0m 0.00s much better " for esxi 6.0 you don't need to disable vmc_ahci module (step 10) but it is required on 6.5
  50. 1 point
    If you try it on proxmox and still get Hdd errors, than my guess would be some hardware malfunction.