bearcat

Members
  • Content Count

    632
  • Joined

  • Last visited

  • Days Won

    17

bearcat last won the day on March 18

bearcat had the most liked content!

Community Reputation

64 Excellent

3 Followers

About bearcat

  • Rank
    Guru

Recent Profile Visitors

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

  1. - Outcome of the update: SUCCESSFUL - DSM version prior update: None, fresh install, with automatic download of .PAT - Loader version and model: JUN'S LOADER v1.04b - DS918+ - Using custom extra.lzma: NO - Installation type: BAREMETAL - Fujitsu Esprimo Q956 - 256GB-M2 - 16GB RAM - i7-6700T - Additional comments: Bios disabled secure boot, set to supporting both Legacy and EFI, locked to boot from USB as default.
  2. From the top of my head... In the photo from your routers DDNS settings, you told it to use "no.ip" but entered the same .ddns.net domain name as your NAS? If the domain points to your router, that should be enough, then NAT/portforwarding should do the rest. If you use the DDNS service in your NAS, you can skip using it on the router (or use different names). It seems like you are using upnp on your router (and NAS?) Sometimes upnp is not working as it should, and sometimes it may cause security issues. Disable that, and manually set up port-forwarding to your NAS, (and make sure your NAS is using either a static or reserved IP).
  3. Yes your data will move easily, but as always, a backup is a nice thing to have At least, you may want to do a backup/restore of your settings. Your addons/plugins might need to be reinstalled, due to different CPU architecture.
  4. @IG-88 Actually, in the Tiny (USFF) I have, the CPU is a i5-3470T, but yes, it's still from a "wrong" generation. I did it just to make sure. On my Asrock Q-1900, I was not supposed to get the 918+ running, but it did. This time, the info was correct Not sure what I did wrong yesterday, when none of the images I tried was working for me, but just for "fun" I had to reboot my router today, and then the last made USB, Juns 1.02b DS3615xs was getting an IP from the DHCP, and I could open the web-based install page. So I made another bootstick, 1.03b DS3615xs, and same positive progress, it showed up in the Syno assistent and I could open the webpage. I will need to find a free 2,5" disk to do a full install and play around some more. The NIC in use, is the Intel 82579LM, device id 1502, using the native e1000e driver. And just to doublecheck, I redid a 1.04b 918+ USB, with the same no-working network. btw: the actual booting "seems to" work , as I get to the normal "Screen will stop updating shortly.." but since I have no serial port, I guess it will throw a bunch of errors behind my back.... Just as a "mental note" to myself later on: BIOS: disable secure boot, CSM enabled, enable boot from legacy USB as primary boot device. No added "extras" just the plain bootimages, adjusted for vid/pid. @LSUStephen As you might get from my rambling above, I did not need to make any hybrid stick, or other "magic" to get it working (today)
  5. According to a post from @IG-88 it seems like Synology might have retracted 6.2.3 for older models. It might be wise to stay calm and wait with the update for now.
  6. If you have downloaded the XPEnology Tool for Windows x64 you will find a "portable" DHCP server that might be useful for faultfinding.
  7. @LSUStephen I "rediscovered" a M92p Tiny (the USFF model) I had laying around, and would like to try it out as a "Mini-NAS". I ran into the same problem as you did, starting with 1.04b 918+, then 1.02b 916+, before trying the "failsafe" 1.02b 3615. But, just like you I'm not able to connect to my LAN, so no IP from my DHCP server. Now: How was your final way to get it going? (my current setup has been using legacy boot while testing) btw: to answer your question, you need an internal drive to install DSM and run it, and your USB will just stay as a boot-media, but I guess you already found out.
  8. Just verified my test, using the latest Windows update on a desktop Same no-problem in my end. Could the ones who experience this "problem" report if your Windows computer is UEFI or Legacy based? And for the "fun of it", try to mount your USB sticks with the free read-only tool: Linux Reader to see if you find grub.cfg at all?
  9. Keep us updated. Best of luck, and congrats with (what seems to be) a nice piece of hardware
  10. How is the rights configured for your NFS shares? (and the actual folders on the NAS). Are you referring to the HW transcoding in Plex, or the one in VideoStation, they are 2 different things.
  11. You may want to clear the drives, not as MSDOS but having NO partitions at all. And stay with AHCI, DSM will be doing any RAID that you want/need.
  12. Ok, I see ... might look into it one of these days I'm used to have a separate management VLAN or IP range, for safety reasons. While you have thae allmost working setup (with pingable IP) Just for a test, you could try to connect the NAS directly to your computer (where any firewall should be turned off), and see if the Assistent can find the NAS that way. Give your PC a static IP, ie. 169.254.0.25/255.255.255.0, then reboot the NAS. ""If the Synology Server does not get an IP address from a DHCP Server (i.e. if you connect your computer directly to the Synology Server), the Synology Server will use a 169.254.x.x IP address. You might need to change your computer's network settings to be able to see the Synology Server.""
  13. Hi, I'm not familiar with the Uni-Fi world, so at first I was stumbled by the IP range, before I recognized it as one of the "other" private ranges;-) But I notice it says Managmenet LAN, is your other computers part of the same Management LAN? Could it be some firewall rules blocking your traffic, even if it get's a pingable IP from the DHCP server?
  14. Based on your CPU speed, this is a HP N40L G7 Microserver. When you added the extra disk controller, you may have "shifted" the enumberation of drives, making it hard for DSM to sort out the RAID, but you should still get an IP. First thing to check: Is you network cable well connected in both ends? Will this cable (and any "boxes" on its way) give an IP to any other unit you have available to test with? Next: Is your BIOS setting all OK? (NIC enabled, C1E disabled etc.)? If booting a Live Linux USB, will it get an IP?
  15. Here is a fresh idea I got today Make a new post / thread in the Installation section of the forum. Make sure you write down all essential info, as what type of CPU and nic your new mainboard is using. This thread is aimed for transcoding, not general installation problems