flyride
-
Posts
2,438 -
Joined
-
Last visited
-
Days Won
127
Posts posted by flyride
-
-
For 6.x yes it's too old.
- 1
-
You need Nehalem processor or later to use DS3615 or DS3617 platform images. Yorkfield is too old.
- 1
-
It's an unusual board yes, but it should be able to make work. I'm not convinced about your USB issues. I think you may have a problem with Intel drivers that needs to be addressed by IG-88's extra.lzma. If you want to try and troubleshoot without, get an Intel CT PCIe LAN card and see if that gets you working initially.
-
Need more information. What motherboard, what DSM version?
-
For this to work in linux, you need a hardware driver and application support.
Synology doesn't have any native support for NVIDIA, so if you wanted to use Synology's packages, you will need Intel QuickSync.
If you want to use Plex, they have some limited support for NVIDIA, but you would still need a functional hardware driver. Jellyfin and Emby have better NVIDIA support. Regardless, I am not aware of anyone implementing the NVIDIA drivers on DSM yet.
-
Do you have USB 2.0 ports (internal or external)? Try those. If there is BIOS options to put USB in legacy mode, try that as well.
-
Try onboard NIC with no driver extension initially with the newest version 6.2.3.
-
I was able to find a picture of a 88SE9215 chip on a DS918+ motherboard. I now realize you may have referred to the deliberately incomplete "reference hardware" block at the top of the post, which isn't really the point (did you even open the spreadsheet?) Anyway, Synology does not publish their hardware specs and any factual information comes from postings on the Internet. I'm not sure where the reference to the 9125 chip came from at the time, but I will update the reference hardware block accordingly. Thank you for contributing to our collective knowledge on the subject.
-
6 hours ago, Jdw0 said:
the real 918+ is use 88SE9215 SATA controller , Not the 88SE9125. I trust your post , and bought a 88SE9125 card. No Disk found! then I check out the real 918+ Motherboard findout 88SE9215 is the native chip up there.
Of course, this guide does not say "here is a list of the actual hardware devices that are in Synology" - it reports the PCI ID's of all the hardware supported by the drivers that are part of the DSM image. It is common practice for manufacturers to support several (and sometimes all) versions of their hardware in their drivers.
If you want guarantees that hardware will work, you had better go to the User Reported Hardware Compatibility thread and make your decisions there.
Now I will make a disclaimer, I have included all Jun's drivers in the list, and we know that those drivers are broken in 6.2.1 and 6.2.2, but again work in 6.2.3. It's pretty easy to see which drivers are Jun's (look in the update folder). I'll post an updated document at some point in the future that makes this more clear.
-
DS3615/3617 is a better choice for your intended system.
-
You can have hardware transcoding (918), RAIDF1 (3615/3617) or support for 16 threads (3617). You can't have it all at once.
FMI: https://xpenology.com/forum/topic/13333-tutorialreference-6x-loaders-and-platforms/
Has anyone ever demonstrated a successful ESXi iGPU passthrough? I agree that it should be possible, but I have not seen any posts confirming it.
-
Use FixSynoboot.sh
-
Try clean install with DSM 3615xs (not 3617xs) version 6.2.3 and 1.03b. Make sure you have selected BIOS boot, not EFI.
-
14 minutes ago, PhoenixNL72 said:
1.04b only works with the 918+ DSM pat files and those require you to have at least an intel Haswell or later processor (I3/i5/i7 4xxx or later) due to the iGPU (915 I think it needs?) requirement.
FWIW it's not an iGPU dependency, although 916/918 are the only supported DSM images with iGPU support. The Haswell requirement appears to come from the kernel; it appears to demand CPU instructions that are only available on that processor architecture or later.
-
Same here, I keep my archive copy on the latest version but my main system is 6.1. I am starting the complex system testing to migrate it to 6.2.3, finally...
-
I would probably do something like that. Have a backup.
-
3 hours ago, Rooster said:
Alternatively, you can also do an qm importdisk of the synoboot.img and assign it to SATA0. That'd been more straightforward and worked for me as well, but personally, I'd prefer not seeing the loader visible as a mountable drive inside the DSM OS so I took the former route of mounting it as a usb device like what you'd normally do in a typical bare metal scenario.
Fixsynoboot.sh would probably had fixed this as well.
-
Are your drives shucked from retail external enclosures? Maybe you have the 3.3v power pin problem: https://www.reddit.com/r/DataHoarder/comments/7ylalg/psa_some_hgst_drives_wont_spin_up_with_some/
- 2
-
1 hour ago, chimera15 said:
I have an adaptec 6405e which definitely doesnt. It wont recognize anything over 2tb. It at least will show the larger drive though and says it's not compatible. This card doesnt even register the drives as being plugged in, which i agree might point to something else going on.
Adaptec disagrees with you: https://ask.adaptec.com/app/answers/detail/a_id/17414
-
With all these restrictions and reservations, I don't see why you are interested in a server-based solution at all.
If DSM has features that remain compelling for you, I'd suggest you configure it as intended (RAID, btrfs, shared storage) and look at snapshot/replication to another DSM instance for crash and data loss protection.
If you are concerned about the stability of XPenology running DSM, you should consider purchasing a real Synology solution.
iSCSI does work with DSM, but really needs btrfs and RAID for best performance. That said, unless you have a strong desire to run diskless workstations, it's not better or faster than using a CIFS or Apple share. If your desire is to back up a local drive to the NAS, VEEAM Free offers a very flexible solution.
-
What controller won't work with 8TB drives? Something else is going on.
-
No real reason to back up the USB. You can boot your system with a new clean copy of the loader at any time and it will be updated. Save the grub config on your PC somewhere.
If you must do it, you can use the WinImage tool to copy your running loader config back to an img file.
-
https://xpenology.com/forum/topic/28321-driver-extension-jun-104b-for-dsm623-for-918/
Your USB drive needs to stay in place. It is the bootable device.
- 1
-
Actually the package that is cross compiled to do this was authored by VMWare, is called vmtools and it is available on most guest OS’s.
I can understand the confusion if you are not familiar with it (but somehow familiar with the function).
No sarcasm here either. All good!
- 1
Tutorial: Install/Migrate DSM 5.2 to 6.1.x (Jun's loader)
in Tutorials and Guides
Posted
So you are verifying Netburst works with 6.x?