Jump to content
XPEnology Community

Masrawy

Member
  • Posts

    34
  • Joined

  • Last visited

Posts posted by Masrawy

  1. 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?

  2. Can anyone post the download link to

    "v1.02a (DS3615xs) is for DSM 6.1"??

     

    In the first post, on the second line, there's 2 links, click on any of the 2 "here".

  3. 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...

     

    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?

  4. 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...

    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 :sad:

  5. 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

  6. Good to hear! :smile:

     

    It's pretty easy to enable SSH, just do it through the GUI in DSM. You should login using admin rather than root (as root doesn't work OOTB with DSM), you can still use sudo with your regular DSM admin password.

     

    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?

  7. 2. Spoofing is another word for faking, if you don't put in your real MAC address into grub.cfg, your network card is having to fake its identity in simple terms.

     

    3. When you setup the Xpenology bootloader you'll see the following entry within grub.cfg:

    set mac1=0011322CA603

     

    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!

  8. 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?

     

    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 :smile:

     

    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! :smile:

  9. 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?

  10. So I tried to install v1.02a2 ds3617xs baremetal, I think it worked but unfortunately, after the install, I cannot find the NAS anymore on the network usint Synology Assistant or find.synology.com. Any clue?

  11. Here is a video install i made of DS3615xs 6.1 Jun's Mod V1.02-alpha on ESXI 6.5 Ill be making another one on how to install ds3617xs V1.02a2-alpha soon...

     

     

    That's would be awesome! Can you do a your next video for a barebone install of 10.2a2 please? :grin:

    Thanks a lot!

  12. How is DSM 6.1 performing?

     

    I'm currently running DSM 6.0 update 8 and would like to switch to 6.1. My usage is really basic and I don't have a lot of experience. Unfortunately I've been off the forum for a few month and I see there's a lot more pages now. I'm sorry in advance if the info I'm looking for is buried somewhere in the 260 pages.

     

    If someone is kind enough to help me through the process or at least guide me in the right direction for the upgrade, I would be very greatful! :smile:

    How can I perform the upgrade from 6.0 update 8 to 6.1 on a barebone configuration?

    What precautions do I need? (this XPEnology server is already a backup of another server which is almost full)

    Is there a tutorial somewhere? (all I see in the OP is to not update to 6.1 with Jun's 1.01, which I'm running now)

     

    Thanks in advance! :wink:

  13. Question.. I have a Dell Precision T7910

    With 2 Xeon E5-2698v3(16 Cores Each) @ 2.3GHz Max 3.6Ghz Plus 128GB of ECC Ram

     

    Why I can only see my CPU's as i3?

     

    Question for you guys. What would be the purpose of have such a powerfull PC for XPEnology?

     

    I understand for example in the case of Freenas which is RAM hungry and ECC is very highly recommended if not mendatory, but in the case of XPEnology, why would we need more cores or a faster CPU? Why would we need more RAM? Would ECC be better or not?

  14. http://www.pro-blog.com/fix-synology-long-raid-rebuild-times/

     

    This article is one source. There are a few posts around the web that explain how you can speed it up.

     

    I already did that as explained. But I couldn't find how to modify stripe cache size.

     

    Under "More advanced tweaks":

     

    echo 32768 > /sys/block/md3/md/stripe_cache_size

     

     

    Thanks for the help, I tried and it didn't do anything unfortunately. Should I put an even higher value? up to how much with the specs I have in my signature?

  15. What can I do to speed up expand speed?

     

    I had 3 X 6TB HDDs + 1 X 128GB SSD all in the same disk group. I added a 4th Seagate Ironwolf 6TB HDD identical to the 3 already in. the rebuild speed is now around 60MBPS. at that speed it will take I remember when I had only 2 HDDs plus the SSD and added a 3rd HDD, the rebuild speed was between 195 and 220MBPS.

     

    I already changed sysctl -w dev.raid.speed_limit_min=200000 and sysctl -w dev.raid.speed_limit_max=500000. My CPU and RAM are only around 4% use... What else can I do to speed this up???

     

    I read somewhere to increase stripe_cache_size, but couldn't find how... Any clue or other suggestions?

  16. If I have a PCIe Sata card with 8 SATA 6.0Gbps will it work? or is it max 4 ports?

    I found some cards that can have up to 8 SATA ports. I am considering buying one to replace my 2 port card

     

    Thanks

  17. Thanks Polanskiman for your help. I have to say all this is pretty new for me, so I'm not quite sure to understand it all. Any ways, I have nothing to lose since there's no data at all on my NAS for the moment. I'm learning and trying things with it before I transfer everything from my other computer to this NAS.

     

    What are VI and Nano?I tried to read and search some information but couldn't find answers.

     

    Also, when you say comment out/delete or add something in the script, I'm expecting to open a file to edit it (for example in NotePad++), but it's not the case since it is through SSH, I'm not quite sure to understand how it works. Can you clarify a little more please and send a screenshot of what I should expect?

     

    As I said, all this is new stuff for me. Thanks a lot again :wink:

     

     

    SSH with admin

    input your password

    elevate rights by doing:

    sudo -i

    input your password again

    you are now root

    edit the synoinfo.conf file with vi or nano if you have it installed. I prefer nano it's easier to use. You can install it through the community package center

    vi /etc.defaults/synoinfo.conf

    or

    nano /etc.defaults/synoinfo.conf

    comment out/delete

    supportraidgroup="yes"

    then add

    support_syno_hybrid_raid="yes"

    Save the file. You are done. Preferably reboot.

     

    If you don't know what I am talking about then you shouldn't be tinkering with system files.

×
×
  • Create New...