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've not set up a Thecus with XPE/DSM but I think you are on the right track 1) Connect monitor/keyboard and if possible serial port (I recall most Thecus boards have a serial header) 2) Boot and see what default video output and bios options you get 3) Remove the DOM and see how the boot process goes vs 2) 4) Try a test boot with XPE/DSM5.2, thats less fiddly to setup and has more built in drivers/modules 5) Check the hardware PCI devices, SATA, NIC etc - lspci etc - you have a list of devices for debugging 6) Test boot with your 1.02b loader (3615 recommended) 7) Debug Things that might be problematic - Onboard SATA vs add on controllers and disk numbering vs physical slots. Port multipler being used. Disk activity lights not working. Enhanced extra.lzma file from @IG-88 needed for controllers, NIC.
  2. sbv3000
    usb= 'Removable Device' perhaps? try that as first boot device and disable all other devices
  3. sbv3000
    It may be easiest to buy a cheap supported sata pci-x1 card and disable the onboard ide/sata. https://www.amazon.co.uk/Syba-SI-PEX40064-Controller-Profile-Brackets/dp/B00AZ9T3OU
  4. sbv3000
    try the 6.0.2 loader - 'best' for amd
  5. sbv3000
    can you check the bios for boot options and boot manager, you should be able to set an external device UEFI or otherwise https://www.manualslib.com/manual/388722/Acer-Ac100.html?page=98#manual
  6. sbv3000
    for the first install of DSM the .pat file version has to match the loader. once installed you then update to later versions.
  7. sbv3000
    I've used the 'clean drive' method to downgrade in these situations' 1) Disconnect your raid drives 2) Connect spare HDD to SATA port 1 3) Install DSM 6.x from fresh 1.02b loader, create admin user and server name matching live system, DONT create volume/raid. Update DSM to match your pre-beta version 4) Shutdown, reconnect raid drives to SATA ports 2-n 5) Boot, login, repair system partitions on raid, shutdown 6) Remove spare HDD and reconnect raid drives to SATA ports 1-n 7) Boot, repair packages etc I've used this method several times and it works fine
  8. sbv3000
    strip everything out and do a bios reset using the onboard jumpers and disconnect the psu. install minimum components (memory) to get the system back, then try the 6.02 loader, which has better amd support.
  9. sbv3000
    I would recommend the DS3615 image, that is the most popular so if you have issues, a greater support base and also the core i3 architecture is the 'native' one for the 3615 https://www.synology.com/en-uk/knowledgebase/DSM/tutorial/General/What_kind_of_CPU_does_my_NAS_have the rest of your hardware should be fine, but do a thorough test in case you need to use the customised extra.lzma file @ig-88
  10. sbv3000
    see my post here
  11. sbv3000
    its an old 411j
  12. sbv3000
    Its recommended to disable automatic updates of DSM to stop 'unstable' (v XPE) versions being installed !
  13. sbv3000
    In principle any use of a generated or 're-purposed' S/N or MAC is a breach of Synology T&Cs, which is why its discouraged by the forum. Valid S/Ns & MACs are usually associated with using Syno servers for a service (quick connect or authenticating a third party service like Amazon Drive or HubIc) but thats because you are using their systems and those are 'funded' by a genuine hardware purchase. If you dont need QC or other services, any numbers will do, if you do then - well... There are alternatives to using Syno services if you research. I use DDNS instead of QC and a remote rsync server (DDNS) for backup. In my experience its the S/N that seems more critical.
  14. sbv3000
    When you create a boot loader it will be the specific DSM version (15047 I think). when you upgrade DSM manually or through Control Panel it updates the boot loader with matching version. So, if your boot loader is corrupted and you flash a new one, that will be 15047. You will need a spare hdd on which to install DSM (disconnect your raid disks) and upgrade it so that it 'writes back' the updates to the boot loader. You can then use that 'updated' loader to boot your system and it should be ok.
  15. sbv3000
    I've installed the VBox DVBT2 - and with early testing it has the usual mixture of quirks Excellent setup, well laid out interface via a web browser. Recording path to a NAS is samba with IP address/folder path, user/password so on the NAS I created an account and recording folder with permissions etc - records SD and HD fine (on my gig lan snmp traffic shows a 1080p recording stream is 2-3 Mbit traffic from the vbox to the nas) A 10 minute test recording at 1080p created a file about 670mb. Files are MP4 container with 5 channel surround (if part of the stream) and subtitles (ditto) iOS app works slow but fine on my older ipad, but the android app crashes on anything I've tried. Dont have A Shield so can't speak for that, but DLNA streaming to VLC seems fine, that plugin is needed for PC/web streaming of channels. Hope thats useful, more as I experiment
  16. sbv3000
    the main reason was I didnt find the home run in my research But looking at the spec, having to pay for a pvr service would have made me look elsewhere. Also even if that was not the case, the vbox looks more 'EU centric' rather than the US home run, so 1) possibly better support for an EU buyer, and also 2) paying import duty/vat. And it has a built in DVBT2 dual tuner, so no dongle? When its installed I'll let you know more.
  17. sbv3000
    I just purchased one of these (DVBT2 version), http://vboxcomm.com looks similar to the HD Homerun, but according to the spec you can stream to most devices and record to mounted NAS drive It arrives on the 4th April! Not as cheap as the other devices you mention, but I'm hoping to get something similar to what you are doing, to replace my setup that has the same hauppauge tuner you are looking at combined with DBVlogic apps, which is getting 'tired' on the slow PC I'm using. Will report more if you are interested.
  18. sbv3000
    DSM6.x defaults to disk/raid groups and volumes rather than shr, clean install with 3 drives the same size, just stick with btfrs/disk group. check the faq for re-enabling shr in the config via ssh for example if you have different size drives, which is what @abced is referring to.
  19. sbv3000
    You are in a minority using hyper v, so there may not be a lot of advice available. Have a search through the forum here and the synology forum for accessing raid via mounting in Ubuntu/mdadm, there is a tutorial. A lot could depend on your h-v setup, the controllers etc. Generally DSM/shr is quite good at recovering/reassembling raid but that would come up on the web interface and offer a file system check. The fact that your raid does not may be a sign that the data is lost, you might have to delete the volume and restore from backup
  20. sbv3000
    I'm running syslog fine on xpe/dsm6, one box (asus bare metal) is the server, several other xpe boxes and my router sending to it. try a test with logging locally, to make sure the service and logs location is ok, then look at the remote settings. You might have to play with the format and port settings on both server and client.
  21. sbv3000
    might be a quicker option to add a compatible (intel?) pci network card to get working and test the remaining hardware (drive controllers etc) while you sort out the on board nic drivers
  22. sbv3000
    Before you upgrade I would test your boot USB and the DSM installation on a spare HDD to make sure you have your vid/pid correct and your other hardware is compatible, disconnect the raid drives of course. Also a backup would be recommended. When you boot with your 6.1 loader it will need the 'matching' DSM .pat file, which, if I recall right is 15047. When you run Syno assistant it will show the system version and as migratable to that version. Install DSM 6.1- 15047 and then go through the various updates (control panel or manually) to get you to 6.1.5. If you try and install 6.1.5 with the 6.1 loader it will probably fail. When you update DSM it 'writes back' to the boot USB the latest version files so the boot and on disk O/S are in synch
  23. sbv3000
    try installing dsm using the 'default' mac for a single nic, and once you are 'up' then edit grub for the the correct addresses and quantity
  24. sbv3000
    imho a fresh install would be best, as recommended. However, if you test your hardware with a spare HDD and 6.1 loader/DSM (having disconnected your raid hdd's), once that system is tested, delete any test volumes, power off, reconnect your raid drives to sata ports 2-n, on boot of DSM6, it should find your raid and the system partitions will be bad, repair them and you will have a full 6 setup. backup data first as recommended.
  25. sbv3000
    I dont know if this is of use but I looked at the logs of my real DS1812 and an xpe DS3615. Both units show the drives waking up at random times, not just related to connections. I'd put this down to processes running that need disk access, whatever that might be, there are plenty running all the time in resource monitor. I dont think you will eliminate waking up completely, and if during 'non production' times, they do wake up for a few minutes, is that an issue?
×
×
  • Create New...