Apologies if asked/answered somewhere else. I looked around but couldn't seem to find this scenario being asked...
I have a ton of old hardware collected from various things that I like to just tinker around with. As such, I've got an old Thinkcentre M83 and a stack of random HDDs ranging from 20GB to 240GB in 2.5" SATA. I want to do a fun little NAS build out of it, JBOD the drives, and link it into the home network to see how well it would perform hosting as a media server compared to my existing Synology DS220+, just for the fun of it. Not concerned regarding efficiency, long term viability, volatility of old drives, etc. This is just screwing around, so criticisms aside, can anyone answer the following?
- I'd like to use Xpenology for the build for two reasons, first is that I like DSM, the second being that I'm curious if the two could co-exist. I would (obviously) not put my legitimate Synology creds into the Xpen build as I don't want my account blocked or my DS220+ bricked. I have no intent to open the build to the web. When fired up on the network, would DSM on Synology give automatic recognition that another DSM OS had joined and go into conflict? If so, would using a different version be a safeguard?
- If no confliction, I'd just map the JBOD network drive on a few machines and just dump old, non-important, non-mission critical stuff on it I suppose and also see how it would do with some random ripped media. It would be only on when used, off otherwise to increase longevity.
- The curious part of me wonders, if the Xpen is build out and then introduced to the network and they can co-exist, can it be safely taken a step further in that I could manually add the Xpen build to the Synology CMS as the second Synology device it thinks it is?
I mean, I bought the DS220+ recently, legitimately, brand new, so this isn't an effort to circumvent paying for a product/service completely. Rather, I'd just like to integrate into the network hardware that is not supported or recommended to be used in this fashion. We're talking about drives pulled from 15+ year old laptops, one from an Xbox I bought in the early 2000s. They're likely to fail at any time and I'm not going to spend the sort of money for a 4 or 6 bay enclosure for drives on their last legs. This is going to be called FrankenNAS. I'm more curious to see how long it will live in reanimation lol. Integrating into the existing DSM would just be the cherry on top. If it won't work, I'll just FreeNAS the thing and network the drive as I don't see that causing confliction between the two, but I don't want to be missing something there and be horribly wrong...
Question
CatBox
Hello all,
Apologies if asked/answered somewhere else. I looked around but couldn't seem to find this scenario being asked...
I have a ton of old hardware collected from various things that I like to just tinker around with. As such, I've got an old Thinkcentre M83 and a stack of random HDDs ranging from 20GB to 240GB in 2.5" SATA. I want to do a fun little NAS build out of it, JBOD the drives, and link it into the home network to see how well it would perform hosting as a media server compared to my existing Synology DS220+, just for the fun of it. Not concerned regarding efficiency, long term viability, volatility of old drives, etc. This is just screwing around, so criticisms aside, can anyone answer the following?
- I'd like to use Xpenology for the build for two reasons, first is that I like DSM, the second being that I'm curious if the two could co-exist. I would (obviously) not put my legitimate Synology creds into the Xpen build as I don't want my account blocked or my DS220+ bricked. I have no intent to open the build to the web. When fired up on the network, would DSM on Synology give automatic recognition that another DSM OS had joined and go into conflict? If so, would using a different version be a safeguard?
- If no confliction, I'd just map the JBOD network drive on a few machines and just dump old, non-important, non-mission critical stuff on it I suppose and also see how it would do with some random ripped media. It would be only on when used, off otherwise to increase longevity.
- The curious part of me wonders, if the Xpen is build out and then introduced to the network and they can co-exist, can it be safely taken a step further in that I could manually add the Xpen build to the Synology CMS as the second Synology device it thinks it is?
I mean, I bought the DS220+ recently, legitimately, brand new, so this isn't an effort to circumvent paying for a product/service completely. Rather, I'd just like to integrate into the network hardware that is not supported or recommended to be used in this fashion. We're talking about drives pulled from 15+ year old laptops, one from an Xbox I bought in the early 2000s. They're likely to fail at any time and I'm not going to spend the sort of money for a 4 or 6 bay enclosure for drives on their last legs. This is going to be called FrankenNAS. I'm more curious to see how long it will live in reanimation lol. Integrating into the existing DSM would just be the cherry on top. If it won't work, I'll just FreeNAS the thing and network the drive as I don't see that causing confliction between the two, but I don't want to be missing something there and be horribly wrong...
Link to comment
Share on other sites
1 answer to this question
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.