• Content Count

  • Joined

  • Last visited

  • Days Won


sbv3000 last won the day on October 14 2018

sbv3000 had the most liked content!

Community Reputation

61 Excellent


About sbv3000

  • Rank

Recent Profile Visitors

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

  1. sbv3000

    Asrock DeskMini 310

    use the 1.02b loader for 3615xs, that should work with dsm 6.1.x. I think there are several threads indicating that the i219 nic isn't working correctly in 6.2 boots. I have a aliexpress NAS mobo with dual 219s installed and in my testing it didn't work with 6.2 loaders so I'm sticking with 6.1. That version of DSM is getting all updates and patches so imho is as good as 6.2.
  2. While you are testing, I would also disable the IDE, audio and 1394 devices in bios
  3. Check the tutorial for setting up an xpe boot drive. you can edit the s/n in the grub file as you would the vid/pid. you should be able to edit the grub file on the existing boot drive and on the next reboot it will load with the new s/n. I've run a few xpe boxes on at the same time with the same s/n and never has a problem. however note that I always use 'made up' s/n's that bear no relation to a real syno one (except the string format) as I dont use any features that need a real s/n.
  4. sbv3000

    USB stick freezes at boot.

    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
  5. There are a lot of threads where people have edited their synoinfo file to match the drive layout/internal/external. It will be trial and error for you depending on your hardware/controller setup. I think I would do some tests by setting internal to say 16 drives (0xffff) and the usb and sata to none (0x0000), then play with the binary/hex conversion until you get a match. Obviously do all tests with a spare hdd. For example if you set to 16 internal and your esata appears as say drive 15, adjust internal to 0x02fff esata to 0x10000 (if my conversion is right)
  6. Have a look at the synoinfo.conf file for the esataportcfg/usbportcfg/internalportcfg settings and you might need to edit them to match your drive/controller configuration so that the e-sata is seen as an external port. If set 'correctly' it might make DSM automatically mount a drive when plugged in
  7. sbv3000

    DSM 6.2 Loader

    if your system boots ok and is found on the LAN, then you choose the migrate option, retain settings. That will 'overwrite' the 6.1 install
  8. sbv3000

    Future for HP microservers?

    I guess it depends on what you mean by 'borrowed time' Synology seem to be pretty good at maintaining the two latest DSM versions (6.1 and 6.2) and providing update packs and fixes, they have also supplied a fix for a recent flaw in DSM5.2, even though that O/S is out of support and not being developed. Your borrowed time might well be the failure of the hardware before DSM is unsupported:) Syno may release a 6.2.x update that changes significantly the DSM setup which might cause issues with the loader that cant be worked around, but in that case just stick with the previous version. ATM I'm running some 5.2 boxes which are 'fit for purpose' using old AMD embedded mobos, and on my 6.1.x environment I can't see any major reason to go to 6.2, for me not enough of a feature improvement to do.
  9. You should be able to update directly to DSM5.2 using the 5967.1 image from the loader page. Ensure the pat file is the correct one from the Synology 5.2/5967 archive For DSM5.2 you don't need to make any changes to the USB boot device, just create your image. Once the machine is booted you can migrate, (keep settings or delete) then complete the update. Once that is completed you could look at updating to 6.1, and just follow the published tutorial 5.2>6.1. I would do a hardware test using a spare hdd and 6.1 loader to make sure you system is ok with 6.1 then connect you raid drives and migrate, but do a data backup either way before you start 'playing'
  10. sbv3000

    DSM 6.2 Loader

    It might be. Because its a software raid system the underlying hardware should not matter, provided all the disks in the raid can be 'seen' by the hardware and software. I would do a test with a spare HDD, set to IDE, install a test DSM/volume then swap to ahci. If you can still see the volume it should be ok for your raid. I would do a backup of you critical data though.
  11. sbv3000

    DSM 6.2 Loader

    you might need to switch the controllers to ahci mode
  12. sbv3000

    GA-Z68XP-UD3, install but then can't find after

    just to check, you can install fully to the test HDD with no errors (pat corrupted etc) and its only after the first boot with dsm installed that the box can't be found? try booting with the test hdd disconnected so that you are only using the 'installed' boot usb. If that fails to find, it might be that some drivers/modules on the usb are being 'overwritten' by the versions on the pat file, or the driver version used/installed into the DSM partition is failing. compare to a clean boot usb that has not been possibly updated I'd also try a 'minimal hardware' boot, by disabling all devices (sata controllers, usb's, audio, parallel, firewire etc) except for the onboard sata needed for the test hdd. Connecting a serial port for full boot diagnostics might give you more info on failing modules.
  13. sbv3000

    Can't get AsRock B360M-ITX/ac to work with Xpenology

    Try disabling the onboard audio in case that has a conflict with the nic resources. Also try the 3615 loaders and also leaving the mac address blank. if you have a usb/serial adapter you could try a serial port connection and check the loading process for drivers/modules. could also try a live ubuntu or mint boot and check the pci devices and check that the nic is on the supported/enhanced module list.
  14. sbv3000


    check the serial numbers of the drives as shown in Storage Manager and then have a look at the labels on the drives in the box to match up. I usually label by sata leads with the DSM drive numbers for diagnosing problems like this