dynax
-
Posts
47 -
Joined
-
Last visited
Posts posted by dynax
-
-
I am very sure HD hibernation does not work wit Jun's loaders when the loaders came out. I am not sure if anyone ever work out a patch for it. I was away for months so I am not that up to date on what's going on with xpenolgy.
-
You can host another VM (win/linux etc) on the same ESXi host to use find.synology.com from that VM (via remote log in that VM).
-
Polanskiman/everyone
last time I check, DSM 6.0 won't let the HDD go to sleep mode. Is this fixed in the current version?
Does anyone has a ovf for ESXi 5.5 of the newest loader?
Thanks
-
1
-
-
I would tape close the inlet holes right below the hot swap bays. I would also tape close the side panel inlet holes. That way all the air is forced thru the hot swap bays cooling the HDD.
As a trade off, your CPU and other components will run hotter. If everything gets too hot then get a spot cooling fan and mount it over the hot components to mix the air up and remove hot stagnant air.
-
the update addresses are stored in
/etc/synoinfo.confhere are some text from the file
# DSM auto update default server rss_server="http://update.synology.com/autoupdate/genRSS.php" package_update_channel="beta" update_server="http://update.synology.com/" small_info_path="http://update.synology.com/smallupdate" enable_pkg_autoupdate_all="no" pushservice_ds_info_updated="yes" rss_server_ssl="https://update.synology.com/autoupdate/genRSS.php" dsm_autoupdate_type="download"Change it to whatever to be on a safe side.
dynax
-
I am not sure exactly what you mean from your post. But if you want Xpenology to see to use your RAID share natively (as volume2 for example), you can do just that.
On your Xpenology, create a very small volume2. Then ssh onto your Xpenology box
Edit the file
/etc/rc
search for the line
# checking and Mounting filesystem(s) ...
/usr/syno/bin/synobootseq --set-check-fs >/dev/null 2>&1
/etc.defaults/rc.volume start
/etc.defaults/rc.syn start
Add the above line (/etc.defaults/rc.syn start) below the rc.volume start
Now you need to create file rc.syn in /etc.defaults
In that rc.syn file put in the 3 lines:
umount /volume2
sleep 2
mount -t nfs 192.168.1.100:/mnt/Vol01/Synology /volume2
Make the rc.syn file executable.
Obviously, I use 192.168.1.100 as your host IP and /mnt/Vol01/Synology is just an example share location. Change it to match your setup.
root users on both your xpenology and host must have the same password.
After everything is done, in Xpenology you'll see that your small dummy volume2 is replaced with your RAID share. You can create shares and stuffs in Xpenology on that volume2.
-
BTFRS vs SHR is the same as Apple vs Orange.
One is a file system, the other is a RAID management.
-
I attempted to inject firmware into image via OFSMount with no success.
sorry i'm just guessing, its what i would try so ....
looking further into the extra.lzma, there is /etc/rc.modules
...
EXTRA_FIRMWARES="bnx2/bnx2-rv2p-09ax-6.0.17.fw bnx2/bnx2-rv2p-09-6.0.17.fw bnx2/bnx2-rv2p-06-6.0.15.fw tigon/tg3_tso5.bin tigon/tg3_tso.bin tigon/tg3.bin"
...
so looks like the firmware file has to be mentioned in that file to work?
I am not sure if jun compiled or just tossed a kernel ID. Guessing its not compiled for 3.10Tossed a kernel ID? Not sure what that is supposed to mean but if modules were not compiled against the proper source code they would simply not work. Do not confuse modules and firmware.
All modules within the v1.02a (or v1.02a2) loaders are compiled against DSM 6.1 source code and made to work with linux kernel 3.10.102. There is no other way around. In your case, the firmware seems to be missing. I checked the extra ramdisk and it is not there. The rc.modules also needs to be updated with the added firmware or whatever module you add in the ramdisk else it wont be loaded during kernel boot. I have made the necessary changes in the ramdisk. Let me know if it works (or not). I can't test it myself since I do not have that NIC.
https://mega.nz/#!OQplzISJ!L6HzXJq2ZwX- ... k99jYVwKBc
note to myself: This ramdisk only contains the additional firmware bnx2-mips-09-6.2.1b.fw on top of the default ones added by Jun. Nothing else.
The original DSM 6.0 loader/modules was compiled with beta source code. Are you saying the DSm 6.1 loader (1.02a and such) was compiled with the released source code? if I remember correctly, the loader was available before the source code was.
thanks
-
If you have a real Synology box, take a picture of it with MAC address/serial number then contact them. They'll get you sorted out.
Until then, don't use quick connect. It will only be a matter of time before all external-access apps calls home for validation when they got sick of the abuse.
-
xpenology 5.2 works well with ASRock q1900-itx board. In BIOS, set the boot csm to legacy.
-
If you use ESXi 5.5 (or newer)
1) Use this loader (jun's)
https://mega.nz/#!5koz0ZjZ!SLWdLCD2db22 ... m-aJQ4w2gI
2) Add a HDD
3) Then download the 6.1 pat file (DSM_DS3615xs_15047.pat) and install that
That is a clean install.
If you want to upgrade from your previous DSM. then skip step (2). Reboot and you are done.
-
Yeah this is what I did, it worked perfectly. The only downside to Jun's loader is it didn't work with LSI 9211-8I (flashed to IT P20). So I used the cheap IO Crest PEX40064 for now.
Try this https://mega.nz/#!Ul5RXKQR!_IiCurbduvbR ... ggqj5vo_Sg
I think it would work with LSI-9211. It has been a while and I don't even remember if the driver for your control was included or not.
-
Is this loader still based on the beta code similar to jun's loader?
-
[quote name="cuspess"
Hey people' date=' while I am hoping to hear some experience sharing regarding the problem I faced, I have been researching and came across a statement saying "USB boot is not supported in ESXi". Can someone with related knowledge confirm that??
Thanks[/quote]
ESXi does not support VM booting from USB. You can work around the issue with "plop boot manager". Basically, you use CDROM iso as a boot drive in your VM, which then points to the USB stick.
I am not sure it's worth the trouble. If you want to edit the config file on the VM, you can just do that, there's no need to use a USB image as a work around.
-
Updates!
I succeed and got it Xpenology setup finally. Enlighten by post from above I came across the OVF file made and shared for use in ESXi 5.5, take a shot and use it instead of the one from op, and everything setup normally without a glitch. Worth noting I am on ESXi 6.0 not 5.5, so I am not sure if there is any issue to use that OVF, but as long as it works I am very pleased now. Thank you everyone here. Superb effort guys! cheers
If you are talking about the ESXi 5.5 OVF that I uploaded then it's the same as jun 1.01 OVF. I only made it compatible with ESXi 5.5 and the Classic vSphere Client since I don't like the web client.
-
I hope restore config saved in 5.2 will work.
Not sure using a restore from an older version is a good idea.
Restore config works great. That's actually a a step to move from ext4 to btrfs
-
what bglf83 means is this
Setup a hypervisor on your hardware (KVM, ESXi etc). Xpenology is a NAS VM, low memory, low CPU. Use Win7 (just an example) as a Flex Server VM. This one can use all the CPU power you have.
An alternative is install Ubuntu (or any Linux really) on your hardware. Within Ubuntu, setup a Xpenology VM (via KVM). Flex is installed on the main Ubunto.
I would advise against running a heavily utilized app onto the Xpenology DSM. That just makes it hard to figure out where the issue is when something goes wrong.
-
I tried to import the .ovf from DS3615xs 6.0.2 Jun's Mod V1.01 to my ESXi 6u2 server, but i got a 'Failed to deploy' message (IOError). I have downloaded the .zip again (maybe it was corrupt), but i got the same error.
How can i get it working
?For those users who still stay on ESXi 5.5 and dislike the vCenter Web Client, here's ovf file:
https://mega.nz/#!Ul5RXKQR!_IiCurbduvbR ... ggqj5vo_Sg
Don't forget to add a Harddrive before setup. This is jun's 1.01 converted to HW 8.0
-
Hello everyone,
First of all, thanks to everyone trying to make this new dsm work, excellent job!
Now, i have a Dell PERC H200 flashed to a LSI 9211-8i, it was working perfectly on DSM 5.2 but on this one as long as the card is plugged, nothing boot, i get the "Booting Kernel" screen but never find the NAS on the network, without it, no problem, everything goes smoothly.I'm using the arcao V2 image. If anyone knows a easy fix, let me know
Thanks
I am very sure there won't be a fix for this one until the proper source code is released.
-
Nice job Arcao, works even fine for me and my GA-170N-WIFI Board without a serial port. But I can only use one port, can you bring in the Intel i219 Ethernet port driver. This would be nice. After that, I can go to production system with DSM 6
The source code used in this this loader came from DSM6 beta2. I wouldn't trust my "production" data on a beta source code.
-
Was someone able to replace the vmware boot image with jun's version?
When i booted after replacing the boot image, the migration wizzard appared in http://find.synology.com and i was affraid to continue and lose my data.
With Oktisme's bootloader, the boot image uses ide and my data drive sata.
With Jun's bootloader, the boot images uses sata and my data drive scsi.
At the end I made a clean new installation with Jun's bootloader and manually migrated the essential data (basicly dockerfiles and persistant docker data)
If there is a way to simply change the bootloader, i would appreaciate if someone writes a migration "guide" and the ops would close this thread afterwards.
You won't lose your data that way. The sata/ide/scsi data drives doesn't matter. Synology doesn't care. As long as there are drivers for your controller in the new loader (sata/ide/scsi) and there are valid OS (pat file) file installed in the drive, migration will work.
-
Thanks for your reply.
I get the backup wizard. I log in, and then get to a page (synoauth.synology.com) that says:
Redirect your personal information back to http://192.168.14.10:5000, please make sure http://192.168.14.10:5000 is your DS domain.
After I confirm and click 'Next', it's just an empty page.
P.S. If Hyper Backup requires the use of Synology services (does it?) then never mind: like others, I don't mind using Xpenology, but don't feel like defrauding Synology by using fake serials, etc. Otherwise I'd still like to know.
Even on the real Synology box, I got the blank page the first time. Close it and try again and everything seems to work.
On the Xpenology box, I got the same situation (close the browser and try again and it seems to work).
I saw the synoauth.synology.com address also. This is the first time I saw an app bounces traffic around like that.
-
Is anyone using the latest DSM Hyper Backup with Amazon Drive?! All I'm getting is a blank screen when I initiate the Hyper Backup and connect to the cloud.
Anyone have an answer to this, btw?
At which step do you have a blank screen?
If I click on Hyper Backup, it launches backup Wizard. I then can select S3 then [Next] and a backup destination settings opened up. I don't have the keys needed to go further.
Up until that point, it seems to work fine on my end.
-
To clarify, I started trying out the xpenology only a few months back and only started to play with qc in this dsm6, in the last week or two. I never needed the service. I don't really know what this is all about, until I found out that it could be useful for Ds cloud to back up iphone. I have yet to sort it out how. I is not working as I expected it to ( I would want it backup my iphone, but not necessarily sync, I want the files stay in the NAS even after they are being deleted from the phone). That is not the case, therefore it really has no use for me. However, this is not the reason I am stopping using it. Thank those who made me become aware that this is a mis-use of Synology service. I have no intention to harm the community, the project and Synology.
However, I don like the rheteric of how thi mesage is being conveyed to people like me. I f offended and mis-characterised. It would be more constructive if the messages are less person-oriented. This does not mean I am condoning myself.
A couple of technical questions. I am not a computer guy at all.
1, I have difficulty configuring the "external access" function as someone pointed out. I have a pfsense box with VPN service running. When I try to set up t router through "external access", it always tells me something like "I have two routers in the network". If I turn off the VPN, it seems to work. Anyway I can set it up with VPN running?
2, if I use the serial and mac address from an old Synology box, would that be okay?
Thanks
You can definitely do what you want with DS cloud app on iPhone w/o QC.
DS Cloud listens to port 6690. On your router, you need to open this port to your Xpenology IP address. You can then just use many of the free DDNS service to link you DS Cloud App back to Xpenology.
On your iPhone DS cloud app, click on the first ICON "Cloud Station". You should see the folder that you picked for "sync". Click on the (!) on the right of that folder name. Under Sync direction, select "Upload only".
Now, after upload your photo to your Xpenology, you can delete those on the iPhone and stuffs on the Xpenology remain.
Technically speaking, there's nothing illegal/wrong with Xpenology project since it's based on opened source codes. Synology can't stop Xpenology if they wanted to. Quick Connect is a Synology service licensed only for their hardware's.
Synology can easily make the apps (not DSM itself but the apps within it) stop working if detected a non-genuine MAC/SN from their data base. All they need to do is delay their release of the source code for a few years and the project will die eventually (or they can just encrypt it better).
For (1), I don't quite understand your question. You have pfsense box that provides VPN server and you also have VPN server turned on in Xpenology? The option for "Router Configuration" in External Access is just a fancy way to open port in your router, it won't work if it sees 2 routers on your network. You can open port manually.
When people talk about "External access" they typically mean the first tab "DDNS" setup. That's where you do your setup to replace QC.
For (2) if you have a genuine Synology box, you can use its MAC/SN. in fact, a few years ago (before the xls file became public), many ppl bought broken Synology boxes just for the valid MAC/SN.
DSM 6.1.x iLO
in DSM 6.x
Posted
I know it can be done as Quicknick did it in his loader configuration tool.
Maybe he made entry that loads the Linux kernel and run a script by passing init=/path/script
or he pass custom argument on the kernel command line. I've never tried so I can't pin down the specific. You may want to contact him to see how he did it.
It's best to get a DNS server up and running on your ESXi host. Then you can SSH onto the ESXi host to see the IP address of your xpenology (or any VM for that matter).
If you don't have physical access to the hardware then how are you going to get the hard drives for your NAS installed? For best/most stable config, you'll need to PCI-pass thru the entire HBA controller.