meimeiriver
-
Posts
104 -
Joined
-
Last visited
Posts posted by meimeiriver
-
-
10 hours ago, jitesh_88 said:
hey meimeiriver, how did you get to 6.0.2?
did you upgrade from 5.2 or clean install?
did you loose your data?
I simply upgraded to DSM 6.0.2-8451 Update 9 (which is the latest the jun loader supported). No loss of data.
My question remains, though, Is there a reliable way yet to upgrade to 6.1.1-15101-4 by now? I've been out of it for several months.
-
Current DSM version: DSM 6.0.2-8451 Update 9 (ESXi 6)Is there a reliable way yet to upgrade to 6.1.1-15101-4?
-
SOLVED!
1. During installing the usb loader went corrupted (tried twice). So after install you had to clean the usb drive(all partition) and reflash image.
2. Upgrade not work. so the only working route is to choose clean install (data folder are not deleted, you only have to rejoin domain or recreate user and assign permission. App are lost instead)
Your apps are only not installed, all your data is still there, if you backup the @appstore folder before you reinstall your apps, you can copy back the var folder to retain settings.
That is a good tip!
Thanks. -
Offtopic (like a lot in this thread
):Do we have some kind of mods here in the forum? A DSM6.1 loader would be a good start for a new thread, isn't it?. The devs and the loaders are awesome, but the forum discipline is a mess. A more structured approach with the forum would also reduce the food of noob questions over and over again. BTW: I am also one of them...
I will not be able to contribute something to the loader sources, but if you need support with the forum management, I would help for sure!
^^ Where's that Upvote button when you need it?!
Seriously, this is precisely what I was saying earlier today. This forum is full of very talented programmers, but it's often very hard to find anything. I had to call a friend, the other day, to ask what image we used again was, and he was like "Remember, it was in thread X, page Y, Z post from the top?!" It's gotten a little better, as some things have been moved to the start-post. Still, there are all these different threads going on, all relevant in there own way. Like that OVF mentioned earlier: I'm sure it's in some of the other threads; but yeah, would be nice if we had some forum manager add a wee bit of sctructure to it all.
-
Quck update...
1.02Alpha doesn't support LSI 2xxx cards - it never boots after initial installation; remove the card and you get the "please install harddrives" message.
I was wrong - after using the OVF download in another thread - everything is perfect.
this was an user error (mine).
If there's any critique to be had about this site, it would have to be that it's rather chaotic.
This OVF, I'm sure you found it somewhere, but not in any place obvious (like the start-post). Would be nice if the powers that be were a little more systematic about all of this. Now, flame away! -
Just migrated one of my "test" bare metal boxes from jun's v1.01 loader running 6.02-8451 Update 9 to jun's v1.02-Alpha loader running 6.1-15047. Migration to DSM 6.1-15047 completed without error. Testing of packages begins.
Thanks jun.
Thanks for the feedback. I will be using this method then.
-
I can see in the grub.cfg file the AMD loader is commented out, does this mean that those using Gen7 HP Microservers have to wait a little longer? Just wanted to make sure before trying to use this.
Yes, AMD loader need some extra work.
Thanks for all the hard work!
Personally, I'm not so brave, so I think I'll wait another week or so.
But, dumb question, perhaps, I haven't upgraded yet. So, will I be able to take your new loader, later on, and boot my old 6.0.9 install with it, and then do the Upgrade? Otherwise (if your new loader only supported 6.1), we'd have a chicken-and-the-egg situation. -
Where's jun when you need him for a new loader?!
Seriously, I appreciate all the work done by the coders; but yeah, it looks like I'm going to wait this one out, until an entirely new loader exists.
Boohoo, an update came out and the dev wasn't magically able to make it work in a matter of days. What were you expecting, seriously?
A bit of a strange reaction, don't you think?! Especially since all I really said was that I appreciate all the work done by the coders, but that it really looks like I will just need to wait a bit before a new loader comes -- OMG, the horror of saying such a thing! (Yeah, mate, that was sarcasm, in case you didn't realize it).
In fact it looks like I -- and apparently others -- have learned from last time, and have not hastily upgraded our system. That's a good thing. My current .9 install still runs fine. I can afford to wait it out. So can you.
-
Anyone ever heard of snapshots? Have a nice day.
Like I said earlier, unless you're using ESXi without a pass-thru array, reverting to snapshot is not going to do any good. Have a nice day.
-
Where's jun when you need him for a new loader?!
Seriously, I appreciate all the work done by the coders; but yeah, it looks like I'm going to wait this one out, until an entirely new loader exists.
-
Happily this happens on a test VM ; so recovery is not a problem.
What are you guys talking about?! Unless you're using ESXi without a pass-thru array, reverting to snapshot is not going to do any good.
I use LSI 9207-8i passthrough
Hence, that's what I don't understand.
The DSM Upgrade is going to take place on your pass-thru disks, whereas a VM snapshot does not include your array. So, how would a 'revert to snapshot' undo the Upgrade then?! -
Happily this happens on a test VM ; so recovery is not a problem.
What are you guys talking about?! Unless you're using ESXi without a pass-thru array, reverting to snapshot is not going to do any good.
-
"Due to infrastructure update, packages will need re-initialization after upgrading to DSM 6.1."
And what the heck is that?! You will need to reinstall all your packages!? (Like SABNZB)
-
That's funny, I did the same test on ESXI and it failed.
Sent from my XT1565 using Tapatalk
What exactly failed? Don't want to go thru the same s*** again as last time.
-
Update 9 was installed successfully. (DSM on VMware Workstation with Jun's Mod V1.0)
The only problem was that no IP was assigned via DHCP after the update! I also tried several hard resets without success.
My solution was to change the Network Device in the .vmx file from e1000 to e1000e!
ethernet0.virtualDev = "e1000e"
Was your jun package not set to use e100e already then?! Mine was, and update still fubarred.
-
For all ESXI users:
I've changed NIC type in my ESXI vm from VMXNET 3 to E1000E and now DSM is accessible after update 9
It was already on E1000E for me (and still is).
That link is not V1.01. Here is the official link from the OP: https://mega.nz/#F!18kB1BTB!1ft3N5Hnrcnqsneu0aQUkA
And that jun 1.1 ovf package still won't load for me on ESXi 6.5.0. Can someone PLEASE tell me how they got it working?!
Try the following from Koroziv. Download his .ovf and import that into Esxi. This worked for me on Esxi 6.0 and i upgraded my Esxi to 6.5 yesterday and DSM is still running fine with this and Update 9
For esxi users : here you have an ovf vm export that will make the install easier:https://mega.nz/#!Vk40FCDT!r2ertz7Eyoeh ... W2p1GLgzfs
All you need to do after import is to add your drives and edit ram/cpu to your needs (comes with 2x2cpu and 4 Gb ram), then start the vm and continue with the install process. It will start with the vmware boot option automatically, and after the install you will not see the 50mb boot drive. I didn't edit a thing in the cfg (vid or pid)
This is the loader on the first page of this topic, latest version, I just made it more easy to use it for esxi users. Here is the process:
I had to import the original vm in VMware Workstation Pro (I had errors at import in esxi 6.5), and chage to hw version 10, export to new ovf; imported the new ovf in esxi, edited a few things, start once to retain the vmware boot option, changed the boot drive to non-persistent (it's hidden in xpeno now) and exported again to the ovf in the link for easy future use. I hope it will be useful to others to; if I messed up something let me know, for me and a few others this worked nice.
Edit:
On my gen8 microserver I don't have and can't add an usb3 controller; this could be a poor choice at vm guest os version, I put "other 3.x or later linux x64", did not tried any other way yet.
Edit 2:
The usb3 issue is not present on the atached hw 10 ovf(the one in the link), you can add usb3 controller in it; my xpeno install is on a vm with hw 13 and that is why I can't add an usb3 controller.
Thank you very kindly!! That koroziv guy, and you, may yet save my day!
P.S. Seems he had the same experience: "I had errors at import in esxi 6.5". So it wasn't just me.
-
For all ESXI users:
I've changed NIC type in my ESXI vm from VMXNET 3 to E1000E and now DSM is accessible after update 9
It was already on E1000E for me (and still is).
That link is not V1.01. Here is the official link from the OP: https://mega.nz/#F!18kB1BTB!1ft3N5Hnrcnqsneu0aQUkA
And that jun 1.1 ovf package still won't load for me on ESXi 6.5.0. Can someone PLEASE tell me how they got it working?!
-
Using this jun 1.1 image, btw, from the start post:
"Updated loader by Arcao latest images (10-28-2016) : https://mega.nz/#F!Oc8TCLgD!IiullNuGs95RlelM9SKd5w"
That link is not V1.01. Here is the official link from the OP: https://mega.nz/#F!18kB1BTB!1ft3N5Hnrcnqsneu0aQUkA
The other link has a sub-dir with 'jun's images'.
Just to be sure, I downloaded the one from your link, but it's the same, and won't install.Anyone?! I'm using the latest ESXi 6.5.0 machine. This thing just won't upload. Sigh. When it rains, it pours.
-
Using this jun 1.1 image, btw, from the start post:
"Updated loader by Arcao latest images (10-28-2016) : https://mega.nz/#F!Oc8TCLgD!IiullNuGs95RlelM9SKd5w"
That link is not V1.01. Here is the official link from the OP: https://mega.nz/#F!18kB1BTB!1ft3N5Hnrcnqsneu0aQUkA
The other link has a sub-dir with 'jun's images'.
Just to be sure, I downloaded the one from your link, but it's the same, and won't install. -
Please report back once you update to v1.01. I am curious to know whether this could be due to people using V.1.0
Yeah, this is not going well. When I try to intall the jun 1.1 version, ESXi 6.02 says: "failed to deploy ovf package", "error uploading synoboot.vmdk".
Using this jun 1.1 image, btw, from the start post:
"Updated loader by Arcao latest images (10-28-2016) : https://mega.nz/#F!Oc8TCLgD!IiullNuGs95RlelM9SKd5w"
-
Please report back once you update to v1.01. I am curious to know whether this could be due to people using V.1.0
Yeah, this is not going well. When I try to intall the jun 1.1 version, ESXi 6.02 says: "failed to deploy ovf package", "error uploading synoboot.vmdk".
-
Using Juns pre-packaged Esxi vmdk I have ran into an issue on Esxi 6.2 patched all the way.
(...)
SCRATCH ALL THAT! I wan using jun 1.0 vmdk. no wonder I couldnt get it going. after loading correct boot 9 went on fine
So, which image are you using now then?!
v1.01
Okay, thx. I'll give that a try.
-
Using Juns pre-packaged Esxi vmdk I have ran into an issue on Esxi 6.2 patched all the way.
(...)
SCRATCH ALL THAT! I wan using jun 1.0 vmdk. no wonder I couldnt get it going. after loading correct boot 9 went on fine
So, which image are you using now then?!
-
I installed update 9.
But can't get the ip.
i tried
ifconfig eth0 up
and it told me: eth0: ERROR while getting interface flags: No such device
I tried to reboot and reboot, it doesn't work.
I use KVM.
And you're the lucky one! Me, I'm stuck with a VMware image that doesn't even have a console!
DSM 6.1.x Loader
in Loaders
Posted
Let me get this straight, you had to a clean install or an update? Really don't want to lose my data. Thx.