Diverge
-
Posts
355 -
Joined
-
Last visited
Posts posted by Diverge
-
-
Can someone tell me if Jun's bootloaders support LSI SAS2308 controllers?
I'm trying to help my buddy get a system based on ASRock E3C224D4I-14S motherboard up and running.
-
On 10/31/2017 at 3:11 PM, denmalley said:
Docker is sooo easy though. I'm brand new to this project and I have sonarr and nzbget working flawlessly on a bare metal Dell T30 with 6.1.3
I was in the same boat, not thrilled that synocommunitywas broken for 6x and not crazy about using docker.
Check out the guides at drfrankenstein.co.uk
I have/had a bunch of apps running in dockers. I just don't like Synology's docker implementation. Most of the time things don't work from the GUI, and you need to start/create dockers from the command line. Some things I have to delete the docker and recreate it every time the system reboots because it doesn't start correctly.
-
I updated to DSM 6.1.3-15152 Update 6 without any issues so far.
I have 2 x VM's, with 2 x arrays. One DSM 5.2 and the other DSM 6.1.3-15152 Update 6. DSM 5.2 is my main system, and it does backups to the DSM 6.1 VM.... once all the synocommunity addons I use are compatible with DSM 6.1, I'll likely move to making DSM 6.1 my main VM, with the secondary VM as the backup VM.
-
Does anyone have a compatible package for DSM 6.1?
Synocommunity is ages behind, and it doesn't seem like they'll release anything anytime soon.
There was a guy who created packages for 6.1, but he decided he didn't have time to keep everything up to date, so he removed them all... this used to be the path: http://www.jadahl.com/synology6.1/packages/nzbget_bromolow-6.1_19.0-23.spk I haven't been able to find a mirror of it. Does anyone have a copy or something else that works?
I'm not interested in using docker
-
I would try mounting the array with linux first. Sometimes Synonolgy will mark the array as bad, when it's not really bad. How to undo that I'm not sure. But if your array is working (even if synology says it's bad), you should be able to mount it in linux and get to your data to back it up, then start over w/ synology.
I went through my own experience years ago, that I documented here: https://forum.cgsecurity.org/phpBB3/fou ... t2600.html
Good luck!
-
What dutchman said. VM's are awesome
I've never had an issue running a DSM VM in ESXI, and have been playing with DSM on 3rd party hardware before this site existed thanks to Vortex 
-
You're right. I read it wrong. Sorry
-
You should re-read that article, and re-try it. Because I've been doing the same thing for years, and it works fine.
-
You need to add rmmod=ata_piix to the grub/syslinux config on the kernel line.
That's why you're seeing the boot loader as a drive in DSM when using ESXI. I'm not sure why the people creating VDMK's aren't doing that step. This will also prevent DSM from writing over your bootloader disk when doing a fresh install, and formatting blank drives on initial installs.
-
Has anyone gotten a rackstation vm image with Jun's loader working with this?
I ask, as the 3615xs does not have the SHR/SHR2 config anymore.
Synology has pretty much phased out SHR on most of their high end models:
https://www.synology.com/en-us/knowledg ... d_RAID_SHR
Some models are allowed to use SHR, if it was created in an earlier version of DSM, which is likely how Xpenology uses it w/ DS3615 (it's there, but not enabled in UI - but the xpenology guys enabled it).
-
So it looks like the official DS3615xs no longer supports SHR1/2 at all. Does that mean that the dev team should be looking towards an alternative model that supports SHR? It looks like the models below this: RackStation RS2416+/RS2416RP+ support SHR only now, with the enterprise range (DS3615xs belongs here) only supporting traditional RAID modes. The enterprise range is also the only one with native SAS support using the LSI cards.
It never did, it was a feature they removed w/ the 2015 model. The other loader guys re-enabled it. I think it's there, just disabled behind the scenes. They'd have to chime in for more info.
-
Got this up and running on an older pc with the idea that I can move it to my parents house and have an off site backup of my ds1513+. One issue I ran into was the ds3615xs no longer supports shr in dsm 6.0 when making new volumes, and for me that has got me stuck in my tracks. I'm planning on using a pile of my old hdds to get my total space and they are of various sizes. As I understand this is a dynamic patcher correct? What is the likelihood that this would work on a system that still supports shr? I would use the corresponding pat and change sn and model number in grub.cfg of course. I was going to try this, but am currently still testing as it is for stability, and didn't feel like clearing the whole thing out in the middle of that and messing it up if it flat out won't work from the git go. Any thoughts or guidance would be super helpful. Thanks to all that have worked on this!
SHR was removed from ds3615 officially. It was re-enabled by those that created the loaders.
https://www.synology.com/en-us/products/DS3615xs#spec
Just an FYI
-
People shouldn't really be trying these hacked loaders with their real data until some time goes by and they are tested more thoroughly... unless you don't mind the possibility of losing your data.
-
1
-
-
Jun,
I looked at the code changes from your second ramdisk against your first release and got to say good changes and I approve! Your code vs XPEnology's is much cleaner and less changes to Synologies chroot.
So far your module seems to be flawless for virtual guys. Here's what I've tested so far:
- Test basic VM deployments with OVF and install monitoring logs. (your changes fix some of the delay)
- upgrade from 5.1-5055 to 5.2-5565 to 5.2.5644 to 5.2.5697 then to 6.0.2-8451
- separate XPEnology running 5.2-5644.8 to 6.0.2-8451
- ESXi RDM's work perfectly
- ESXi PCI Passthrough LSI 9211-8i and LSI 9265
I plan to test from KVM as well. I will provide the mpt3sas for later LSI cards.
We still need to look at the non-virtualized hardware that people are having issues with. Don't have cycles at the moment to test this right now, but do have a spare SuperMicro Twin server that I may test for this.
One last thing, did you see my pm on this site or the pm on Tapatalk? Can you send me the source code for the module?
When you're passing through the 9265, what mode is it in? Does it have an IT like mode like a 9211?
- Test basic VM deployments with OVF and install monitoring logs. (your changes fix some of the delay)
-
Only the data volume is an actual array (raid 5), the others are just mirrors of one another. You could just try mounting one of the system partitions by itself to see if you can see any files.
-
Well the only way that DSM will have smart data from hardrives, is if you passthrough a controller to your DSM VM (it won't work w/ RDM).
If you use virtual drives (on a datastore) for your array, then you won't be able to use your disks with systems outside esxi. Like if you wanted to move the disks to real synology system. Or if wanted to mount your array in Linux (outside of esxi), to recover a broken array, ect. I'm not sure about transfer speed differences.
-
Yeah, the unas case rocks
-
Try setting up another XPE VM, make an iSCSI drive the same size as your old one. Shut it down, or disable it, and swap the file you mention above.
I have no idea if that will work, but it might be worth a try if you haven't done something like it yet. I use iSCSI as well, but haven't tried moving the iSCSI drives from one VM to another... But I have accidentally deleted one that I had a lot of files on.. and then much later wondered where I had those file and realized I had deleted the iscsi drive they were on
-
Works here as well. I use openvpn, along with the android app on my phone, to connect to my lan
-
I have no experience with Bitlocker, so not of much help. But if you figure it out, let us know
Good luck! -
You're probably better off trying to mount the array in standard linux. I lost my array once a while back, and from a lot of reading how linux raid works, and help from someone on the TestDisk forums I was able to recreate my array w/o having any partition tables, backup my data and start fresh. It took me like 6 months until I got my data back - now I make backups
From my experience once Synology marks your array as failed, ect, it's very hard to get it to work in DSM again (unless you work for synology - they don't tell you what they do when they SSH into your box to recover arrays).Anyway, I outlined everything I did back then, and it can be found here... it may or may not be of any help: https://forum.cgsecurity.org/phpBB3/fou ... t2600.html . All I can say is take your time and do a lot of reading. Image the disks to another set if you have spares, and work with the imaged drives in case you make it worse. If you have backups, it's probably easier to format and start over... unless your just curious and looking for a huge challenge.
-
DSM assigns bay slots to the controller ports it detects. It's possible it's assigning the last 4 bays to other ports your not using. You'd need to poke around in ssh to try to see what is going on. fdisk -l and other utils might give you some clues.
-
They know what the license says, but they also know we can't do anything about it; only the copyright holder can. They should really declare war on Synology because Synology ihas been intentionally breaking the license for years, while making a huge profit.
The same goes for about any Chinese company that uses Android as well. None of them follow the rules...
-
I gotta agree with the last 2 guys. If you pass through your controller, and let DSM manage the disks, at least you can mount your array in linux and get to your data if DSM fails somehow... or at least you have a chance to rebuild your array outside of DSM if it fails, physically or w/ another VM by moving the controller to the new VM.
And you also get smart data in DSM
DSM 6.2 Loader
in Loaders
Posted
Thanks, I'll take another look. I've searched the forums, but IMO it's a huge mess w/ guides and various versions of bootloaders everywhere. I been using modded versions of dsm forever (before this site existed), through the various bootloader modders (vortex, gnoboot, ect), but haven't touched things in years - works == good. When searching you find too much old stuff that doesn't apply.
I told my buddy to just order another lsi 9201-8i from ebay for $25. Easier then pulling my hair out trying to find accurate info.