Jump to content
XPEnology Community

Diverge

Member
  • Posts

    355
  • Joined

  • Last visited

Everything posted by Diverge

  1. Boot them up in a linux system and see if you can use your array. DSM is a PITA when it thinks it's crashed, and it really hasn't. edit: check from SSH if the volume is still accessible before trying the above... I've seen DSM say an array was crashed, but yet be working via a terminal session.
  2. Verify that you are actually on 5055. I saw same exact error messages when I had updated to the 5055 bootloader, but hadn't upgraded the firmware DSM. Soon as I upgraded DSM, they went away.
  3. I actually did it the same way.. Initially I picked the install/upgrade option... but for some reason it did a full boot.
  4. I don't see 5055 on synologies servers... have they taken it down for some reason? I don't need it, just curious why it's MIA all of a sudden.
  5. +1 I was going to post a suggestion earlier. But I like yours.
  6. XPEnology is based on one of the higher tier models that uses an Intel x86-64 cpu, so you won't be able to use it on arm.
  7. depends on what you do with your NAS. If you use Plex, and transcoding, more CPU power is better. DSM doesn't really use more memory, at least with the things I do with it.
  8. The board comes with the CPU under a passive heatsink and I do not overclock the CPU.. Synology report a temp of 40-42°C so I do not think it is heat... I do have the only fan at the motherboard room in a exhaust configuration, so might be worth it to change it to a intake fan... Thanks for your input The temp that DSM reports either isn't accurate, or isn't the CPU temp. It might be another motherboard sensor... mine always reads ~40C. I've got a fancy server motherboard, and I can read the real CPU temp via a web browser, and it doesn't correlate at all.
  9. You should be able to get them directly from DSM. Change the firmware update settings so it only includes minor update, not major ones.
  10. No issues here with Plex Server on my system. Are you sure it's not related to your router, DHCP, ect?
  11. +1 I'd like to see this as well. I'd welcome a newer version of mpt2sas
  12. You don't need a new tutorial, or to redo everything from scatch. Setup ESXI, setup the boot image, create a virtual disk for testing.... get everything working, remove test disk, insert array. It should be seamless if you do everything correctly. Moving your array from physical hardware to esxi, and vise versa is doesn't require any special steps. It all comes down to the boot image, and your hardware working correctly with esxi. If you're not familiar with esxi, set your array safetly to the side and play with physical test disks, or virtual disks. And read a lot.
  13. it's a .spk... install it with package manager...
  14. https://forums.plex.tv/index.php/topic/ ... ver/page-4
  15. Do you have anything to compare it to using the same hardware? Previous versions, bare metal, ect. I have no experience with virtual disks for real storage (have only done tests with small vdmks). Most of us that use ESXI don't use virtual disks, we passthrough the controllers for our storage using direct I/O (VTd), or RDM.
  16. Seems odd a built in GPU will prevent ESXI from booting; it's pretty much headless. The aspeed controller isn't a regular GPU, it's for IPMI and remote desktop access. It's used in the Asrock board in my sig, and worked great for me (it's not used by ESXI, the Intel GPU in my CPU is).
  17. I never use the Synology Assistant software. I always use the webclient at the IP address of the DSM's VM. If you only have access to the IP for managing ESXI, then why not install windows/linux in a VM and use the console of that VM to open up a browser at the IP of the DSM VM, or use the Assistant software (if you go with windows)?
  18. It's not gonna work until Vortex finds workarounds to the new protections they add every version. He also usually doesn't release stuff for beta releases, so they don't change it up. It's a cat and mouse game. Pro tip, read the russian forum section (I use google translate in chrome). So just sit tight, and wait for the final releases, and read if you want to
  19. reflash whatever image is on your usb flash drive.
  20. Open a ssh terminal, or via console, and do the following (replace sda with your drives letter): synodisk --read_temp /dev/sda synodisk is the util used by DSM to show drive temps. Then try: smartctl -a /dev/sda |grep Temperature this is just smartmon tool. synodisk needs real access to your HD to report temps, only works with baremetal and VTd (passthrough), doesn't work for RDM. Smartctl should report drive temps for all 3 (baremetal, VTd, RDM). If smartctl reports a real drive temp, and synodisk doesn't, then DSM doesn't like the controller you passed through for whatever reason. If smarctl doesn't report a real temp, then I guess it doesn't like your controller either or it's a driver issue. as far as the wierd drive still showing up, you edited your syslinux.cfg wrong. Plus, you have your bootloader as a SCSI drive, so adding rmmod=piix_ata won't help (I don't think). I use IDE for the bootloader. Here's an example: UI menu.c32 PROMPT 0 TIMEOUT 50 DEFAULT xpenology MENU TITLE XPEnoboot 5.1-5022.1 LABEL xpenology MENU LABEL XPEnology DSM 5.1-5022 KERNEL /zImage APPEND root=/dev/md0 rmmod=ata_piix ihd_num=0 netif_num=4 syno_hw_version=DS3615xs sn=B3J4N01003 vid=0x0EA0 pid=0x2168 loglevel=0 vga=0x305 LABEL debug MENU LABEL XPEnology DSM 5.1-5022 Debug KERNEL /zImage APPEND root=/dev/md0 rmmod=ata_piix ihd_num=0 netif_num=4 syno_hw_version=DS3615xs sn=B3J4N01003 vid=0x0EA0 pid=0x2168 loglevel=0 vga=0x305 debug=1 console=ttyS1,115200 LABEL install MENU LABEL XPEnology DSM 5.1-5022 Install/Upgrade KERNEL /zImage APPEND root=/dev/md0 rmmod=ata_piix ihd_num=0 netif_num=4 syno_hw_version=DS3615xs sn=B3J4N01003 vid=0x0EA0 pid=0x2168 loglevel=0 vga=0x305 upgrade=5.1-5022
  21. This may or not be helpful, but look into how people got Xenserver working; as I think I remember it having a an issue since it used /dev/xvda. Start here viewtopic.php?f=15&t=3001 from there are links to other posts/threads. Good luck!
  22. Hibernation upsets can be caused by lots of stuff. Apps you installed in DSM, network shares, ect. As far as your one weird drive, it's probably the bootloader image for you XPEnology VM. For every ESXI VM of DSM I've had to add rmmod=piix_ata to the kernel line in syslinux.cfg of the bootloader, or it will show the bootloader drive as a disk within DSM. If this is the case, then it's also why it's temp is -1C (because it a virtual disk).
  23. Use Plex, it's much better, and transcodes
  24. I make a script file; ex; check_link.sh chmod 755 check_link.sh an then schedule a task to run every few hours in DSM. #!/bin/sh STATUS=$(ping -q -c 4 192.168.1.1 | grep -o '4 packets transmitted, 4 packets received' ) if test "$STATUS" = "4 packets transmitted, 4 packets received" then echo "$STATUS" else /etc/rc.network restart fi Replace the IP address with your routers IP. You could just try running the code from DSM task, and bypass making the script file, but I haven't tested it that way. I forget what the message says when you lose the network connection and try to ping your router, but it would probably be better to do the 'if else' on that message.
  25. That happened because you basically had 2 sets of disks with synology on it (your original array), and the single disk you were testing on on your other system.. so it probably booted off the DSM on the single, saw all those disk from the array and wanted to migrate them... when you really wanted to boot off the array, and add the single disk. Next time just delete the partition tables of any disk you want to add into your array, since if it also has an DSM install it will get confused. Or put the disk in after DSM is booted (if you have hotswap), then it can't boot off it
×
×
  • Create New...