fonix232
-
Posts
324 -
Joined
-
Last visited
-
Days Won
1
Everything posted by fonix232
-
try rebooting ur router - had this issue the other day with my Synology DS916+II - after a router reboot I could find it with find.synology.com with no prob. Been there, done that. I did the whole shebang of debugging for hours before posting it. The funny thing is that even my router won't show it, so it gets no IP address at all.
-
Okay, now I'm having the same issue. System set up properly, USB PID and VID matches, serial and MAC matches, aaaand it doesn't work. Nothing on the network. Nothing found by Synology's tool or find.synology.com. Interesting. Loader is v1.01, with the same USB drive I've been using for months.
-
Make sure that your boot USB has been properly updated with the matching PID and VID. 9 out of 10 cases happens because of this.
-
Yes we are. This is a topic for Jun's loader, let it be for 6.0.2 or 6.1 - your question however is totally off topic and should be in a separate thread. Don't try to play smart. I didn't specifically mention XPEnology DSM in my question, but since I posted it here in this thread I'mm sure most would assume that is what i was talking about seeing how there is a vmdx for Jun's loader.. tell me how it wasn't relevant to the discussion? This is honestly the first place I've seen mentioned about running a NAS inside a VM. Your question was whether it's worth to run a NAS OS in a VM. Completely unrelated to the actual topic of the loader. Here, discussion should be limited to the following topics: a, Discussion of usage of the loader b, Discussion of bugs/missing drivers of the loader c, Discussion of possible upgrades to the loader (e.g. if 6.2 introduces a new defense mechanism, like they did with 5.something with the PCIe device check) Your topic falls into neither of these topics.
-
Why not open a new thread? This is a forum and not a chatboard. Once again the question: are there any Mods around here? Are we really going there with the semantics? The terms message board and forum are pretty much used interchangeably ever since the dawn of internet. Since we are talking about mainly DSM 6.1 in the thread labeled 6.0.2, a new thread should have been started weeks ago. Yes we are. This is a topic for Jun's loader, let it be for 6.0.2 or 6.1 - your question however is totally off topic and should be in a separate thread. Don't try to play smart.
-
besides bragging rights that 3617 > 3615, from everything I've read 3615 doesn't limit usable hardware in any way "quad core cpu, more mem etc" most likely the available ad-on Synology packages may differ from the detected hardware version. Someone correct me if I am wrong here. No, the loaders do not modify the accessible hardware, and the sys info page saying a different CPU is because it's a burnt-in value per model. However the 3615 might not get future updates, while the 3617 will (since it's a newer model).
-
Indeed. As we speak! Not sure all the source code is included though looking at the size of the source. We shall wait they finish the uploads. Apparently they're done. As far as I see, all the sources we need are available. Synology also made a Docker/KVM package/image available, so I was thinking, maybe it would be possible to use a baseline Linux distro with Docker/KVM, and run it inside that? That way most of the hackery to get around their security wouldn't be needed.
-
So now is it the SSD cache, or the portmap setup?
-
Or you could just boot the GParted Live USB, which does all the array building for you
-
@fonix232 - what commands must I run? Sorry for the late reply. Use lspci, or even better, if you can get it installed, lshw, and of course, lsmod to check the kernel modules.
-
Have you tried setting SataPortMap to 4/6? It might help
-
Thanks for the info.. I'm just using an old Dell desktop to test the release - which has definitely only got 2 Sata ports (and two drives connected) - so I guess it's going to be 2 anyway.. When I go to use it on my main NAS system - probably when it's out of Alpha - it's probably going to be slightly different (it has 6 sata ports).. My point, I guess, was that I don't think this sataportmap command was being used at all in the original grub.cfg. I couldnt see where the sata_args list was called, so I moved sataportmap from it and into the common_args list (I could see where this was called). The sataportmap setting was present in older versions of the grub.cfg and it was the cause of my previous issues in 6.0.1... #H Might be, as it was said before, the 1.0.2 loader is still an alpha. Before you install on your main NAS, make sure to check the mobo info, so your SataPortMap matches it. It will most probably be 42, unless there's only the onboard controller, driving all 6 ports (in which case you need to use SataPortMap=6).
-
Did anyone reverse engineer Photo Station ?
fonix232 replied to Exchizz's topic in Synology Packages
Plex is nice for streaming movies, but how does this relate to my question :> ? \Exchizz Plex has a photo sync feature which pretty much "just works". You need to purchase the client (5$ one time) or pay for the subscription, though, to use it. -
Looks like the installer hasn't been updated for 6.1, and results in this error. Why don't you take the easier approach and deploy Docker containers with MariaDB? It would certainly be safer.
-
SHR was a custom implementation of RAID, with quite a lot of problems. While it provided the most usable space from the array with minimal data protection, data loss was a problem if more than one disk got corrupted in an 8-disk array.
-
I'm booting a BareMetal machine from a USB drive - it has two SATA disks present.. I was under the impression, from previous builds of your loader, that the SataPortMap command was required to set the number of Sata disks present in your machine.. This SataPortMap command was in the original 6.0.x loaders - and setting it correctly fixed this very same issue in 6.0.1 and 6.0.2.. (as per http://xpenology.com/forum/viewtopic.php?f=2&t=20216&start=20#p72953.) Whatever the case, moving it to the common_args line fixed the issue in 6.1 on my BareMetal machine with your Alpha loader!.. Thanks! #H Actually, SataPortMap defines both the available ports AND the controllers. So, say, your motherboard has 6 ports, 2 on the CPU (because it supports it), and 4 on an external controller. You add a 4-port PCIe card to have 10 ports in total. Then your SataPortMap variable looks like this: SataPortMap=244 Now, if we reverse this, and your CPU built-in controller powers 4 of the ports, and the other 2 are on the external controller, it will look like this: SataPortMap=424 What you need to do is find out what kind of controller(s) are on your motherboard. Usually the manufacturer lists these info, but you can use a live Ubuntu image with lsscsi --hosts too.
-
Have you checked the USB VID/PID and made sure it's correct? In my case (a few pages back) that was the problem.
-
No it is not possible. A good majority of the Synology software stack over their kernel is proprietary, and not covered by GPL.
-
Okay I have the weirdest thing now going on... I built a new NAS. Pretty standard config: - MSI B250I PRO for motherboard (not the gaming version!) - Intel Pentium G4560 for CPU - Corsair Value 8GB DDR4 2133MHz - Chieftec PSU, 400W - Bitfenix Prodigy case, handles and legs removed So any way I popped in my hard drives from my old NAS (a VERY old HP EliteBook 8530W), 2x 1TB HGST 2.5" drives, running 6.0 Update 9, and a 6.1 bootloader with the previous serial number, MAC, etc. added. It did recognize as migratable, but I decided to wipe the disks and go at it again clean. Except now NOTHING shows up in Syno Assistant. It's empty. Even the router won't show the device. I tried re-flashing the USB disk, to no avail. What could've happened? BIOS settings were not touched, network seems to be up, but not working...
-
So drives are not showing up... Can you check in terminal if the SATA controller onboard has a loaded driver, and is recognized? If not, you possibly need to compile your own controller module - the currently supported controllers are limited to a handful of commercial ones, most that you find in off-the-shelf motherboards, HBAs, et cetera. It is possible that QNAP decided to use a more obscure (or enterprise level?) controller.
-
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? No need for "an entirely new loader", just wait for a loader update. Either jun or someone with the expertise will update it. It has all happened before, and will happen again. There are always people who want it done, and can get it done, and that two combined usually results in someone actually getting it done. Just be patient.
-
Any chance of having some extra drivers added? I'd need the Intel WiFi Link 5100/5300 drivers, even as a separate module would be nice! I believe the two use the same module, and possibly are even covered by the regular iwlwifi module if I'm not mistaken.
-
Tutorial: Install/Migrate DSM 5.2 to 6.0.2 (Jun's loader)
fonix232 replied to Polanskiman's topic in Tutorials and Guides
Are there any news about update 9? It isn't really specified what issues it is causing, and I can't see much about related topics either. -
They work great if you installed them on 5.x and then migrated to 6.0... The issue is with the installer. The community packages used a very specific way of creating users with specific rights (often reaching for sudo to create specific folders during install) within the installation process. That part fails, thus the packages can't start.
-
Dockerfiles aren't the problem. I can learn a new syntax and language in no time, and Dockerfiles are very straightforward Yup, this is the main issue. I always specify the ports so that it maps on my DSM to the same (usual) port. E.g. in Plex, I map 32400 docker-internal to 32400 DSM. Same for the others. I used those images, and worked somewhat okay. Though with Transmission, I usually replace the web UI, which AFAIK is not possible with the Docker version. I also like to refer to my server, no matter what container, as "localhost". But the containers get their own little network, thus Sonarr can't refer to Transmission as "localhost:9091".