Tyrell66 0 · ID: 1 Posted February 1 Hi guys, I'm trying to setup a new DSM on a recycled Server I got. When I boot on the USB stick (flashed with Jun's Loader 1.03b), it freezes after the text "Screen will stop updating shortly". Booting with Hiren Boot CD on the same USB stick or a Win7 on another HDD works fine. I've updated the grub.cfg with the pid/vid/mac/SN accordingly. Can you please help? PC HP 6300 Tower CPU: Intel i5 3rd gen. Graphic: Intel HD integrated NIC: Intel 82579LM MAC: B4B52FC33BE1 SKU: QV985AV BIOS K01 V02.05 HDD: 2*2Tb SATA (set in AHCI in BIOS) Share this post Link to post Share on other sites
sbv3000 61 · ID: 2 Posted February 1 screen will stop updating is normal behaviour, you dont see the drivers loading as in v5 boot loaders. can you find the nas on your lan? if yes then you can move on to install dsm if not you might need to diagnose more, perhaps with a serial port connection, you can see the full boot load activity then Share this post Link to post Share on other sites
Tyrell66 0 · ID: 3 Posted February 2 Hi, I don't see the nas in the lan. I tryed replacing the extra.lmza with the bigger one, but with does not help. I tryed boot with a lubuntu live usb stick, and I have a message below looping indefinitively. Any idea? Share this post Link to post Share on other sites
DeviantGeek 0 · ID: 4 Posted February 2 If your USB drive is plugged into a USB3 port, try a USB2 port. If you don't have one, see if you can turn off USB 3 in your bios and try again. Also, make sure the USB is emulated as a hard drive in your bios. Share this post Link to post Share on other sites
Tyrell66 0 · ID: 5 Posted February 4 Plugging it in a USB2 port doesn't change a thing I'll try tonight with a serial cable. Share this post Link to post Share on other sites
Olegin 236 · ID: 6 Posted February 4 В 01.02.2019 в 10:20, Tyrell66 сказал: NIC: Intel 82579LM The driver for this NIC - e1000e is absent in the 1.03&1.04 loaders. The same problem is here. Share this post Link to post Share on other sites
flyride 118 · ID: 7 Posted February 4 (edited) 5 hours ago, Olegin said: The driver for this NIC - e1000e is absent in the 1.03&1.04 loaders. The same problem is here. Maybe I am not understanding what is being stated. NIC drivers are not in loaders except as part of an extra.lzma. The implication is that DSM 6.2 or 6.2.1 is used with a 1.03 or 1.04 loader, and for DS3615, DS3617 and DS918 DSM distributions, e1000e driver is present in all cases. Edited February 4 by flyride 1 Share this post Link to post Share on other sites
DeviantGeek 0 · ID: 8 Posted February 4 A quick google search shows that error you are seeing is a bug in lubuntu. Please try booting off a newer version or trying a different iso/software. I typically use Hirens Boot cd. It comes in handy. It is a windows 10 based image/iso. You can find the USB version here. Share this post Link to post Share on other sites
Olegin 236 · ID: 9 Posted February 5 14 часа назад, flyride сказал: NIC drivers are not in loaders except as part of an extra.lzma. The implication is that DSM 6.2 or 6.2.1 is used with a 1.03 or 1.04 loader, and for DS3615, DS3617 and DS918 DSM distributions, e1000e driver is present in all cases. Yes, you are right, and I used incorrect information from this post. I looked extra.lzma from 1.04 b, here is the correct list of the drivers: Скрытый текст -rw-r--r-- 1 root root 51984 Jan 19 17:47 agpgart.ko -rw-r--r-- 1 root root 46288 Jan 19 17:47 alx.ko -rw-r--r-- 1 root root 54312 Jan 19 17:47 atl1c.ko -rw-r--r-- 1 root root 49648 Jan 19 17:47 atl1e.ko -rw-r--r-- 1 root root 50200 Jan 19 17:47 atl1.ko -rw-r--r-- 1 root root 25736 Jan 19 17:47 ax88179_178a.ko -rw-r--r-- 1 root root 105304 Jan 19 17:47 bnx2.ko -rw-r--r-- 1 root root 55120 Jan 19 17:47 BusLogic.ko -rw-r--r-- 1 root root 13907 Jan 19 17:47 button.ko -rw-r--r-- 1 root root 5688 Jan 19 17:47 cfbcopyarea.ko -rw-r--r-- 1 root root 7720 Jan 19 17:47 cfbfillrect.ko -rw-r--r-- 1 root root 5008 Jan 19 17:47 cfbimgblt.ko -rw-r--r-- 1 root root 81088 Jan 19 17:47 cnic.ko -rw-r--r-- 1 root root 223896 Jan 19 17:47 drm_kms_helper.ko -rw-r--r-- 1 root root 535808 Jan 19 17:47 drm.ko -rw-r--r-- 1 root root 250208 Jan 19 17:47 e1000e.ko -rw-r--r-- 1 root root 155240 Jan 19 17:47 e1000.ko -rw-r--r-- 1 root root 65608 Jan 19 17:47 fb.ko -rw-r--r-- 1 root root 4016 Jan 19 17:47 fb_sys_fops.ko -rw-r--r-- 1 root root 1966232 Jan 19 17:47 i915.ko -rw-r--r-- 1 root root 213208 Jan 19 17:47 igb.ko -rw-r--r-- 1 root root 31128 Jan 19 17:47 intel-agp.ko -rw-r--r-- 1 root root 29640 Jan 19 17:47 intel-gtt.ko -rw-r--r-- 1 root root 285760 Jan 19 17:47 ixgbe.ko -rw-r--r-- 1 root root 54008 Jan 19 17:47 jme.ko -rw-r--r-- 1 root root 50504 Jan 19 17:47 libphy.ko -rw-r--r-- 1 root root 6328 Jan 19 17:47 mdio.ko -rw-r--r-- 1 root root 69088 Jan 19 17:47 megaraid.ko -rw-r--r-- 1 root root 53320 Jan 19 17:47 megaraid_mbox.ko -rw-r--r-- 1 root root 17832 Jan 19 17:47 megaraid_mm.ko -rw-r--r-- 1 root root 164520 Jan 19 17:47 megaraid_sas.ko -rw-r--r-- 1 root root 8152 Jan 19 17:47 mii.ko -rw-r--r-- 1 root root 343040 Jan 19 17:47 mpt3sas.ko -rw-r--r-- 1 root root 106504 Jan 19 17:47 mptbase.ko -rw-r--r-- 1 root root 45584 Jan 19 17:47 mptctl.ko -rw-r--r-- 1 root root 38872 Jan 19 17:47 mptscsih.ko -rw-r--r-- 1 root root 26200 Jan 19 17:47 mptspi.ko -rw-r--r-- 1 root root 144616 Jan 19 17:47 netxen_nic.ko -rw-r--r-- 1 root root 57528 Jan 19 17:47 pcnet32.ko -rw-r--r-- 1 root root 58768 Jan 19 17:47 qla3xxx.ko -rw-r--r-- 1 root root 381696 Jan 19 17:47 qlcnic.ko -rw-r--r-- 1 root root 122312 Jan 19 17:47 qlge.ko -rw-r--r-- 1 root root 642888 Jan 19 17:47 r8168.ko -rw-r--r-- 1 root root 10528 Jan 19 17:47 raid_class.ko -rw-r--r-- 1 root root 23504 Jan 19 17:47 rtc-cmos.ko -rw-r--r-- 1 root root 52936 Jan 19 17:47 scsi_transport_sas.ko -rw-r--r-- 1 root root 36680 Jan 19 17:47 scsi_transport_spi.ko -rw-r--r-- 1 root root 334552 Jan 19 17:47 sfc.ko -rw-r--r-- 1 root root 50520 Jan 19 17:47 skge.ko -rw-r--r-- 1 root root 79864 Jan 19 17:47 sky2.ko -rw-r--r-- 1 root root 5560 Jan 19 17:47 syscopyarea.ko -rw-r--r-- 1 root root 7656 Jan 19 17:47 sysfillrect.ko -rw-r--r-- 1 root root 4944 Jan 19 17:47 sysimgblt.ko -rw-r--r-- 1 root root 210696 Jan 19 17:47 tg3.ko -rw-r--r-- 1 root root 20536 Jan 19 17:47 uio.ko -rw-r--r-- 1 root root 44275 Jan 19 17:47 usbnet.ko -rw-r--r-- 1 root root 32368 Jan 19 17:47 vmw_pvscsi.ko -rw-r--r-- 1 root root 66008 Jan 19 17:47 vmxnet3.ko Share this post Link to post Share on other sites
Tyrell66 0 · ID: 10 Posted February 10 Hi guys, my system is finally in place. I tried everything on baremetal, but nothing worked. I then installed ESX 6.5.0, and created my VM the same way I did my first Xpenology. But here again, Bootloader did not start correctly. Even with the virtual Serial port redirected to a file, it didn't helped. Finally, I used a OVA template I found here on this very forum. And it worked just fine 😀 Until I noticed that one of my RAID1 disk was out of its life ☹️ Thanks for your help when I was blocked. Tyrell66 PS: I think there should be an option to see the boot log, in order to be able to debug easier. Serial port is quite an old tech don't you think. Share this post Link to post Share on other sites
Tyrell66 0 · ID: 11 Posted February 11 Link to working OVA template: Share this post Link to post Share on other sites
