sbv3000

Moderators
  • Content Count

    972
  • Joined

  • Last visited

  • Days Won

    10

sbv3000 last won the day on October 14 2018

sbv3000 had the most liked content!

Community Reputation

62 Excellent

3 Followers

About sbv3000

  • Rank
    Guru

Recent Profile Visitors

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

  1. 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)
  2. Dont waste your time, just use openmediavault that has a loader for rpi and does everything dsm does
  3. 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
  4. 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)
  5. 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?)
  6. 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.
  7. 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
  8. sbv3000

    DSM 6.2 Loader

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

    DSM 6.2 Loader

    can you post some info about your hardware?
  10. 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.
  11. 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.
  12. you should be able to login to the console as 'root' and 'your admin pw' to check the files and or if you have telnet enabled use winscp to check directories, assuming the box has an ip address (pingable?) if you have a spare hdd then disconnect your raid, boot with that connected and install dsm with same station name/admin pw but no volume, on reboot check for same errors (dodgy usb, try a new one?) but if the clean dsm works ok then leave that hdd attached to channel 1, reconnect other drives and boot, the 'good' system partition on channel 1 should repair the array disks you can then disconnect spare hdd etc. maybe look at updating to 6.1/6.2 as well
  13. If by 'backup' you mean you just want a NAS to act as an rsync or hyper backup target, the I'd go for the lowest power compatible setup. Looking at your parts list some of the mobos seem to be embedded cpu, that might be a start, but maybe do a hardware test with your chosen DSM version, for nic and sata controllers working, then go from there
  14. Seeing as it shuts down with 2 ssd, maybe there is some weird issue where the temp sensor is combining the values both drives are reporting and if SSD1 temp + SSD2 temp > trigger point then shutdown? No idea where that value might be in XPE/DSM but maybe worth investigating. also, have you thought about some monitoring via an SNMP app (eg Paessler PRTG), you can get a lot of drive/device stats through the syno built in mibs and standard device mibs with that app, might give you some extra data to help diagnose.
  15. There are several threads on downgrading from a failed upgrade, can be done by editing various config files and migrating, or (my favourite method and easier imho) is to build a clean XPE/DSM install on a spare hdd and allow that drive to 'repair' the system, here is one thread with the process