sbv3000

Moderators
  • Content Count

    996
  • Joined

  • Last visited

  • Days Won

    10

sbv3000 last won the day on October 14 2018

sbv3000 had the most liked content!

Community Reputation

73 Excellent

About sbv3000

  • Rank
    Guru

Recent Profile Visitors

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

  1. Hi All I checked the forums for mention of these and there are a couple of archives from way back. I like to keep away from 'licence' issues with my XPE boxes but see a lot of people using Surveillance Station with hacks. There is a possible good alternative to SS that runs in Docker and seems to work well and no syno licence requirements. https://www.ispyconnect.com/download.aspx I didn't use the docker script, instead this docker guru has created a registry package doitandbedone/ispyagentdvr Once installed and runni
  2. Just as a follow up to this I connected an old 137GB SAS drive to the controller and it shows up ok in Storage Manager and the demsg output is; [ 19.258492] drivers/scsi/mvsas/mv_sas.c 1079:phy 3 attach dev info is 80001 [ 19.258494] drivers/scsi/mvsas/mv_sas.c 1081:phy 3 attach sas addr is f90ad50e00c50050 [ 19.662485] scsi host4: mvsas [ 20.762159] drivers/scsi/mvsas/mv_sas.c 277:phy 3 byte dmaded. [ 20.762268] sas: phy-4:3 added to port-4:0, phy_mask:0x8 (5000c5000ed50af9) [ 20.762275] drivers/scsi/mvsas/mv_sas.c 1116:set wide port phy map 8 [ 20.812335] sas:
  3. Hi All I'm testing some hardware before updating my 'prod' systems J3455 itx board and Intel add on nic 1 drive attached to mobo onboard sata 1 DS918+ boot loader created/installed DSM6.2.3-25426 and U3 to the mobo drive - all working fine Replaced extra.lzma and extra2.lzma with @IG88's driver extension v.0.13.3 files to boot loader partition Added Supermicro Marvell 98SE6x sas controller with 2 (sata) drives attached Booting system the 2 drives are visible in the Marvell bios DSM Storage Manager only shows the 1 drive attached to the
  4. This website seems to suggest the 6tb drives are not compatible with the d70 http://findhard.ru/en/checkcompatibility/part?partType=Drives&id=17597&model=seagate-6-tb-st6000nm0034
  5. 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 a
  6. 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
  7. 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
  8. 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
  9. 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
  10. 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
  11. 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
  12. 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
  13. 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.
  14. 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.
  15. 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 I