Jump to content
XPEnology Community

Search the Community

Showing results for tags 'lenovo'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Information
    • Readers News & Rumours
    • Information and Feedback
    • The Noob Lounge
  • XPEnology Project
    • F.A.Q - START HERE
    • Loader Releases & Extras
    • DSM Updates Reporting
    • Developer Discussion Room
    • Tutorials and Guides
    • DSM Installation
    • DSM Post-Installation
    • Packages & DSM Features
    • General Questions
    • Hardware Modding
    • Software Modding
    • Miscellaneous
  • International
    • РУССКИЙ
    • FRANÇAIS
    • GERMAN
    • SPANISH
    • ITALIAN
    • KOREAN

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Found 5 results

  1. Just installed xpenology with dsm 6.1 (ds3615) with juns loader 1.02b on the PX6-300d (6 drive NAS). Pretty straight forward using this guide to boot from usb. GUIDE: Customer OS on PX6-300D 1) Had to plug the USB in the back usb port. 2) Entered the PID/VID/SN and mac1 and mac2 3) also required to enter: SataPortMap=6 After that it booted right up and installed DSM with the synology assistant. Working good so far with no issues and all 6 bays can be utilized.
  2. Dear all, I am trying top Install Xpenology on a spare desk computer that i have. I out in a sigle disk with 6TB capacity. I burned the image via Rufus on a USB Stick. The Stick boot correctly and the dsm installation start, but It stops at 95%. If i refresh the Page, the installation progress Starts again from 56% and stops 95%. There Is something that i can check to understand where and how i have made something wrong? Thanks in Advance for all the reply that i Will receive. 👋👋
  3. Dear all, I am trying top Install Xpenology on a spare desk computer that i have. I out in a sigle disk with 6TB capacity. I burned the image via Rufus on a USB Stick. The Stick boot correctly and the dsm installation start, but It stops at 95%. If i refresh the Page, the installation progress Starts again from 56% and stops 95%. There Is something that i can check to understand where and how i have made something wrong? Thanks in Advance for all the reply that i Will receive. 👋👋
  4. Bonjour à toutes et à tous 🖐️ Voila, j'aimerais installer une solution XPenology sur mon petit ThinkClient, dont voici les specs: CPU: i5 8400T RAM: 8Go DDR4 2666 CHIPSET: Intel B360 GRAPHIC: Intel UHD 630 S. ECRAN: HDMI, DP ETHERNET: Intel l219-LM (1Gbps) WIRELESS: Intel Dual Band Wireless-AC 8265 SATA 6Gbps (Vide) PCI-e NVME (un disque M.2 - 512 Go) INTERFACE: 3x USB 3.1 Gen 1 1x USB-C Gen 1 J'aimerais pour bien faire installer une solution NVR pour gagner des licences caméras, que j'intègrerais alors dans CMS sur mon Synology principale (RS3614xs+) - Que me conseillez vous ? - Peut-on envisager d'avoir une version DSM aussi à jour que les solutions legit actuelle ? (je suis actuellement en DSM 7.1-42661 Update 4) Merci d'avance 😀
  5. Trying to get an IBM x3650 M4 to work with this as baremetal. Here are the steps I followed so far. I am looking for anyone who knows what bootloader I should use (and the most recent compatible .PAT file). The current ones I am using obviously do not work with this hardware. I will list the hardware as I know it. 1. Intel Xeon E5 2620 (2 CPUs total) 2. The BIOS shows the drivers for Intel Pro 1000 Network adapter. 3. I have an LSI 9211-8i card installed with a single 8tb drive attached. 4. The system as 120 GB of RAM installed. 5. All onboard SATA ports are empty. 6. The Network Cards MAC addresses were listed in the BIOS, I have copied all four addresses from there for use in grub.cfg. Here are the steps I followed. 1. Using OSFMount I mounted the synoboot.img found in the file synoboot-ds918.zip, ensuring it was not read-only. Based on what I was reading this bootloader is 1.04b. 2. Edited grub.cfg a) created four entries for nic's, using all four MAC address copied from the BIOS b) Removed the ESXi boot option by commenting it out at the bottom of grub.cfg. c) Generated a serial for a DS916 and placed it within the correct location in grub.cfg. d) Found the PID, VID for the USB device to which I planned to write the IMG file and placed them in the correct locations within grub.cfg. This was double checked to ensure that VID and PID were put in the proper locations. e) Saved grub.cfg. 3. Wrote the resulting image file to the USB stick that I found the VID and PID values for. 4. Installed the USB stick into the hypervisor boot slot and booted the server. 5. It booted to the point where it said I should locate the synology using find.synology.com 6. I have the synology assistant on my computer so I used that to search for the device after waiting for awhile. I repeated the search after waiting again for about 3 minutes. No synology was ever found. I ran through the above procedure once before with the modifications required for ESXi and was successful in eventually getting synology going. The big issue with ESXi was that I could not get that system to recognize my 9211-8i adapter properly and see the drives attached to it (even though it was loaded, adapter showed in devices) it never showed drives.. but I digress. This is my attempt at using DSM bare metal on the same hardware and I'll just use DSM to power any VMs I may want rather than ESXi. I have several theories but the one that stands out is this: Is the NIC being detected by the bootloader and if not, is there a way I can get the NIC to be detected and working? Other question that may or may not be relevant are. 1. Does the updated 1.04b boot loader support the hardware I have listed above? 2. If the bootloader does NOT support it, what is the latest bootloader I should try and the corresponding version of DSM that would work? 3. If I should try a different bootloader and DSM are there any modifications I should make to my steps above (aka things known not to work). What I mean by this is that during my reading I have seen that some bootloaders had problems with multiple NICs but I saw that was back at 1.02 so I assumed such problems had been resolved by 1.04b, hence my use of 4 nics. I am not looking for someone to essentially do this for me, but rather someone who might know where I am going wrong and point me in the right direction and I most certainly want to thank anyone who takes the time to read this and respond. Thanks, Wizengamot
×
×
  • Create New...