• Content Count

  • Joined

  • Last visited

  • Days Won


sbv3000 last won the day on October 14 2018

sbv3000 had the most liked content!

Community Reputation

64 Excellent


About sbv3000

  • Rank

Recent Profile Visitors

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

  1. Check this thread for native boot loader drivers and additional module you might need for the megaraid controller. I would do a ground up check of all the hardware for compatibility, plus what you might need to do in the bios to setup internal sata controllers versus the megaraid. Also, you probably need to set the megaraid bios to jbod/IT or basic adapter mode. If its set to hardware raid, its unlikely that XPe will have the modules. There are several forum threads where people have setup XPe on supermicro servers so check them out too.You might need to edit synoinfo.conf to get the system to correctly see internal/external sata ports
  2. have a read of this older thread on drive limits, addressing and the possible fixes. You will always be faced with having to reedit the synoinfo.conf after a boot loader upgrade or change
  3. The boot loader USB should be left connected to the NAS all the time or it will fail to boot as you have seen. Its also best to disable all other boot devices except the USB in bios
  4. error 35 probably means you have not set the vid/pid correctly for your usb device, check that again. Not sure what you mean by the .pat file being on the usb, the install process is normally boot with usb then upload/install from the .pat file on local PC drive. Maybe the error 35 is because you are trying to read from the USB which is nominally just a boot loader? make sure the .pat file is the correct one for the dsm version on the boot loader, if its not then may also fail, also make sure you are 'manually' installing that version Another thing to check is your raid controller settings, normally raid controller is set to jbod/it mode and let dsm handle the raid (softraid)
  5. Dont waste your time, just use openmediavault that has a loader for rpi and does everything dsm does
  6. I would suggest a 'test' with the 1.03b loader for ds3615. Follow the tutorial to create a NEW usb boot disk for this loader, ie dont use your existing boot usb. Check the forum for posts about the 1610 G8 and any issues, bios settings etc Ideally you should somehow backup your critical data before the following; Disconnect your raid drives Connect a spare hdd Boot with your new loader, check device is found on LAN Install DSM to the spare drive, create volume, user account, shared folder, install/test the packages you use, and also any services you use (ftp, samba, rsync etc) When you are happy that everything 'works', Shutdown disconnect spare drive reconnect raid disks boot with OLD loader to check everything ok, shutdown swap to new boot loader Boot and install/migrate to the chosen DSM
  7. As you are trying to 'restore' a geniune synology unit, have you looked at their forums? There may be advice there. I dont speak Russian but looking at the thread there are links to a 1511 boot loader and how to edit the mac/serial (it looks to be the same process as for creating an xpe boot loader - of course If you could find the loader for the RS you might be able to 'reflash' the module. Also, if you have connected the DOM to a PC, have you looked at editing it using ofsmount and the hex editor and re-add the serial (which should be on a label on the unit)
  8. what does the synology assistant say when you search for the unit on your lan? if you can see serial and mac then it should be ok. Looks like the unit has vga and com ports on the rear next to the usb, you should try a monitor on the vga. also have you contacted synology to see if they could supply a replacement dom (assuming it can be replaced?)
  9. Yes this should work, I've done the same for xpe testing purposes. Drives might show up in a strange order depending on pci slots and internal controller setup but otherwise ok.
  10. sbv3000

    DSM 6.2 Loader

    If you have followed the usb setup guide to open and edit the boot loader and change vid/pid etc, then its the same process, but you access the partition with the extra.lzma file and copy the extended version over it
  11. sbv3000

    DSM 6.2 Loader

    probably missing the atheros driver and you need to use ig-88 replacement extra.lzma driver extension
  12. sbv3000

    DSM 6.2 Loader

    can you post some info about your hardware?
  13. sbv3000

    DSM 6.2 Loader

    Just follow the same process as described in the install/upgrade tutorials for 6.1, but using the bootloader for 6.2, for your hardware/model Before you attempt to upgrade, disconnect your raid drives and do a thorough hardware test and complete installation using the 6.2 loader onto a spare hdd. Once you are happy your hardware is all ok then you can boot/migrate your system. Data should be backed up of course.
  14. As mentioned in the FAQ, the XPE community discourages using genuine sn and macs as its a breach of Synologys terms of use. Also, its known that all syno installations (real or XPE) regularly 'phone home' to various synology servers so its possible that calls from two different external IP addresses from 'the same' device might be an issue, just what I wouldnt know, but most probably if your friend is using quick connect it could be.