HHawk
-
Posts
59 -
Joined
-
Last visited
Posts posted by HHawk
-
-
MTU in DSM actually. With the link I provided you can access the system partition and modify the MTU in /etc.defaults/synoinfo.conf
The line to modify if your NICs are bonded is the one that says:
bond0_mtu=
Any other line with mtu should also be brought to 1500 if higher than that.
Ah thank you for explaining that...
But if I can access the system files, I will be able to change /etc.defaults/VERSION to something like:
majorversion="5"
minorversion="2"
buildphase="0"
buildnumber="5592"
builddate="2012/12/05"
Right?
If that's true, I can even try to downgrade if I fail DSM 6 again this evening...
-
Polanskiman said:
I understand. You could try the latest loader v1.02a2 although I am not sure it will work. Give it a try and let us know.
In my opinion the problem is coming from the network configuration files or even your MTU if you set it too high. Difficult to say since I don't have access to your hardware.
I could also recommend you only plug one network cable and de-bond the NICs on your switch/router if that was the case before.
Thank you Polanskiman. I will certainly try several other things, before really wiping it.
Hopefully there is some way to make it work. When I get back home, I will:
1. remove the network cables from the Intel PCIe card, so I will only have the onboard Intel one.
2. check the MTU on my switch
3. check the LACP settings on the switch (maybe that's the problem) though it still weird that other applications actually work.
I will modify the grub.cfg once again and run "Force Install" again. And select the .pat file once again. Hopefully it will work now...
Never had this kind of problem before, but then again, it's a new loader ofcourse. Something I am not experienced with.
Polanskiman said:Wiping the system partition would require to access the partitions (system and data) through another OS like a live Ubuntu USB for example. I made a tutorial on the matter >>> https://xpenology.com/forum/topic/7004-tutorial-how-to-access-dsms-data-system-partitions/
Thank you for explaining. I will look into it, though it's a final resort ofcourse.
Polanskiman said:I don't think so. If that was the problem you wouldn't even be able to boot the machine.
Yeah true, but really trying to figure out what's causing the problems... Would have been so much easier if you had a command prompt (locally) upon boot imho.
Will report back later.
-
Why are you commenting out
# initrd $img/ramdisk.lzma $img/$extra_initrd
?
Because if it's wrong and/or incorrect, I can easily correct it. It doesn't matter if it's commented out or not in this case, as it shouldn't do any harm.
It's for me easier to revert back in case it's wrong. Otherwise I have to search the forum again and copy and paste the line once again.
Personally I would wipe the system partition and do a clean install and proceed as I have advised. Your data is on another partition so you won't lose anything but you will need to reconfigure everything and reinstall packages. This is what I always do when I do major DSM version updates.
Reconfigure everything....!
I will lose all my series, movies, download settings for Sabnzbd, Couchpotato and Sonarr. Not to mention that I will get recommended movies with Couchpotato I already have seen...
Furthermore I will lose my database which is being used by 2 Kodi/Jarvis machines.
So, that's not really a solution imho. I followed the tutorial step by step.
After a reboot and waiting 10 minutes, I can connect to Couchpotato, Sonarr and Sabnzbd, but I cannot connect to DSM GUI.
So there seems to be a bug in the loader as I did everything exactly correct according to the manual.
I waited several months (6+) before doing this update, thought it would be pretty safe to use by now, but apparently not.
I really find it weird, that it could be the NIC, as I can connect to C, S and S (as mentioned above and in my other posts), if it was any of the NIC's, these wouldn't be accessable either imho.
Anyways, I will try it once again this evening, as you mentioned, maybe it's the NIC (something I doubt), but I rather be wrong on my side. If it would fix things.
Ohterwise I will have no other choice than to purchase a real Synology and say goodbye to Xpenology (= win for Synology obviously), because redoing my complete setup of everything (including my applications and such) is not a real option here.
Will report back later this evening when I get back home. I will also test the beta loaders from Jun as well. Maybe those will work instead for me...
It's sucks that I cannot downgrade back either to 5.2, because when I use my 5.2 USB stick, I am getting a prompt, but none of my useraccounts in combination with my passwords work.
//edit #1
You mentioned and I quote "Personally I would wipe the system partition..." how would I do that if I cannot even access the machine by SSH or locally with monitor and keyboard?
Or is that what you meant with the "Reinstall"-option from Jun's loader? Anyways, it's something I rather not do....
//edit #2
Probably silly, but DSM 5.2 USB stick was always booting in BIOS Legacy mode, the new 6.0 USB stick is running in UEFI (as it said the tutorial you can select either one).
This wouldn't be the issue right?
ME = Headache!
-
Polanskiman said:
That nick uses e1000e as a driver which is included in the ramdsik of loader v1.01.
Only populate the MAC address of that NIC in the grub file (mac1), leave netif_num=1 and also change the following line:
initrd $img/ramdisk.lzma $img/$extra_initrd
to:
initrd $img/$extra_initrd $img/ramdisk.lzma
Then try installing again.
Please revert.
Thanks for answering, but I already found that "solution" yesterday as well here: https://xpenology.com/forum/topic/7507-tutorial-installmigrate-dsm-52-to-602-juns-loader/?do=findComment&comment=65939
So I changed it to the following:
# initrd $img/ramdisk.lzma $img/$extra_initrd initrd $img/$extra_initrd $img/ramdisk.lzma
And I reinstalled again (throught Force Install and select the .pat file once again).
...but no luck.
But I doubt this is the issue, because (like I have mentioned a few times) after 10 minutes on a normal boot, I can access Sabnzbd, Couchpotato en Sonarr. So I really doubt it's any of the LAN ports in general... Otherwise it wouldn't be able to connect to those applications, let alone download stuff... Right?
Anyways, I will retry the above once again this evening when I get back home (for the 3rd time), but I doubt this will solve it.
//edit
In DSM the 3 LAN ports were bonded (LACP). I don't know if this is important.
Anyways, I re-read your post and I will populate only LAN port this evening, as you mentioned and redo everything once again...
...unless you have any other ideas....?
-
I would recommend using the onboard NIC to start. There is actually no need to set all MAC addresses. What Realtek NIC model do you have?
Hi Polanskiman.
First thanks for answering, but I replied (since the forum was working again) a minute before your answer. Please check when you have the time.
It's not an onboard Realtek NIC...
-
So the forum is fixed again? Apparently also running on Jun's loader?
Well changing "1" to "3" for "set netif_num" didn't work.
I also checked the motherboard, which is an AsRock Z87E-ITX. According to the website of AsRock the onboard LAN is an Intel NIC (Giga PHY Intel® I217V).
But to be honest; I doubt it's any of the NIC's (correct me when I am wrong though), because after booting up (normally with 1st option in Jun's loader) and wait for about 10 minutes. I can connect to my applications like Sabnzbd, Couchpotato and Sonarr. They also work normally, as they download stuff...
...what I cannot access is my Synology partitions/shares through Windows (or other) and I cannot access the DSM GUI.
I also tried downgrading, by using "Force Install" and select a 5.2-pat file. However this obviously doesn't work.
Furtermore; I used my original DSM 5.2 USB stick (with XPEnoboot). Though I get a command line on the NAS, it doesn't accept my user/password and I tried everything. I am 100% sure the password is correct, but no luck.
So I am running out of idea... I really wished I never did this update. So any other ideas?
Also, as mentioned above, I also tried changing the serial, but that didn't help.
-
Thanks for replying IG-88.
I am already using my real MAC addresses for all ports.
However the only thing I didn't change, was "netif_num=1", I still had it on "1".
This wasn't mentioned in the tutorial though, so dunno if it's important. Will change it now to "3" and retry.
Okay so no changes in SSH then whatsoever... Since I cannot enter the DSM GUI.
Yeah, tried a few downgrades, didn't work... Sigh. So I am really hoping I can get 6.0 to work instead.
The weird thing is, I just did another Force Install and loaded the .pat file. Then on the normal boot (1st option in bootloader).
It takes about 8 - 10 minutes and then I can access Sabnzbd, Couchpotato and Sonarr. The only thing I cannot access is DSM GUI itself... Really strange.
Also Sabnzbd is downloading. So that also works...
I also tried using a different serial (here: https://xpenology.github.io/serial_gene ... r_new.html), but also no luck.
I will now edit the "netif_num" to 3. Maybe that will help....
-
Followed the tutorial perfectly. And both firmware and DSM are both updated to 6.0.2-8451 (I can check this if I reboot in Force Install mode again).
The weird thing is, is when I wait long enough 5 - 10 minutes. I can connect suddenly to Sabnzbd, Couchpotato and Sonarr...
However I cannot seem to connect to DSM 6 at all! No matter what I try...
I have 3 LAN ports, 1 of them is an onboard Realtek port and the other 2 ports are from an Intel PCIe card.
...don't know if this matters.
My Xpenology is Intel based btw.
Also I can ping my Xpenology, but cannot connect to it through SSH or whatever.
The screen only shows "Booting the kernel" but that seems to be normal, as far as I understand.
Any idea or solution...?
If not, can I revert back to 5.2 with my backup USB stick? TY
//edit
I also tried find.synology.com and synology assistant, but neither of them can find my NAS.
The NAS can be found when it's in Forced Install mode.
//edit2
Well I wished I never ever touched this update... I cannot even go back, cannot login through SSH and/or local... Seems I completely screwed. Nice.
Hopefully someone has a solution to get DSM working again 6.0 or 5.2.... Thanks in advance.
-
Hi guys,
I have quick question and I need your advice.
After 3 years I am going to replace my current harddisk in my XPEnology system.
Currently I am running 6x 2TB harddisks in RAID 10.
Now I am going to replace these harddisks with 4x 4TB in RAID 10.
I am wondering what's the best approach to replace the harddisks without losing settings and contents obviously?
I was thinking about copying everything over to a few external harddisk I have still lying around.
Or should I use the backup function from within Synology to create backup of everything and store it on external harddisk?
What would you recommend and what is your advice in this?
Thank you in advance!
Regards,
HHawk
PS: On a sidenote; is SSD caching working nowadays? Or still not recommended?
-
Thanks for replying freddan83.
Yeah, noticed it a bit later when I was connected through terminal.
Weird though that it keeps copying the folder over and over to my Windows machine. But I am glad there is no bug.
Thank you once again.
-
Hi guys,
I bumped into something the other day, when I was making a backup of my @appstore.
In the MariaDB folder under 'usr' I have several bin folders. Like this:
@appstore\MariaDB\usr\bin\bin\bin\bin\bin\bin\bin\bin\bin\bin\bin\bin\bin\binThis goes on and on probably, but I hit a limit (on Windows, when transfering the files to my PC). The files under all the bin folders are the same.
On my Windows PC I checked how much space it was using: 1.81 GB. But that's because it hit the limit on my PC, maybe on the NAS it's even worse?
Now as for my questions;
1. Is it safe to remove the 2nd bin folder in bin? So delete the folder (and ofcourse subfolders) under /usr/bin/bin?
2. What is causing this? Any idea?
Thank you.
Regards
-
Well since I hardly received answers (except for brantje) I decided to go in kamikaze style!
Downgraded again, but this time from 5644 back to 5022.
Changed VERSION, then rebooted, did install/upgreage and and ran 5022 upgrade.
Rebooted. Samba not working, but apparently this is normal. Enabled it and noticed straight away that everything else was working also again. Even after reboots.
Will run the other upgrades now in series, skipping the patch versions (hopefully). And after I am done I hope that everything works as it should.
//update 1
Currently updating to DSM 5.2-5592 Patch 3, so far so good, no more problems at all!
Will report back in a little when I am done with the last one.
//update 2
Well the problem is, at least in my case (and 100% sure about it), DSM_DS3615xs_5644(28.10.2015).pat.
I flashed my USB stick with the XPEnoboot_DS3615xs_5.2-5644.1.img, selected install/upgrade and ran the update through Synology Assistent. Rebooted and I already noticed it was slower than normal (I can tell after running all the updates and patches). It took (for example) 3 more minutes to get into DSM. Though Web Station is still working now, I do have other problems, like: disabled FTP, SFTP, Windows File Service, NFS-service and SSH.
I will reboot a few times and see what happens, but I think I will re-downgrade to DSM 5.2-5592 (latest patch) as that version didn't cause any problems at all.
/update 3
Downgraded back to DSM 5.2-5592 and installed patches. No more problems. Will stay at this version until problems are solved.
Case closed.
-
Thanks brantje for taking the time to answer.
Yeah, I am starting to think this wasn't caused by the update. Apparently you think the same, I guess.
So if I create a VM with xpenology, what config files do I need to check? Though I have been using xponology for 2+ years, I never had to do this before. So not experienced with it.
-
I checked the logs, as far as I can with my limited knowledge and found this.
Dec 7 13:32:24 DiskStation S99zbootok.sh: Error! synoservices start timeout! (service [ "webstation" ] failed on bootup. service [ "cups-lpd" "nfsd" "synomount" "synovfsd" "pgsql" "avahi" "ssh-shell" "httpd-sys" "httpd-avahi" "sftp" "findhost" "ntpd-client" "synoindexd" "snmp" "httpd-user" "ftpd" "synosnmpcd" "nmbd" "samba" ] not ready. )
Don't know if it's useful. Also I am wondering if this even related to the update?
-
* small bump *
-
Bleh... Think I now totally fooked up.
I changed the VERSION file, to the old version, then ran DSM 5.2-5644 (28.10.15) update and rebooted, but now I can't access anything anymore. No DSM, no SSH, no nothing.
Great.
//edit
Nevermind the above, I can access DSM again (after several reboots). And it says "DSM 5.2-5644" (not 1).
Anyways, still that Web Station message and NFS, SAMBA aren't working.
If anyone has an idea, let me know. I am going to sleep. Thank you in advance.
//small update
Well apparently I can play movies from my Kodi machine from my NAS through NFS.
But SAMBA isn't working, nor is Web Station.
-
Thanks for replying djf.
I checked the cables, but while doing so, I thought that it couldn't be the problem, because I can connect to DSM interface. :S
But I checked the cables, it isn't the problem.
I noticed another issue; I cannot connect to SSH, unless I disable and re-enable SSH-service. Than it works. Sigh.
...I wish I didn't run this stupid update, or read the warning post earlier.
Anyone else has an idea? Downgrading isn't possible I presume?
//another update
Noticed something else... In DSM's 'Infocenter' the following are set to 'minus' (if I hover it, it says 'error'):
- FTP
- SFTP
- Windows-fileservice
- NFS-service
I double click them to enable them (and save them) but when I run "test" it keeps saying 'Busy with testing'.
-
Hi guys,
Unfortunately, I read the warning post a bit late. :S
I was still on 5.2-5592 and decided to update my NAS (should have postponed it, I know).
First I downloaded the DS3615xs 5.2-5644.1 x64 image and wrote it on my USB stick.
After that I booted up my NAS and installed first: DSM 5.2-5644 (28.10.15)
Installation went fine and after a few reboots it was up.
Then I downloaded: DSM 5.2-5644 Update-1
Installation went fine and after a few reboot it also came up.
However the only and main issue I have are:
1. I get the message "Web Station Service" cannot be started.
2. I cannot connect to my NAS through Windows / SMB.
I already tried disabling and enabling Windows File Service and Windows Network Detection, but no luck.
Any ideas or solution. Oh and it's not possible to downgrade to vanilla DSM 5.2-5644 (28.10.15), right?
Sorry for my ignorance. This normally doesn't happen to me. :S
Thank you in advance.
Note to myself: shouldn't have done this with a headache.
//edit
By the way; I can get the "Web Station Service" started again when I disable it and enable it, HOWEVER after a reboot it's the same problem again.
...this doesn't work for SMB / Windows File Sharing.
-
Sorry to ask this question here, but the site I used to go for tutorials and stuff ceased to exist.
I am currently running: DSM 5.1-5022 Update 2
I think I need to update the image on my USB stick and than download the latest version and just update, right? No special requirements?
Thank you and sorry for bothering.
-
Ah yes, back to square one then. I wanted to use the USB stick for the logfiles, so I can hibernate the harddisks. Now it access the harddisks, so they NEVER hibernate. That's the whole reason I wanted the logfiles on the USB stick in the first place. :S
-
Sorry, but I thought using an USB stick for the logfiles was the correct way to go?
Anyways I edited the config files back to volume1/etc... because it wasn't working from the USB stick. Couchpotato was giving the most problems.
And what do you mean with "use drive based volume"...?
Sorry for my ignorance, but I am pretty to new to Synology.
-
Okay, I installed a second USB stick for my logfiles from sabnzbd, sickbeard, couchpotato and auto-sub.
All works well until I reboot my machine. Then the applications won't start again and I must activate them by hand / manual. I think the problem is, is that the applications like sabnzbd, sickbeard, etc. start to quickly before the USB stick is initialized. Therefor it cannot read / create the necessary directories.
If I enable the apps manualy after a few seconds it works without any problems.
Anyone has an idea on how to solve this? Or a workaround?
Thank you!
-
There is definitely some misunderstanding here
First: USB stick is for booting, questions about this are already answered. (stick can be very small, will never be written to, etc.).
But your second questions is about hibernation. To make sure your system can hibernate, the disks need to be idle. If you write a lot of logfiles regularly to the disks, they never become idle, so the system will never hibernate.
To solve this, you can move those logfiles to a USB stick. I'm not sure if it's a good idea to use the same USB stick you use for booting.
Easiest is to use a second USB stick for this. This can also be small, but 64MB might be too small. I think 1 GB should be enough for logfiles of SABnzbd, Sickbeard and CouchPotato.
Just try and see if that solves the hibernation problem.
Thank you, this is what I meant.
And I did mention a 2nd USB stick, which will be 64 GB which will ONLY be used for the logfiles, as I mentioned.
-
I think there's still a gap in understanding here. The USB is NEVER written to, so the amount of free space you keep on it is irrelevant.
Thats weird. When I select to store my log-files on a (2nd) USB stick, it actually does write the log files on it. So maybe indeed a misunderstanding.
Tutorial: Install/Migrate DSM 5.2 to 6.0.2 (Jun's loader)
in Tutorials and Guides
Posted
Thank you for your answer...
...I might try this, if everything else fails.