Jump to content
XPEnology Community

sbv3000

Moderator
 View Profile  See their activity

  • Posts

    1,061

  • Joined

  • Last visited

  • Days Won

    10

 Content Type 

Everything posted by sbv3000

  1. sbv3000
    I think the 1b4b:9235 class 0000 device is another 4 port marvell sata controller - might there be some testing/work to sort out 3 controllers (4+4+8?) sataportmap settings maybe or adjust drives to 16? Also, I spotted this page about the sas driver not binding, not my area of expertise, but maybe it gives a hint? https://github.com/ArchAssault-Project/archassault/blob/master/packages/linux-archassault/mvsas-Recognise-device-subsystem-9485-9485-as-88SE94.patch Also, I wonder if it may be worth disabling spare devices (second serial port, additional USB etc) in case there are resource conflicts between devices, maybe the XPE/DSM driver/module wont load in 'shared' space? I'm using several mvsas driven (supermicro AOC) cards with 5.2 and 6 (with @IG-88 enhanced extra.lzma) and they work fine - maybe try 5.2 just as a test/diagnostic?
  2. sbv3000
    I think its made in China by USI, but re-badged to Terastation? I'd imagine there should be a boot option to access the disk controller bios and set that up. Probably set to raid and needs to be jbod/IT/Passthrough. Found a manual, page 32 might give a pointer:) TS-7120R-35012398-03_EN.pdf
  3. sbv3000
    The router supports DDNS so setup a (free) service on that, then open the necessary ports to access the system. To be more secure you could use 'port translation' rather than standard DSM ports or (even better) setup the DSM VPN server and connect with a client - that way you only open one port for the VPN server service.
  4. sbv3000
    cloud station might also need tcp port 6690 open. also have you enabled on the server the folder to allow sync
  5. sbv3000
    There are no alternative loaders to the 361x and 916 I recall a forum member reporting similar quirks when XPE/DSM was installed on a a Thecus NAS. I think it turned out that the features were related to hardware/syno software being linked so they didn't work on non-syno kit. Having said that, there are other people using the F2-220 so have a look through their posts for any support. Also, I think there are some people have created fan control and shutdown add-on packages so have a search for them. disk spin down normally works so have a look at any services or features that might be keeping them alive
  6. sbv3000
    Same thinking here which is why I suggested audio station. the remote end needs some sort of client/amp and not sure how an audio card solves that (unless cables are being run to various remote amps )
  7. sbv3000
    If you repair the system partitions first, then repair the array with disk one and finally do the file system check you have a good chance of getting everything back. I would take a backup before the fsck (you can do this while the volume is rebuilding) . Playing around with the drives in Windows could have had some effect. You can do smart tests in DSM Storage Manager btw. As you found, if a drive is removed from an array and the system booted up without it, it will degrade the volume. Even if you put the drive back that was part of the volume, it will be seen as a disk thats not part of it - just as in your case.
  8. sbv3000
    I'm not sure this will work for you exactly, but have you looked at Audio Station and setting up multiple devices for multi room setup? Might be easier than compiling etc
  9. sbv3000
    Hi welcome to the forum There are several options to access the NAS over the internet with port forwarding or other ways What make/model router do you have? What do you want to do with access via the internet?
  10. sbv3000
    Sorry I thought when you said VMWare you meant ESXi (its a VMWare product) so would now guess you mean VMWare Workstation or Player running on your Windows HTPC - 6.x should work ok if you follow the tutorials.
  11. sbv3000
    Not done this myself but I'd imagine you could use some standard tools to convert the hyper-v to ovf and import that into esx. there could be a number of risks/issues with transferring so it might be 'simpler' to setup an esxi host (or bare metal), create a new 5.2 instance and backup/restore between systems, then update to 6.x
  12. sbv3000
    there are ways to speed up the process, https://adamroe.me/blog/shr-rebuild
  13. sbv3000
    You can work out the devices from this sort of data/site http://pci-ids.ucw.cz Of interest could be the 0106 class, 1b4b:9215 looks like there may be 2 marvell controllers, and also an intel celeron sata controller 8086:22a3. My guess is that the 8 drives are on the marvell controllers and its the intel giving the ghost ports. Probably qnap o/s does not include drivers for the intel so they are not in use, but XPE/DSM loads generic sata drivers and they show up. Disabling in bios (if you can find it) is I think the only option. BTW, check your hex settings for the internal drives, although you are seeing 13 in DSM your hex fff is 12 drives, not sure how this is working correctly
  14. sbv3000
    I'm investigating a similar issue with an old mobo of mine, see this thread; If you can, have a look at the bios to see if there are any other controllers or hardware that could be interpreted as a drive (firewire etc) and disable. Also, as mentioned in my thread, look at the pci devices and modules loaded, that might give a pointer. The weird thing on my system is that with all onboard sata disabled I still see hdd 1-4 slots as empty. I'm sure this has something to do with pci bus/enumeration but why 'phantom' slots in a random order, not found the answer yet
  15. sbv3000
    Broadly speaking from my knowledge I would say the answers are; Remote access - SSH or weblogin from outside network? - Yes provided you setup the right services/port forwarding etc Streaming media and uploading to the NAS from external network? - Yes - ditto VPN services in torrent client? - Yes - can should be able to create a vpn client connection and set torrent services to use it Virtualization on the xpenology os? - Yes - depending on hardware Webserver? Yes Plex/Streaming- Yes plus there is a native DLNA server and various apps pfsense - not sure myself - dont think so, it may be an option to setup ESXi on your hardware and install VMs of XPE/DSM and pfsense
  16. sbv3000
    Thats an interesting find - well done, lets see what beasts it lets loose From my earlier tests, I suspect that your analysis of the SES services is what Synology use with real systems so it allows the 4 letter allocation as with my DX unit. The next challenge will be finding a solution to retaining the extensive synoinfo.conf changes that these setups need to avoid raid crashes during upgrades.
  17. sbv3000
    The Lenovo machine should be compatible okay. The 'Screen will stop updating' is normal behaviour. Things to check; You have correctly edited the usb vid/pid settings Update the extra.lzma file with the enhanced version (4.1) by @IG-88 Connect the serial port to a PC and check the boot loading logs via a Putty session - you can see lan modules loading and dhcp/ip address logs
  18. sbv3000
    If you clean install a new hdd with 1.02b loader on some spare hardware, then update DSM to 6.1.3, that will also 'write back' to update the loader so everythings at the same version. You can then use that loader the production box with less steps to
  19. sbv3000
    'Backup' between XPE/DSM versions is fine From 5.x to 6.x On the 6.x machine, enable Rsync in File Services On the 5.x machine create a backup destination in Backup & Replication to the 6.x machine ip address (synology rsync) Create a backup job to that target From 6.x to 5.x On the 5.x machine enable Backup Services in Backup & Replication On the 6.x machine, create a data backup in Hyper Backup to the 5.x machine. Choose 'Remote Data Copy', (NOT Remote Synology NAS) for compatibility
  20. sbv3000
    It depends what you mean by 'update'. Applying any 'update' could make a change that causes instability - just look at some Windows updates that have 'bricked' machines. However, I think that with XPE/DSM, is you are updating within a version - eg an update pack, that would be low risk, however a version change or loader change would be more more risky as there could be driver/module changes, missing modules or changes to security settings on files. A good approach would be to always test an update on your hardware first with a spare disk, (disconnecting your raid drives) and checking the forum for members reporting updates and testing on similar hardware. You could also look at an offsite backup, for example, Amazon drive is unlimited for around £50 a year and you can setup to sync selected folders from DSM6 also encrypted
  21. sbv3000
    Have a play around with the SMB settings in File Services, older versions have been depricated but if there is a mismatch with your clients it could cause drop outs I guess
  22. sbv3000
    Its expected behaviour, check out the FAQ 11
  23. sbv3000
    Check your hardware spec and the embedded nics to make sure they are supported, and maybe use the enhanced extra.lzma by @IG-88. Others are having issues with the perc hdd controller , but network is ok. Also have a look at the system status through the onboard console, and make sure you have not connected that network port and nothing else
  24. sbv3000
    You could look at running an snmp monitoring tool like paessler prtg, there is a free version, that can collect a lot of data from the nas. also have a look at whats happening on your network, there might be another device thats causing a lot of traffic, also the synology AV if thats running, maybe disable or whitelist files. This patch was to fix wireless security flaws but maybe also covered other things, that might be network related. if you are using media server package, check the indexing and also ssdp and device reset.
  25. sbv3000
    You will probably need to set the raid controller to 'non-raid', 'jbod' or 'passthrough' (which ever is applicable terms for the setup) then you create a raid in DSM. I think the on board raid is adaptec, check the drivers in 6.0.2 as you might need to use the additional extra.lzma file from @IG-88
×
×
  • Create New...