spellman

Members
  • Content Count

    11
  • Joined

  • Last visited

Everything posted by spellman

  1. spellman

    DSM 6.1.x Loader

    Drivers for USB 1.1 aren't currently included (which I believe most ups's use). Jun has stated that he is working on adding them for the next release.
  2. spellman

    DSM 6.1.x Loader

    Jun, I must preface this that I know very little about linux systems at this point, and I know little about the kernal, but can you tell us if at this point stuff is or isn't in place that this loader can recognize usb 1.1 devices? Not that I'm trying to hook some ancient thumb drive up to it, but it seems like that is what a fair amount of the ups systems are using to communicate. My bare metal system seems to be working very well and is destined to be an off site back up at my parents house, but we live in a rural area and power outages can be quite common in in-climate weather. Both my c
  3. spellman

    DSM 6.1.x Loader

    Did some more digging on what could be going on. I'm thinking my ups only has a usb 1.1 port. I've read where previous xpenology builds didn't have the driver modules to talk to 1.1 devices, but that post was several years old and may not apply here. Does this DSM 6.0 have any such modules included(UHCI or OHCI)? *Edit: Also just tried on an old APC UPS, and no go with that either.
  4. spellman

    DSM 6.1.x Loader

    So I did some more testing for my cyberpower ups. I drug it over to my 1513+ and it did not recognize it being connected to the usb either. Tried switching the usb cable and it worked (the first one did work when plugged into a computer however). So I thought wow, I'm such a boob, that was easy. Drug it back to my xpenology test system and plugged everything back in and...nothing. Are there some drivers or something that could be missing? Anything that someone could suggest I check? USB flash drives work fine when plugging them in, so I know the usb ports are working. Disclosure, I'
  5. spellman

    DSM 6.1.x Loader

    Is anyone else having issues with their ups? I just got a cyperpower or500 that I'm trying to get working, but doesn't seem to be noticing that it is plugged in. I only have options in the ups management page for network ups's. Is there something else that needs to be installed? This ups should be compatible, but haven't figured out what is going on yet. Any help would be awesome! This is on bare metal btw, usb ports are working correctly.
  6. spellman

    DSM 6.1.x Loader

    As I understand it btrfs has good data integrity checks which seems like a major advantage in a data storage and backup environment where bitrot is a potential issue. ext4 doesn't offer that layer of checking and is therefore less reliable with respect to data integrity. I haven't used anything with btrfs so I don't know how it's implemented in a real world environment? I assume the core features of btrfs are usable so there are snapshot, deduplication and cloning options to name a few benefits. The big issue seems to be the limitation of raid system support and in our case shr and the advanta
  7. spellman

    DSM 6.1.x Loader

    Another update to my shr. For some reason I have been under the impression that a ds1513+ can do btrfs, but alas it can't. So that means I don't have any way of building a shr btrfs volume. I don't see why it wouldn't work to build a volume on a machine that can and then migrate it into the 3615xs dsm 6.0. For now I'm calling it quits on that and moving forward on building my actual shr ext4 volume that I will use as a destination hyper backup machine. Anyone have a few quick words on if ext4 or btrfs matters for this purpose? There is a lot of conflicting reports on the net, and at the
  8. spellman

    DSM 6.1.x Loader

    Just an update on my migrated shr tests: expanding to an additional drive works! I'm going to assume that swapping an existing drive to a larger one should be fine as well. If shr is something you want, I would create your volumes using 5.2, then migrate them to this 6.0. Once you are in 6.0 you can't create new shr volumes only standard raid, so get everything how you want it first. This method does limit you to ext4. Next thing I'm going to try is to use my ds1513+ to create a shr btrfs volume and see if I can migrate that into this build and expand it all the way through. Wish me luck
  9. spellman

    DSM 6.1.x Loader

    I just tried making a shr-1 volume in the xpenology 5.2, then swapped usb and put my 6.0 stick in. Had to reinstall to the box, but it worked! It kept my shr-1 volume and seems to be working. Right now I am testing expanding the volume by adding another drive (gonna take a while). Then I might try replacing a drive with a larger one to make sure that works. One note, this will only get you ext4. I may try and build a small btrfs volume using my 1513+ and try moving that over.
  10. spellman

    DSM 6.1.x Loader

    Does this mean this version should have SHR capabilities? When building a new volume it told me I needed to setup a raid array, and I did not have shr as an option. Has anyone gotten this to work? I used the pat file from synology, was I wrong in doing that? Is there a different one I should be using? If I were to build my shr volume in dsm 5, then redo the system as dsm 6, will I be able to keep shr capabilities? I can obviously test some of this myself, but when it takes days to build these volumes, I kind of would like to have an idea if it will work or not if it is already known by ot
  11. spellman

    DSM 6.1.x Loader

    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.