petersnows

Transition Members
  • Content Count

    12
  • Joined

  • Last visited

Community Reputation

0 Neutral

About petersnows

  • Rank
    Newbie

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. (Использование Google Translate) Можете ли вы загрузить файлы снова? Я имею ввиду 3,6Мб. Не весь пакет. Спасибо
  2. Thanks IG-88 I have tested before installing the DSM. I created a usb pen with: v1.04b DS918+ with: extra.lzma/extra2.lzma for loader 1.04b ds918+ DSM 6.2.3 v0.12.1 plug the usb pen and booted find.synology.com appears but I am not able to connect to it using SynologyAssitant plug the usb pen and booted find.synology.com appears but I am not able to connect to it using SynologyAssitant plug an "usb-Ethernet device" find.synology.com appears and I am able to connect using SynologyAssitant I don't even use the "usb-Ethernet device" to connect to it I repe
  3. I was able to get SynologyAssistant to work, connecting an USB-Ethernet card. Just by connecting it, without changing anything else. I can now see both network cards (the usb one and the intelNUC one). Do you know why ? I then installed the DSM like usual. No I notice that the CPU in controlPanel (J3455) is not the one on the machine. ( i3-8109U CPU) Does this impacts the performance ? Here you have the lscpi (of the NUC8i3BEH after installed the DSM) I removed the usb-ethernet device, after installed the DSM admin@syno:/proc/net$ lspci -
  4. I am trying to to install xpenology on intel NUC NUC8i3BEH (Intel® Core™ i3-8109U, Intel® Ethernet Connection I219-V) I have tried : v1.04b DS918+ v1.04b DS918+ with: extra.lzma/extra2.lzma for loader 1.04b ds918+ DSM 6.2.3 v0.13.3 v1.04b DS918+ with: extra.lzma/extra2.lzma for loader 1.04b ds918+ DSM 6.2.3 v0.12.1 I always get find.synology.com. But I am not able to connect to it using SynologyAssitant I also don't see any new entry in the DHCP server. Can anyone help me ? I think the driver for this device is e1000e, but it's not working.
  5. petersnows

    DSM 6.2 Loader

    Hello guys, I just updated my synology setup to 6.2.2-24922 v1.03b - DS3615xs I boot using: "DS3615xs 6.2 Baremetal with Jun's Mod v1.03b" But I see this line (see serial.out ) patching file etc/synoinfo.conf Hunk #1 FAILED at 291. 1 out of 1 hunk FAILED -- saving rejects to file etc/synoinfo.conf.rej Is there a way to fix this ? Why do I see it ? I am attaching: /etc/synoinfo.conf /etc.defaults/synoinfo.conf jun.patch (that everyone has it) Thanks My Setup Info: - DSM version prior update: DSM 6.1.7-15284 update 3 - DSM af
  6. - Outcome of the installation/update: SUCCESSFUL - DSM version prior update: DSM 6.1.7-15284 update 3 - Loader version and model: JUN'S LOADER v1.03b - DS3615xs - Using custom extra.lzma: NO - Installation type: VM - ESXi 6.5 (HP MicroServer Gen8 with Xeon CPU E31260L 1265v2) (4 virtual SATA HardDrives: 50Mb 50Gb 1.7Tb 2.7Tb) - Additional comments: It failed in the beginning , as all services, including networking, would shutdown a few seconds after logging in to DSM (SYNO.Core.Desktop.Initdata_1_get would call "usr/syno/bin/synopkg onoffall stop"). Saw other posts men
  7. Hi pigr8, "the cougarpoint is passed through to the xpenology vm" how did you passthrough the pci cougarpoint ? My ESXI 6.5 does not allow that. Can you send photos of your setup ? Pedro
  8. So far I was able to resolve this by doing the following: - syno_poweroff_task -d - ssh again - mdadm --detail /dev/md3 GET the UUID, mine is : bbe73c5c:694d1437:20f54790:be2b9bfb root@fs02:~# mdadm --detail /dev/md3 /dev/md3: Version : 1.2 Creation Time : Sun Apr 16 19:58:33 2017 Raid Level : raid1 Array Size : 2925444544 (2789.92 GiB 2995.66 GB) Used Dev Size : 2925444544 (2789.92 GiB 2995.66 GB) Raid Devices : 1 Total Devices : 1 Persistence : Superblock is pe
  9. One or more raid groups/ssd caches are crashed. I have a volume 3 that shows up as crashed. It had been working fine for more than a week I can accees it though (all the files are fine). I would like to know how do I change the HD/volume/raidgroup status. I actually don't know why it shows as crashed. hp microserver gen8 ESXI 6.5 3TB Hardrive, RDM, (Raw Device Mapping) 6.1.15047 Jun 1.02b ** Mdstat root@fs02:/etc/space# cat /proc/mdstat Personalities : [linear] [raid0] [raid1] [raid10] [raid6] [raid5] [raid4] [raidF1] md2 : active raid1 sdb5[0] 4
  10. Thanks that worked for me ! N54L + Proxmox 3.4 + XPEnoboot_DS3615xs_5.1-5022.3.img
  11. Thanks that worked for me ! N54L + Proxmox3.4 + XPEnoboot_DS3615xs_5.1-5022.3.img