bearcat

Members
  • Content Count

    454
  • Joined

  • Last visited

  • Days Won

    10

Everything posted by bearcat

  1. Just a thought... what if you temporarily remove 1 of your other drives, while formatting your new SSD and copy your old to it, then pull out your old SSD and replace your other drive.
  2. @NooL did you send "your magic packets" to the genuine/real mac address of your nic''s or to your spoofed/cloned addresses?
  3. @NooL Are you using the real or fake MAC addresses with WOL?
  4. @emufile as posted above, this tutorial might help you. (there are others posted in the forum)
  5. Yes, but you might have missed one important point, your internal nic will no longer work, and those who runs a G7 Microserver are using an add-on nic (mostly a Intel based, with native support (e1000e driver). If you have access to one of the supported NIC's, you may disable the internal nic and install the add-on, and it should work right away (with your "old" USB) This tutorial might help you to downgrade,
  6. @TyphoonNL I think you missed my point: There is a reason why it gives you a headache, it won't work, as the bootloader needs to know the vid/pid of the bootdevice (USB stick). If you clone your USB to a SATA connected device, your cloned vid/pid info will be wrong, and your system will not boot. So the answer to @Vernon question in post 1. would be "Yes, but it depends on what DSM version and bootloader you are using".
  7. @Vodka2014 : if you are more friend with Windows than Linux (like many of us), you may shut your NAS down, remove your USB stick and edit your grub file on a Windows computer with the help of the trial version of Paragon's nice sotware.
  8. @TyphoonNL : Maybe a little hint for you: What VID/PID is your SSD supposed to use after cloning your USB stick? (assuming you know how Jun's bootloader for DSM 6.x work).
  9. @Paul Stead Hello and welcome aboard First thing's first, read the FAQ's. Then, based on your current hardware,and your needs. you (maybe with some help) can decide what version will work the best for you. Q - Do "you" (me, anyone...) need the latest software? A - I don't think so. Q - What would someone claim to be the most "forgiving/compatible" combo? A - Jun's 1.03 3615xs bootloader and DSM 6.1.x ( currently .7-15284 Update 3) Q - Where do I find the above mentioned combo? A - Go back and read the FAQ again. Q - If I don't get it, can I ask for more specific help? A - Yes, of course
  10. And exactly how do people in the other end decrypt those files, if the only key is inside your NAS? Unless I'm wrong (never have been, never will ) your files will be decrypted before beeing transferred to the network, and it is only being encrypted locally, much like Microsoft's BitLocker.
  11. If you use MicroSD on HP Gen8: VID 0x0424 - PID 0x4030 is the internal card reader, (located on the USB bus). (as I mentioned to you before, did you try it?) Yes, some SD cards can behave badly, that's why it's always better to use a known brand, at a normal price, the cheaper the card, the bigger the risk of getting a bad card. Whenever I buy (or get) a new USB stick or memory card, I like to test them with H2testw to make sure I get what I want. I have found fake Corsair sticks and fake SanDisk SD cards using this tool, and avoided to use them and risk dataloss.
  12. Cool 3615 is a "winner", as can be seen in this post the HP NC365T is working with 3615 and DSM 6.2.2. Did you keep the NC365T, or did you replace it with the ET2 card? You should be able to "cross-upgrade" from 3617 to 3615, by booting a 3615 USB you will get the option to "migrate your HDD's" from 3617 to 3615 as DSM thinks you have moved your HDD's from one NAS to another. You will get an option to keep "just data" or "data and settings", the last one will try to keep your compatible app's as well. But you should make a backup of your settings, just in case. What your control panel show you as CPU info , is "hardcoded" in the loader, and nothing to worry about.
  13. @AndyMcC Hello and welcome to the "family" just as @NooL stated, the USB stick must remain at all time (at least during boot) as it's not an "installation USB", it is a bootloader allowing you to boot your system and install DSM on your HDD's using the .pat file It might be seemd as a single point of (possible) failure, but as said you can easily create a new one of needed. Even the original Synology boxes use a bootdevice to boot before handing over the system to the HDD's (thats why you can buy a box with no HDD installed, and still be able to install DSM on your preferred disk's.). What you can, and should do, is to make sure you take regulary backups of you configuration and keep it off-NAS. btw: Seeing you are using a NC365T with DSM 6.2.2, could you check what deviceid it presents to your DSM? (How to: SSH to your working NAS, log in as admin, type in this command: lspci -k | grep 0200 )
  14. I might be repeating myself, but here it goes: There are "some" issues in regards to the 3617 systems with DSM 6.x, stay to 3615!! btw: what Device ID is your HP NC365T presenting to your DSM? Seems like many of the forum users have been using the NC364T with good results, in various DSM versions, this is still supported with the native e1000e driver, but the NC365T should be based on the intel 82580 chipset, supported by the native igb driver (at least it used to be)
  15. Ok, that makes sense (Y) But now, the BIG question: how and when did this problem first show up? What bootloader are you using? 3615/3617/916/918 ? as it been working stable before, and how long? Have you changed any HW lately? Have you done (or tried to do) any updates lately? What can you tell us, to let us try to help you?
  16. You have 2 boxe's? And you have 2 *different* mac adresses? How/when did this happen?
  17. @altas Just out of curiousity, why are you so sure? If you look at the drivermatrix, the 82579V is listed as having native support as e1000e in DSM 6.2.1, using Jun's 1.03b (as long as it's having the "correct" device ID). @adicontakt : Good choice to stay on 6.1
  18. @adicontakt Good to see that your 6.1 test went well, you don't really need the 6.2.x, 6.1.7 is still running great! If you "need" to update, first see if you are able to disable UEFI/EFI boot in your BIOS, and use legacy only. Then, make sure your 82579V based nic, has the "correct" device ID, letting it load the e1000e native driver (not the e1000 driver as mentioned above) How to: SSH to your working NAS, log in as admin, type in this command: lspci -k | grep 0200 This should show you all the nic's found in your NAS, hopefully giving you "Device 8086:1503" If so, you will need to create a new USB stick, using Jun's 1.03b loader, with the same settings related to VID/PID, serial, MAC as you currently use, and start with manually providing the .pat (DSM_DS3615xs_23739.pat = DSM 6.2) (or you might want to try and jump directly to DSM 6.2.1 ?)
  19. @adicontakt While you had windows running, your NIC was working ok? as stated by @jensmander your 82579V based nic should work with the tested config, but you could try testing with DSM 6.1 / 3615. to see if the NAS gets an IP. I don't know your motherboard, but do your BIOS have an option to boot in legacy mode (as opposed to UEFI/EFI etc.)? With 1.03b and 6.2.x you MUST use legacy. btw: Not sure what you meant by "I even asign an static Ip in dhcp", did you reserve an IP for the mac adress of your NIC?
  20. FYI: There are "some" issues in regards to the 3617 systems with DSM 6.x, stay to 3615 (or 918+ if you have the hw for it). You don't have to take my word for it, just search the forum...
  21. @omar According to a Google translate, If you use MicroSD on HP Gen8: VID 0x0424 - PID 0x4030 this is the internal card reader, (located on the USB bus)
  22. @Manolenta Where you able to change the IP on your client, to bypass the IP ban, letting you use SSH locally.
  23. @Manolenta Did you try the "easy step" and change the IP on your banned client?
  24. @SerpensAlatus did you by any chance update your NAS?
  25. @Tuxx You should have read the update-reports, as then you would have found out that the internal nic is not supported with the latest update. If you add a supported Intel (or other) nic, you will be back online