-
Posts
156 -
Joined
-
Last visited
-
Days Won
1
Posts posted by filippo333
-
-
No real reason for VirtualBox when Synology is providing a QEMU/KVM alternative for DSM 6 called "Virtual DSM Manager".
Well not really, Virtual DSM Manager only allows you to run additional DSM instances from my understanding? Virtualbox allows you to run any supported guest OS whereas Docker's approach, feature-set and use-cases are entirely different.
-
That's fine, just wanted an update was all
-
Quicknick's 2.2 loader doesn't even support BTRFS which arguably is the main reason to jump to DSM 6.0 in the first place. There isn't a good reason to use the old 2.2 loader, better to use something which isn't riddled with issues.
I see that June's loader also doesn't support BTRFS yet. Power button usage on baremetal also doesn't work. But right now it's the only option I guess.
You are right. Everyone just keep calm.
Sent from my SM-G920I using Tapatalk
Jun's loader does support BTRFS as I have a 2TB array which has been rock solid since I created it
-
The advice is that 2.2 is quite broken which is why it has been taken down, if you want to use DSM6 then use jun's loader, viewtopic.php?f=2&t=20216 and let quicknix finish his work in peace.
+1 My advice is also for people to use Jun's loader rather than 2.2 given how many issues it has. I've been running Jun's latest loader with no serious issues for almost 2 months now. There are minor things which may not work such as HDD standby and altering the packet size of your IPV4 connection (don't do this as it will crash your network driver); but overall it's stable and works.
-
Quicknick, is there a guide to upgrading, and do you know if its stable enough to upgrade without losing packages and configuration?
Would be nice to know, though I'm sure the community/quicknick will take care of it once he's actually released the next version. There are a lot of unknowns until we have a stable build.
-
Guys,
finally I am running on Juns loader, dsm update 4. Is it safe to do in dsm automatic upgrade to update 7?
Thank you.
Yep, I'm currently running Jun's loader on update 7 with no issues!
-
Hi,
forgot to say that $sataportmap isn't expanded well
cat /proc/cmdline ihd_num=0 syno_hdd_powerup_seq=0 HddHotplug=0 syno_hw_version=DS3615xs vender_format_version=2 console=ttyS0,115200n8 withefi root=/dev/md0 sn=XXXXXXXXXX netif_num=2 mac1=001132XXXXXX mac2=001132XXXXXX synoboot_satadom=1 DiskIdxMap=0C $sataportmap SasIdxMap=0 quiet
for instance, I've made it hard in grub-quicknick-v2.cfg
set sata_args='sata_uid=1 sata_pcislot=5 synoboot_satadom=1 DiskIdxMap=0C SataPortMap=4 SasIdxMap=0'
This was resolved on the 2.3 bootloader.
I almost feel like we need a bug tracker, so people can easily see what issues are/aren't known.
-
So I fanally managed to access XPEnology tool, so I decided to enable SHR and to update it. I did these steps in this order:
1) 12. Enable/Disable Synology Hybrid Raid (SHR) enabled by default
2) 18. Update XPEnology Ramdisk/Drivers/Kernel
3) 19. Update XPEnology Configuration Tool
Then any volume I tried to create was crashing. I tried with 3 different drives.
So I decided to reformat the USB stick, recreate the boot drive with the same image I used before then reinstall XPEnology. Then I enabled only SHR without updating the tool (I read somewhere that an update will crash the volumes), but it still crashes!!!!!
Any solution or advice?
Please everyone with 2.2 don't update. The intial size was not big enough to handle updates. 2.3 addresses this by providing a new boot loader with ample space for updates.
Also issues that were in 2.2 are resolved and it will be fully operational.
Sent from my SM-N920T using Tapatalk
Is there a PayPal link somewhere for donations?
-
I have been trying to install this on a baremetal gen 8 microserver but I keep getting the error Failed to install the file. The file is probably corrupted. (13)"
I have made sure 100% that the vid and pid is correct and that the pat file is not corrupted but comparing md5.
Can anyone assist? Thanks
hi I got this running fine on a gen 8 microserver
only issues drives must be in ext4 has most people know
and it is not find data on external usb hard drive work fine on the jun release one this is just on a usb pen stick in side the machine
very good so far
backupking
Btrfs is fixed in 2.3. I had a bad ecryptfs kernel module
Sent from my SM-N920T using Tapatalk
I have a quick question quicknick (no pun intended)
I am currently using Jun's loader on my BTRFS volume, would upgrading to 2.3 require just re-imaging my boot USB and ensuring the same serial number, mac address etc are the same? In theory my Synology install volume and BTRFS partition should be picked up using a different bootloader correct?
-
Thanks to everyone for the new loader.
I have read this thread several times over the last few weeks and haven't seen any mention of hibernation issues. Does the current loader allow for HDD hibernation and auto poweroff?
Has the 5.2-5967 issue carried over to the DSM 6 loader? OR is it just me?
Thanks
HDD Hibernation does appear to be an issue for me too both SATA and USB 3.0 on my Skylake system. I remember Hibernation working using Quicknick's 2.2 loader.
-
Does anyone successfull install in VM Ware workstation 12?
If I try to connect via ssh and the private RSA key is still get a second login promt with password.
Also connect via serial doesn't work.
I can't even get an IP address using Workstation 12 so you've gotten further than me!
-
When is the hopeful date to have Upgrade instructions for people coming from 5.2 ?
I used this http://www.xpenology.com/forum/viewtopic.php?f=2&t=22100 to upgrade from 5.2 worked perfectly
Update instructions are intentionally left blank until rerelease. I jumped the gun thinking it was ready, but missed a couple of things. Don't worry it will be back.
Sent from my SM-N920T using Tapatalk
Any rough idea when to expect 2.3 quicknick?
-
Here is what I used on esxi 6.5, on a hp gen8 microserver :
https://mega.nz/#!Vk40FCDT!r2ertz7Eyoeh ... W2p1GLgzfs
It's jun's loader 1.01. Add drive and install.
If you want to modify the grub cfg you need to set the boot drive as dependent or persistent before edit. But I see no need for abusing synology services, a free dns is all you need.
The vm comes with 2x2 cpu and 4 GB ram, change it to your needs.
edit:
here is how you can edit grub after dsm6 install (make sure the boot drive is NOT non-persistent for this to work):
SSH into dsm and type
echo 1 > /proc/sys/kernel/syno_install_flag
mount /dev/synoboot1 /mnt
/mnt/grub/grub.cfg
umount /mnt
or for using winscp to edit the file with notepad++ (vi editor is not that hard, but...):
1. Login using putty or any other ssh client with administrator account (usually "admin")
2. You will be asked for a password. Enter the one for the administrator account
3. You will get a command prompt
4. Enter: sudo su -
5. You will be asked for a password. Enter again the one for the administrator account
6. You will get a command prompt root@...
7. Enter command: synouser --setpw root your_new_root_password
For "your_new_root_password" please use the desired password for root account.
Nou you can do
SSH into dsm and type
echo 1 > /proc/sys/kernel/syno_install_flag
mount /dev/synoboot1 /mnt
login using winscp (user root and the password you set before) an go to /mnt/grub/ and edit grub.cfg Save and close editor when finished.
Get back to the ssh sesion and do
umount /mnt
Shut down dsm normally (not from esxi cli or webui) and edit the vm setting - change the boot drive back to non-persistent.
Hey Koroziv,
Thank you very much for this information. I have been able upgrade from 5.2 to 6.0.2 with such ease. All my data migrated easily. Everything works OK. Many thanks folks for your priceless contributions to this community.
I'm guessing your file-system is formatted as EXT4?
-
My question regarding this is, if you're installing it from VMWare you wont have any USB stick plugged in - did i miss something?
Ah you may be correct, only when USB booting you need a VID/PID. Have you not tried deploying the OVF file specific for VMware?
-
Wait, Quicknick has released v.2.3 of his tool?
Yes, as stated during the update process.
I'm not sure how official it is since he hasn't updated his downloads post yet, he did say he'd be working on 2.3 tomorrow during his 3.5hr flight.
-
Mainboard: MSI Z77A-GD65 (Z77 chipset)
5.) Updated the config tool to V2.3
Wait, Quicknick has released v.2.3 of his tool?
-
I am running it in ESXI 5.1 on HP54L. I have manged to configure the bootloader via ssh. But the problem is when I try to install DSM pat file it gives me an error.
Any ideas? I got the pat file from the synology website.
Make sure your PID/VID is correct, this is a known problem. The setup assistant will not recognise any DSM firmware if it cannot verify where the install disk is physically on your system. Read quicknick's instructions on how to find your IDs http://xpenology.com/forum/viewtopic.php?f=2&t=24308
Both should be formatted in along the lines of 0x0000.
-
Sorry everyone was not able to do much today, but will be on a 3.5 hr flight on Tuesday, so I will be working on this then.
The baremetal is good to go, a little more testing and I can release 2.3. I am still trying to clean some things up for ESXi build and do some thorough checks and balances. I want to make sure the second release goes well.
Sent from my SM-N920T using Tapatalk
If it helps, I have a bare bones Skylake i3 system I'm not actively using. I could do some testing for you if you list what needs testing on the new build
Thanks for the hard work quicknick
-
Could someone with better english skills please confirm if you only see the config screen via ssh?
I am under the impression one should see the menu on the screen too?
Is that correct?
You will only see a menu once you've SSH'ed onto your box when in Configuration Tool mode. There will be nothing further visible on your screen past "Booting the kernel". Instructions are in quicknick's post on how to get the IP address in addition on how to connect using the SSH auth key (there is no default password).
-
This happens every single time I go to create a BTRFS volume. Pool is entirely initialised :'(
It never happened with Jun's 1.01 loader!
This is because I included Synolog's btrfs module in a different way. This will be fixed in 2.3.
Sent from my SM-N920T using Tapatalk
Thanks for updating us quicknick
-
This happens every single time I go to create a BTRFS volume. Pool is entirely initialised :'(
It never happened with Jun's 1.01 loader!
-
My BTRFS volume remains crashed even after re-creating it. I fully initialised my RAID volume before-hand (this didn't happen with the previous experimental DSM 6 bootloader).
Help!
-
I'm confused, how am I supposed to get a SSH password if I do not have a serial port on my bare metal machine?
password is only for Telnet. Read the FAQs on how to connect via SSH. It is pretty clear.
Nevermind, I found it when digging through your instructions!
Tldr for others; download private SSH key and use that for authentication in Putty or whatever SSH client you have. Login as root with no password.
-
I'm confused, how am I supposed to get a SSH password if I do not have a serial port on my bare metal machine?
DSM 6.1.x Loader
in Loaders
Posted
If your pendrive is not visible after a reboot, it's more than likely a BIOS/UEFI issue (flash it to the latest version) equally it could be a dud pendrive.