sbv3000

Moderators
  • Content Count

    992
  • Joined

  • Last visited

  • Days Won

    10

sbv3000 last won the day on October 14 2018

sbv3000 had the most liked content!

Community Reputation

67 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. I've only used HA mode on real Syno kit so no direct experience of this with XPE, but I'd look at the following; Serial numbers and MAC addresses being 'genuine' (bearing in mind that the XPE community discourages using genuine numbers on XPE) S/N and MACs aside, Try a test with and XPE 'Master' and real Syno 'slave' to see if it works Then vice versa. Might help eliminate if there is a hardware issue Check the system logs in either case Depending on your hypervisor lab setup, are your VM's HA NICs on the same physical NIC or separate? There might be an underlying issue with that so try different NICs I think the best way to prove this would be physical kit rather than VMs, even older hardware if you have spare kit, before you buy new. Also try the 3615 boot loader and lower boot versions. About moving between real syno and XPE, provided you have fully tested your XPE hardware then it should work, however if your real DSM version is higher than your XPE boot build you might need to 'migrate' and reinstall DSM .pat file and then update to the version you have. If its a major build difference you might need to force a downgrade by editing various config files or creating a clean install HDD and adding your array drives afterwards and repairing the system partitions. All this presumes you have good, verified data backups of course! Which, for me prompts another question. If you are currently running an HA real Syno environment, I'm guessing this is business and critical environment, so should you be considering using a 'hacked' O/S like XPE that is community supported and could expire at any time, should for example, Synology lock down the O/S.
  2. You may have fixed this but my comment about 3.3v is that 'some' drives have strange behaviour if powered with the 3.3v supply as well as the usual 5v and 12v. so try sata power connectors without it (the orange lead), alternatively make sure all drives either have it or not, ie not a mix
  3. I would try; disable all onboard devices that you are not using/needed eg audio, usb3. manually setting memory speed to match clock rather than 'auto' Enable disk activity logging and check the system logs following a crash to see if there is a log centre event near when it happens. If you are running any SNMP monitoring, you could use the syno mib to check lots of system resources in real time and see if something is triggering the reboot. One last thought, recreate your usb boot loader on a new drive
  4. My odd thoughts are; Mix of sata 3 and sata 2 channels, maybe a cache/speed issue, disable or enable cache in storage manager? Power supply 3.3v connectors, or not, all drives powered with or without these? Check if drives/PSU are in conflict with 3.3v options, hibernation etc
  5. a silly idea perhaps, but could you remove your raid disks, boot with no disks and see if the network is ok? not sure of the boot process but imagine that with no disks the unit boots with dom based drivers for 'basic' connectivity, but once DSM is installed it uses drivers from the .pat file. if the DSM driver is 'corrupt' then fails to load. Above could also identify if network hardware has failed? Next step would be to install DSM to a spare/new HDD, check that works, if so you just need to 'repair' on the raid drives
  6. just search for 'sataportmap', there will be lots of posts, here is one example grub set sata_args= 'SataPortMap=6' # sata controller, values: 6 - 1 controller on 6 ports; 22-2 controllers on 2 ports; 42-2 controllers, the first on 4 ports, the second on 2, etc. in your case the sataportmap could be 426, 246 66 depending on how the onboard and add on controllers are 'seen' in bus order but it look like the xpe/dsm will only 'see' 4 ports due to the multiplier no matter what you do
  7. 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
  8. sbv3000

    Help newbie

    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
  9. 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.
  10. 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.
  11. 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
  12. 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
  13. 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
  14. https://www.synology.com/en-global/knowledgebase/DSM/tutorial/Storage/How_can_I_recover_data_from_my_DiskStation_using_a_PC
  15. 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