billat29
-
Posts
351 -
Joined
-
Last visited
-
Days Won
10
Posts posted by billat29
-
-
IG-88 is the guru as his signature says. I was going to suggest that you mount the "original drives" under a recovery linux and see what data they had on them.
But I am a bit confused. Which disks? I thought you had just one 8TB disk.
-
1. The USB drive should be visible in FileStation. Right click "properties" will give you the location (my example is /volumeUSB3/usbshare).
2. In your docker compose file, there should be an ENV entry for the directory that calibre wants to see the library. (Or this would be listed in the instructions that came with the docker.
3. In the docker run command (or from the DSM GUI) map the USB volume to the docker container volume. I always use the command line, so my command would be something like
sudo docker run --name=calibrecontainer --volume=/volume3USB3/usbshare:/path-to-calibre library .........
4.Ah yes! The guid and puid that docker is using has to match that of a user that has permission to those folders.
-
If you want to build a NAS based on the Radxa HAT, then you are looking at something like OMV not Xpenology.
Looking at forum.radxa.com it looks some people have had success with OMV but a few seem to have hardware / software problems that result in the disks not being recognised.
-
I did exactly the same upgrade on a N54L with onboard nic. I used the 1.03b DS3615xs loader and made the same changes to it that I did for 1.02b.
What you also need to do is to check for and delete the .xpenoboot folder before the upgrade otherwise you may find that DSM comes up afterwards but when you log in to the DSM desktop, all the services crash.
-
Glad you resolved it. For anyone else stopping by, this problem is caused by the presence of the .xpenoboot folder placed there by a previous version. It needs to be deleted as in step 10 in this tutorial:
-
Type in the filename you wish to save to (or click the folder icon to navigate to the directory you wish to place it in). Select the device and press "Read"
Oh and the instructions said tick the box "Read Only ....."
-
1
-
-
- Outcome of the update: SUCCESSFUL
- DSM version prior update: DSM 6.1.7-15254 Update 3
- Loader version and model: Jun's Loader v1.03b - DS3615xs
- Using custom extra.lzma: NO
- Installation type: BAREMETAL - N54L Stock BIOS integrated nic
- Additional comments: Downloaded .pat from Synology Download Centre. deleted .xpenoboot directory(*).
Full migration (keep settings). Major update of all packages.
All settings preserved.
Uninstalled powerbutton and replaced with 6.2 version
* I'm so dumb. I forgot the <dot> in .xpenoboot meant hidden and so didn't find and delete it before the update.
-
I would strongly recommend that you download the latest version 6.2.3 for DS3615xs from the Synology download centre and try again.
You are much more likely to have success with that version.
Come back if you are still having problems
-
1
-
-
The DS918+ would be a good choice if you want something that just works and will receive future software updates from Synology. If you go down the Xpenology route, then you have a better, potentially more cost effective / more powerful hardware option and the fun of building your own - but you should make the assumption that 6.2 will be the last major release it will get.
(Although the guys have been brilliant at getting new releases to work so far, we cannot be sure that will continue forever).
You could, of course, keep the DS418j for file storage and get something to either do the transcoding or, depending on your requirements, maybe putting a raspberry pi or Vero box running OSMC/ Kodi to do the media playing.
-
47 minutes ago, valix said:
Of course I did. As I wrote it works perfectly for shutdown but not for startup. And I tested this with all my current and former Xpenology NAS (AMD Kabini, Intel Haswell, Intel Skylake, Intel Ivy Bridge, AMD Carizzo platforms). It never worked for startup.
I give you one task:
Set a shutdown time and 30 minutes later a startup time and please let me know if it worked for you.
I'll answer that question. Yes it does. And the answer to the second question is N54L and 6.1.7.
And the answer to the next question is "Don't Know." DSM has to write the startup date to BIOS and the BIOS must be set to allow wakeup on timer.
-
1
-
-
-
That's great! Glad you got it sorted.
-
My N54L runs 6.1.7 with the 1.02b loader. My understanding that 6.2 does not have support for the onboard nic and so people are buying and installing network cards with the intel chipset to make the later version work.
I have looked at my install notes and see that I disabled C1E in the bios (I am running a "stock" bios but that shouldn't matter) and I can't see whether I used the mac address provided in the loader or whether I used one that matched the serial number I have.
So I would check the bios; recreate the USB stick with 1.02b following Polanskiman's instructions; remove HDD drives; attach keyboard and display and watch to see whether you get the boot messages and the chance to select the appropriate option.
Once the boot is complete, then the box should be on your network. You can't install anything at that point as you have no HDD but if you get that far, then the loader is good.
-
You are most probably right.
But power schedule works for me nearly all of the time.
I offered it as a thought as the process I went through was:
1) Box stops working sometimes. Needs a hard boot. What's causing it to crash?
2) Actually, the problem is that it doesn't boot up from the power schedule. Better look at the boot process. Maybe a new USB key is needed.
3) Hang on. Maybe the problem is actually shut down related.
But yes. I can't remember if you have one of these, but if you have you will know that they are terrible dust collectors and so it would be worth opening it up, pulling the disks out, maybe the main board too, cleaning and then making sure all the connectors are re-seated properly when it goes back.
-
My N54L (6.1.7) is also on a power schedule and occasionally I find it "unresponsive" - or rather I discover that one of the services it provides has stopped working.
Blue light on but nothing doing. Power button to force off and restart cures it. The log shows the box shutting down on the power schedule but the next entry is for the forced boot.
I did various things like using a brand new USB key thinking it might have become a bit suspect over the years but the problem comes back.
But then I found the box one night when it was supposed to be off, sitting there showing the blue light as if it is on but the box was unresponsive. I think (and I can't remember whether I have seen anything on this forum to confirm), that the problem is that the box is failing to shut down cleanly. And as a result, the BIOS can't turn it back on.
I tell myself that next time instead of hard booting it I will take monitor and keyboard over to where the box lives and seeing if anything is still running but I've been telling myself that for a few months now.
-
8 hours ago, autohintbot said:
Error 13 can happen if there is a mismatch between serial # and model on the boot loader (i.e. using a DS3615xs serial with the DS3617xs loader or vice versa). Maybe that? If it isn't that--how is your synoboot.img configured in ESXi? Can expand the details in that screenshot to reveal--should be SATA 0:0. I set to "Independent - Persistent", although I don't know if that matters.
Error 13 is also a "Whoops! I had a problem writing the system to disk". This will be the drives that you intend to put data on. It can be that either it is not finding your disks or you have defined a virtual disk for testing that is too small.....
-
Each disk has a small partition on it on which is loaded DSM. This means it can boot from any disk in case of failure. The rest of the each disk is partitioned for data.
I would expect that when you insert your drives into the new hardware and boot it, it would come up with a migration. This would install the current DSM for that model (onto that small partition x5) and then update all your packages to their latest version.Some of your existing settings may survive this process. Some might not.
Your data will be fine.
I also expect that you can put 5 disks from a 12 bay into an 8 bay. But why don't you ask on the Synology forum. Obviously you say you have real DS3615 :-) -
hi all,
I am currently running 5.2 on my hp n54l baremetal. May i ask does this loader support my n54l? becoz when i try to upgrade to 6.0 with this loader. I couldnt find my server through synology assistant, neither on the web or the software. i followed the instructions, changed my usb PID. I saw the lan socket is blinking on both sides, but it seems there is no IP given to my server.is it the lan driver problem?
Thanks in advance.
No, AMD CPU is not supported on the latest loader. (N54L comes with AMD CPU)
Jun has stated there are issues with it and disabled the AMD support.
You will have to wait until there is a new loader out with support.
You can get to 6.0.2 Update 11 with the 1.01 loader (see http://xpenology.com/forum/viewtopic.php?f=2&t=22100) but that's as far as you can currently go. As bchuter says, AMD is not currently supported on the 1.02 loader. Maybe it will in future. Maybe it won't.
-
Ok. So what have you been able to do? Before attempting to add a physical disk, you should have imported the virtual machine files from June loader. Did you do that already?
EDIT:
Oh yes and my assumption is that your 3TB disk has come out of a DSM bare metal installation and is not a random disk with data on it.
EDIT AGAIN!
Ah and then I remembered. Check the VMWare documentation. I recall that Workstation only allows physical disks up to 2TB.
-
Create a new virtual machine using the wizard. You will have to create it with a virtual disk at this point. Save your new VM then go back and edit the virtual machine.
Add a new HDD (choose a sensible type that matches your real disk) and then you will get the option to use a physical disk
-
Here are the release notes https://www.synology.com/en-us/releaseNote/DS3615xs so you can see what vulnerabilities are fixed in later releases and make your decision based on that.
-
Did you get the 4Gb working? I can confirm that DSM reported 6Gb on 5.2 on my machine. I installed a crucial 4Gb ECC module some time ago and it all just works.
I can't comment on the firewall,
What I can say is that later versions of the 5.2 loader disabled writing to the BIOS and that stopped power schedules from working but other than that my box worked fine on later versions of 5.2. Do check that you have the correct setting in update and restore - important updates retaining the current version of DSM or you will be trying to get V6 working with the V5 loader!
-
Luckily I still have the logs ....
update.synology.com
checkip.synology.com
autoupdate.synology.com
Wouldn't package updates or even DSM updates go via this?
I would have thought blocking these would prevent DSM updating itself and you have to manually download and install from your PC. That may not be such a bad idea, given the number of people who post "My DSM updated itself and now it's broken".
I think my point was that apart from the discussion around QC, DSM contacts synology.com for various reasons. It could supply your external IP, serial and mac and any other information it has if it wants.
-
Imagine that for 30/50$ you get all 6.x releases, all security updates included, with a bunch of drivers ready to use, and your drives a click away. Only 50$, which is pretty much half the price one would cash out for a new HDD.
I would be very happy at that price. I suspect at that level, there would be a risk of substantial cannibalisation of their hardware business but let's see what actually happens.
Help updating my 6.1 version to 6.2
in General Installation Questions/Discussions (non-hardware specific)
Posted
It all depends on how long ago you tried the update. The first versions of 6.2 used a different driver model and caused a number of problems. 6.2.3 seems to have reverted to the "old" model and has allowed an easier update path.
So, I would try again. I would really, really suggest that you find a spare HDD and install your current version on it and then test the update process. In any case, back up all your data and settings before attempting to update your live system.
You should also look through the updates thread to see whether anyone has updated the same model (or chipset) as your Dell and see if there are any comments.
The basic steps are:
Download the 1.03b loader.
Follow the same steps you used to create your current loader (vid, pid and any other parameter changes)
Download the 6.2.3 pat file
(When you update your existing system check for the hidden .xpenoboot directory. Delete it if it exists).
Did I say "Back everything up"?
Boot from the new loader, connect via Synology Assistant or find.synology.com and it should come up with the steps to update your system. You can choose a manual install and use the .pat file you downloaded.
It should reboot (this may take a while) and when it comes up you will probably have some packages to update and then another reboot.