oakey

Figured it out, SHR isn't used any more. Everything working fine now. Thanks for the advice

So stupid question, but how do I add a new disk? I've added HDD3 and DSM sees it. My existing drives are SHR but I don't see how to make the new drive the same. I thought you had to go to RAID group and create a new one and then you go to volume and create but RAID group doesn't give me the option to create an SHR disk.

Great informative post. Currently I'm at the stage where everything *appears* to be working with the exception of one HDD which has been showing as 'crashed' for a while now in DSM and couldn't be written to (only read). If I install this drive back in to the system I end up with the problem where I get a network connection briefly on startup and then it loses the connection and I have to pull the plug. I'm currently in the process of swapping that with a HDD that's in my WinPC (once the data transfer finishes). Right now though Xpenology / DSM seems to be working as it should. From what I can understand the issue with WoL not working seems to be with the way the system shuts down through DSM. If you killed it at the power switch and tried WoL it would wake it up but then if you shutdown from within DSM or DS Finder Wake on Lan wouldn't work again until the system was killed at the switch. When I added that weird S99ZZZ_Shutdown.sh then Wake on Lan worked even if you shutdown through the DSM, I don't really know why or how that script influences Wake on Lan. I'm currently looking in Putty and I don't appear to have shutdown_script dir or DSShutdown.sh Thanks for the help, it's been really useful.

I've made some progress. I pulled all the HDD's and booted it up, then ran the DSM. It asked to install a HDD, did that (hot) and then it wanted me to install DSM. I didn't do that. I shut it down. I then started it back up with the HDD in and I actually managed to navigate DSM with no network dropout. Shut it down again and now adding each HDD back in one by one.

The problem seems to be it keeps dropping the connection. I boot it up and it starts up and I can login but then it drops off the network and that's it.

It's gone again. Restarted it but it's not showing up in the router. Would reinstalling Jun's Loader fix this?

No, something isn't right. I'm logged in to DSM but the packages aren't working. File Station won't even open, just get the spinning circle on the icon also even though it shows up in the router and I'm actually logged in both Synology Assistant and DS Finder are showing it as offline. Can't open Control Panel, can't do anything.

Tried find.synology.com and it says nothing is there. I either log in to my router and look at the list of connected devices or I use Windows and look at what's showing on the network. The diskstation doesn't show in either of them. the DS Finder app just shows it offline as well. Oh, wait... it's working after I tried your suggestion of resetting the BIOS. It's showing in the router and I'm logged in to DSM, the packages are back as well. However, both Synology Assistant and DS Finder show it as 'Offline'

Yep. The LAN light flashes. I can turn it on via Wake On Lan but once it's booted up it doesn't seem to be connecting to the LAN. I assume DSM is still functioning as it should just that it's unreachable.

Argh, I've broken it. I shutdown and then started it up via WoL but now I can't access the DSM, it's not showing up connected to my router and if I connect it to a monitor it just says 'Booting the Kernel' (which is what it should do I think?). IT appears to have no LAN connection anymore.

Done it, finally! All works now. Thanks to you both for all your help. These two posts also helped a lot in getting past that final hurdle: I do have one more problem, all my packages have now disappeared from here even though they still appear to be running, how do I recover them?

It's not working fully yet, I need to to the shutdown script in the above link so it works all the time

Aha! It works! I had to boot up the system and then when it finished booting I killed the power at the switch. Then when I used DS Finder to wake it up it turns on. So it seems the issue is when the system is shutdown through DSM or the task scheduler it's not shutting down properly. I need to do the shutdown script in the above link but I'm not familiar with how I create the file in Putty and set the execute permissions.

So through a steep learning process I've figured out how to navigate through Putty and everything points to the MAC address being correct where it needs to be; the Wake On Lan app, the grub file, in DSM, the BIOS, etc, the MAC address is the same in all of them. I've logged in as root and entered ethtool -s eth0 wol g synoinfo.conf shows wol as enabled and eth0 set to g I've bound the MAC to the IP in ARP in the router (as well as using address reservation). Neither Wake on Lan app or Synology Assistant can wake it. I think I need to do this but it's a bit beyond me; https://xpenology.com/forum/topic/9530-how-to-get-wake-on-lan-working/?do=findComment&comment=81927

How do I look at the synoinfo.conf file in putty to make sure the settings are correct? edit: figured it out Is this the problem? the wol settings are set to 'd' or not, just found this

I don't know what you mean by set the mac address in the Wake On Lan app to the one DSM says. The mac address in the Wake On Lan app is already the same as the one in DSM which is the same as the one in the BIOS which is the same as the grub file. All my devices are already configured for ARP

Okay, managed to get root access with sudo -i and entered "ethtool -s eth0 wol g" Still not working. I'm wondering if I don't have the correct MAC address. Edit: I've connected it to a monitor and logged into the network configuration screen and the MAC address is correct and the same as I've put in the grub file so not sure where it's going wrong.

I'll double check everything, at least one of my Windows PC's on my network can be woken with the magic packet and the WakeOnLan app on Android so the router shouldn't cause any problems. I tried the admin password for root and it was denied in Putty, I even logged in to DSM and changed the password and tried it again. Edit: okay, WoL works on my other Windows PC that's connected to the same switch as the NAS so it's not a network issue. Is there more than one BIOS in the MicroServer that needs WoL enabling?

I've googled this and read every thread that shows up on this subject here but I'm still non the wiser how to get Wake On Lan to work. I'm running Jun's Loader 1.02b with DSM 6.1.7 on a Gen8 Microserver, and as far as I know I have the proper MAC address for my ethernet1 port in the grub file. Wake on LAN is enabled in the BIOS, it's enabled in DSM and I've set up in Synology Assistant yet whenever I use any apps to send the magic packet it does not wake up the system. I use task scheduler to start my NAS up at 7pm and to automatically shut it down at 2am, from what I've read this auto shutdown may not be putting it into the correct state in order to wake it up? There's a guide someone posted on here where you Putty in and enter a command but I can't for the life of me remember (or Synology have disabled it if what I've read elsewhere is true) my root password so I can't do this. If it means anything, when the system is powered off the LED's on the ethernet port are still active. Does anyone have the definitive guide to setting up Wake on Lan and getting it to work? Thanks

Thanks Polanskiman, I follow this link: https://xpenology.com/forum/topic/7857-how-to-update-juns-loader/?tab=comments#comment-75881 And step 5 says see your sig for links but there aren't any? Anyway, I think I know what's needed to be done.

Hi, I'm currently running DS3615xs 6.0.2 with V1.01 on a Gen 8 Microserver. A few questions; 1. Which tutorial do I need to be following to update to the latest loader / DSM? 2. Can I go from 3615 to 916+ and is there any reason I should or should I just stick with 3615? Thanks

can this be done in DSM or do I need to stick it in a PC?

I'm running 5564 (28th,Oct, no updates) on 5592 bootloader and one of my 2 Tb volumes (of 3) has crashed. I can still access the disk and copy files from it but can it be fixed? HDD health is normal but there are 52 bad sectors, a quick SMART test seems to get to 90percent, I don't know whether it's stopped responding or just taking it's time. There are 6000 hours on the drive. I stopped processes and unmounted it then checked it with e2fsck and it didn't show any bad data. Is it a bug with DSM 5564 or am I likely to have a genuine failed disk?