Search the Community

Showing results for tags 'baremetal'.



More search options

  • 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
    • CHINESE
    • HUNGARIAN

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


About Me

Found 7 results

  1. Hello I am trying to fix problems with smart information retrieval. The DSM ui works perfectly and I created successfully a 8 drive raid6 but I cannot access smart info and the log is filled with failure messages. The log can be found in the attachments. debug.log
  2. Hello, I am looking to build a Xpenology but am hesitating on installing on bare metal or VMware ESXI 6.7 to replace my DS916+. I would like to use at all time as a NAS as a massively used file server where Moments will be running and casually use VMs (Win10, WinServer & Ubuntu). I know we can use VMs on Synology. That is why I am hesitating. My specs: Intel Xeon E5-2630LV3 (8cores 16threads) Fujitsu 32GB DDR4 ECC 2400mhz Kllisre X99 LGA2011-3 motherboard from Aliexpress 2x WD Red 8TBs (Dedicated for the storage) 2x WD Red 6TBs (Dedicated for the storage) 2x Samsung NVME 256GB SSD PM981 (for the cache) 1x Toshiba Sata 256gb SSD (for the VMware ESXI installation) 1x 2.5 GBE Network interface 1x 1GBE Network interface 1x APC Back up UPS My aim is to have the less problem as possible while the best stability, security, and performance as possible. Requirements: Have at least 18TB with, for example, SHR Have redundancy SSD Cache (NVME maybe?) PS: All my data will be backed up to my GSuite account with HyperBackup. Many thanks for your precious advice!
  3. Hello, Did some of you found how to get the DSM (6.2.2+) restart and shutdown functions to work correctly? Is there something related to BIOS version(s) or settings? Or the issue is in the DSM software itself? I've updated successfully to 6.2.2-24922-3 on bare-metal systems (both with 1.03b bootloader & DS3615xs and additional HP NC365T Quad Gigabit Intel NIC): HP Microserver G8 with latest BIOS (04/2019). Tried No C-States setting at CPU power management, but behavior is the same HP Microserver G7 N54L with modded BIOS 041 (2013, Kamzata version). I've tried ACPI 1.0/2.0/3.0 with no success. C1E and PCI-E power management were already disabled (no worky without them disabled) I've seen many users with successful bare-metal updates and wanted to ask if anybody knows more about the shutdown/restart issue... Thanks, Chris
  4. Guten Morgen zusammen. Mein System: N54L Baremetal, DSM 5.2-5967 Bei mir läuft bereits eine virtuelle Maschine mit Win 7 Pro. Mein alter Scanner unterstützt zwar kein "Scan to folder", aber auf einem laufendem PC, mit der Scanner Software, konnte man dann einen Ordner definieren, wo dann sämtliche gescannte Sachen landen. Daher Virtualbox. Läuft. Wunsch: In Virtualbox eine MacOS mit High Sierra zum laufen bekommen. Problem: Die *.dmg von High Sierra lässt sich nicht zum installieren bringen. Habe die *.dmg in eine *.iso konvertiert. Das selbe Problem. Bleibe im UEFI hängen. Mit "exit" komme ich zwar raus und kann auch im Boot device Manager die CD auswählen, aber die überall erwähnte uefi zum booten finde ich nicht. Mache ich etwas falsch oder funktioniert es mit unserem treuen N54L nicht ? Grüße
  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
  6. I am trying to figure out why my smart info is not displayed in the Web UI. As it can be seen in the images attached the web UI give an error while if I login into the shell I can query S.M.A.R.T. info.. Anybody has a clue?
  7. Hi, Since I have updated my HP n54L to DSM 6/6.1.3, I was unable to reboot. When I reboot, the nas shutdown and boot but still on booting the kernel and nothing happens, no HDD led blinking. I have to shutwon it manually and boot it. There is a way to enable verbose on the bootloader to identify the issue or maye be there is a log for booting part? Thanks.