Masrawy
-
Posts
34 -
Joined
-
Last visited
Masrawy's Achievements
Junior Member (2/7)
0
Reputation
-
I would like to know which is better and more stable between 1.03b DS3617xs and 1.04b DS918?
-
Hello everyone, I need your help. I was running DSM 6.1.7 with Jun's loader 1.02b DS3617xs Baremetal. I'm migrating now to DSM 6.2 with 1.03b DS3617xs. I did all the steps in the tutorial using a 2nd USB drive, so I can keep the original one with the old DSM, just in case, (setting up VID/PID, MAC adress, Serial Number). I was able to boot my server to do the migration, it seemed to install properly and all. Last step in the migration is to restart, but unfortunately I cannot find my server anymore. I tried with another USB drive (a 3rd one), just in case the 2nd USB drive is defective or something. I also made sure to put the right VID/PID. Unfortunately I cannot detect the server at all to reinstall, even if I go to the bootloader and select the second option (Reinstall) What should I do?
-
Is this topic unlocked now . Any other developments coming?
-
Is there still the "timebomb" problem with 1.02b DS3617xs? I had this problem with the previous 1.02a and 1.02a2.
-
I have 6.1.1-15101 Update 4 with no issue since it was released
-
What is the advantages, disadvantages and difference between Baremetal, ESXi and VmWare?
-
In the first post, on the second line, there's 2 links, click on any of the 2 "here".
-
This is a problem aka "Time bomb" - it happens after installation and using DSM through 12-24 hours or something about it. I have same problems few times, i don't know how to fix it and nobody can help me here. try to use 3615 with 1.02a (not 1.02a2) Even if I use a brand new USB flash drive to try to reinstall I get the same message. I there a way to reinstall XPEnology of I'm screwed with a bricked NAS? Is there a way to avoid having time bomb while still using DS3617xs?
-
Have you tried unplugging and reinserting your network cable when your Xpenology is in this state? Every time I've lost connectivity this has worked for me. Sent from my SM-G935F using Tapatalk Yes, I even tried to unplug it from the wall for a few minutes and replug and turn it on, but same result
-
Anyone ever got this message? http://s1038.photobucket.com/user/twistedus/media/Capture2.png.html I can't connect anymore on the NAS and even the drive map is not accessible anymore. I installed XPEnology 6.1.1 lastest update yesterday using DS3617xs v1.02a2. I was working fine. This morning I had this... I tried to reboot, but no result...
-
FINALLY!!! after lots of research, I found Nano compatible with DSM 6.1.1. You can manually install it, here is the link to download it! http://www.jadahl.com/synology6.1/packages/nano_broadwell-6.1_2.7.5-2.spk I also found other links, but these didn't work. I'm posting it just in case it serves anyone... http://www.jadahl.com/synology6.1/packages/nano_alpine4k-6.1_2.7.5-2.spk http://www.jadahl.com/synology6.1/packages/nano_x86-6.1_2.7.5-2.spk http://www.jadahl.com/synology6.1/packages/nano_monaco-6.1_2.7.5-2.spk
-
Sorry I meant SHR not SSH. I remember we had to install a add a package source to install Nano to edit synoinfo.conf. If I remember correctly, that was the right source http://packages.synocommunity.com. Unfortunately, I can't find Nano or VI anywhere. I also enabled all publishers... I added a bunch of sources and none of them add Nano or VI. Also, most of them don't add any package... Is it because Nano and Vi don't work with 6.1?
-
You'll want to figure out what your NIC's real MAC address is, this can be done a number of ways but the easiest (assuming you know what your IP address is) to run "arp -a" from command prompt in Windows. You need to put the physical address you see into the variable above without the formatting so rather than 00:11:32:2C:A6:03 it needs to be 0011322CA603. As Jun mentioned, it's not mandatory to change the MAC address but from my own testing I find using your real MAC address works best. 4. I'm using DS3617xs, I've not tried the other. EDIT: Forgot to mention that before you try and figure out your MAC address, it's essential that you unplug your system from power completely and leave it off for up to 5 mins. Do not boot back into the loader without changing the MAC address entry otherwise you'll get the spoofed MAC address rather than your real one. Thats awesome!!!! thanks a lot filippo333, it finally worked! Now I want to enable SSH, I remember I had to edit synoinfo.conf with either Vi or Nano. I used Nano in the past but I can't find the package source for it. Anyone can help? Thanks guys!
-
I have the EXACT same motherboard and CPU as you and mine works without any issues on 1.0.2a2, make sure your BIOS is up-to-date. One thing I've discovered is that the NIC inside this motherboard doesn't like to be spoofed, so ensure you use your real MAC address for the loader. If you're using a fake MAC address then fully power off and unplug your system for 5 mins; I've noticed the spoofed MAC address is persistent as long as the system is connected to the wall. Also don't select any of the options within the loader, just boot straight to the defaults and you'll be able to find it. One more quirk is that the Synology Finder software (including the website version) is unreliable with Xpenology, so I'd use an IP scanner to figure out what your IP address is. Better yet, reserve a Mac address Thanks a lot for your quick response. I'm new to all this, so there are a few things I don't understand right away. 1. My BIOS is up to date. 2. NIC doesn't like to be spoofed? What does it mean? 3. How can I find the real MAC address of my NIC to modify grub.cfg (I thought it wasn't mandatory) 4. What are you using? DS3615xs or DS3617xs? Thanks again for your help!
-
I'm desperately trying to install DSM 6.1 either with DS3615xs or preferably DS3617xs, but nothing works. I can't detect find it once I select Baremetal install (or force install). Is it because my NIC is not supported? Anyone has a step by step tutorial for Baremetal DSM 6.1 ideally DS3617xs?