sbv3000

depending on your dsm version, the the 'admin/root' account will have been disabled, but you should be able to telnet/serial to the device with the account you created as your replacement 'admin' account and its password. you might be able to get a basic network connection with a wifi dongle add on, to help diagnostics, or backup

I run real synology and xpe boxes and 'like' the gui too, but you have to be prepared to put some effort into getting an xpe nas working. if you like a 'simpler' gui, have you looked at openmediavault? Thats my 'next best' nas to dsm, I found freenas setup overly complicated you could try plex, jellyfin or ready-dlna plug ins

try disabling the onboard sata controller, if all disks appear then it might mean the correct idxmap and portmap will give your the full 12 disk with both controllers. you might need trial and error. also, test each sata port on the add on controller with a drive attached, 4 or 5 may work but if the controller uses a multiplier, the 6th channel will probably not work and if you connect a drive to it may cause the 5th drive to 'disappear' too.

can you post some info on the hardware you are using, mobo etc. if w10 isnt seeing the controller then it looks like a mobo/bios/slot issue, as you are thinking. might be a pci bus issue, you could try disabling any unnecessary devices to make sure the pci controllers are not contended, like I said in that old post. I guessing you have done the basics on the controller to flash to use IT/jbod mode etc.

I would do a full hardware compatibility test before your attempt to upgrade; Create a new XPE boot USB with the version of DSM you plan to upgrade to. Disconnect (power and sata) your raid drives Connect a spare HDD to first sata port Boot with new USB, check system is found on network Install DSM, reboot, ensure all is working and you can connect/login after reboot If the above all works ok you can reconnect your raid drives, boot with the new USB and 'migrate' You might need to add the additional drivers/module extra.lzma created by IG-88 Also make sure you have backed up critical data and checked the forum for other people using Gen 8 for any tips

check this https://www.synology.com/en-us/knowledgebase/DSM/tutorial/Service_Application/What_websites_does_Synology_NAS_connect_to_when_running_services_or_updating_software you could look at your syslogs and see if its working correctly

Why do you want to preserve the install? If the hardware is working with this bootloader, then it may be easier to boot with a live linux disk or gpartd, erase the drives and start afresh. You dont know what data may be on the drives, including malware or other nasties that could put yourself at risk. otherwise your could try this but I dont know if the flaw is patched in recent dsm https://wiki.mbirth.de/know-how/hacking/synology-telnet-password.html

https://www.synology.com/en-global/knowledgebase/DSM/tutorial/Storage/How_can_I_recover_data_from_my_DiskStation_using_a_PC

Sounds like you may be right on the compatibility, there could be a firmware update worth a check, plus also see if it is stable on one of the non-lsi ports. Regarding the PSU, I'd also think it beefy enough, but you could try turning off hibernation, it might be that on spinup if there is a 'blip' between controller and disk it could cause a crash

Im not clear if you are running ESXi for 'other' VMs than an XPE NAS, if not then why not try XPE as the O/S and see what happens. Other things I'd try would be to disable the non-LSI SATAs and move the ESXi SSD boot drive to channel 1 of the LSI array and boot from that if possible. or maybe put your ESXi on a USB or DOM and boot from that, again disabling the non-LSI sata. Both these options mean no need to alter the synoinfo conf I'd also disable all hardware you dont need like the serial ports. How are you setting up your data store(s), single drives or attempting to create an SHR by presenting the passthrough drives to XPE/DSM? Have you done a physical mapping of ports on the board vs the drives/channels connected, checking how they are seen by DSM in Storage Manager. That can help diagnostics

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

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 https://xpenology.com/forum/topic/8057-physical-drive-limits-of-an-emulated-synology-machine/page/2/

Maybe try docker and and youtube-dl?

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

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)

Dont waste your time, just use openmediavault that has a loader for rpi and does everything dsm does

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

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)

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?)

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.

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

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

can you post some info about your hardware?

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.

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.