Joined
·
65 Posts
I thread-hijacked someone else's "Plugged in my new eSATA disk and it didn't work" thread which is rude, so I'm posting this separately.
I recently read the "2 year review" post here on DBSTalk, and it got me thinking about the eSATA "support" and why there aren't any migration tools available yet.
I have a Venus DS3DR Pro RAID1 external eSATA enclosure with two 1 TB WD Green drives sitting in it, just raring to go. I've had it for over a week now.
But meanwhile, my existing 320 GB internal is 85% full, and I don't see myself watching all that content any time soon so that I can drain it down to 0% and make the switchover.
Plus, some of that content is stuff I don't want to erase! (Federer-Nadal Wimbledon 2008 anyone, hello!)
Yes, yes, I know - I could hook it up now and then disconnect it if I wanted to go watch that old existing content, and then reset/power-cycle/reconnect the eSATA. To me, that's just silly. (Not to mention risky - I'd prefer to keep the total number of resets and power-cycles down to a minimum.)
I have 3 times the storage and it's "safe" in RAID1. I don't want to go back and forth, I want to move the stuff off the internal and onto the eSATA, period. But there's no migration capability in the HRs to do this with.
Putting a port on a consumer device and maintaining after 2 years that it's "just there" and is not fully supported is ludicrous. Support the hardware you ship, or pull the port off of successive generations of the hardware if you aren't going to support it. :nono2:
The only way I've seen (here on DBSTalk) to migrate the internal drive's recordings to the external eSATA is to have a desktop PC with room for 2 internal SATA disks, with a SATA data cable & power cable available to the HR's internal drive (either by stretching to reach the HR or taking out the drive entirely from the HR, which voids the warranty and is not advisable).
Well, that doesn't work too well for those of us with a Mac laptop, now does it?
As of now, the eSATA port is nothing more than a giant toggle power switch.
I know enough about Linux (I am a Systems Programmer and admin over 100 Linux boxes daily) to know that combining the internal drive with the eSATA into one mondo volume isn't really feasible (especially when you have Real-Time latency requirements for filesystem performance), but the fact that there are no migration tools at all at the 2 year mark is absurd.
You get your HR. You fill it up. You need more capacity. But you don't want to give up your existing recordings.
So you plug in a new, fresh eSATA drive. What should happen then? No on-screen feedback at all??? :eek2:
Why not something like this?
"New external drive detected. Initialize? [Yes] [No] [Ignore]" (in a pull-down menu)
"Initializing..."
"Initialization complete. Migrate recordings to external drive? [Yes] [No]"
"Migrating recordings. Please wait..."
"Migration complete. Restarting..."
(and it either resets again, or gets to the "Step one of two" screen and continues)
We all know that the internal drive is formatted into 3 partitions, and the 3rd one contains the "raw" recordings on a Linux XFS partition. (Right?)
How hard would it be for D* to initialize the external eSATA as a single partition (XFS volume) and provide a means to move all the recordings over to it, and use that as the partition (instead of the 3rd one on the internal) from that point onwards?
I recently read the "2 year review" post here on DBSTalk, and it got me thinking about the eSATA "support" and why there aren't any migration tools available yet.
I have a Venus DS3DR Pro RAID1 external eSATA enclosure with two 1 TB WD Green drives sitting in it, just raring to go. I've had it for over a week now.
But meanwhile, my existing 320 GB internal is 85% full, and I don't see myself watching all that content any time soon so that I can drain it down to 0% and make the switchover.
Plus, some of that content is stuff I don't want to erase! (Federer-Nadal Wimbledon 2008 anyone, hello!)
Yes, yes, I know - I could hook it up now and then disconnect it if I wanted to go watch that old existing content, and then reset/power-cycle/reconnect the eSATA. To me, that's just silly. (Not to mention risky - I'd prefer to keep the total number of resets and power-cycles down to a minimum.)
I have 3 times the storage and it's "safe" in RAID1. I don't want to go back and forth, I want to move the stuff off the internal and onto the eSATA, period. But there's no migration capability in the HRs to do this with.
Putting a port on a consumer device and maintaining after 2 years that it's "just there" and is not fully supported is ludicrous. Support the hardware you ship, or pull the port off of successive generations of the hardware if you aren't going to support it. :nono2:
The only way I've seen (here on DBSTalk) to migrate the internal drive's recordings to the external eSATA is to have a desktop PC with room for 2 internal SATA disks, with a SATA data cable & power cable available to the HR's internal drive (either by stretching to reach the HR or taking out the drive entirely from the HR, which voids the warranty and is not advisable).
Well, that doesn't work too well for those of us with a Mac laptop, now does it?
As of now, the eSATA port is nothing more than a giant toggle power switch.
I know enough about Linux (I am a Systems Programmer and admin over 100 Linux boxes daily) to know that combining the internal drive with the eSATA into one mondo volume isn't really feasible (especially when you have Real-Time latency requirements for filesystem performance), but the fact that there are no migration tools at all at the 2 year mark is absurd.
You get your HR. You fill it up. You need more capacity. But you don't want to give up your existing recordings.
So you plug in a new, fresh eSATA drive. What should happen then? No on-screen feedback at all??? :eek2:
Why not something like this?
"New external drive detected. Initialize? [Yes] [No] [Ignore]" (in a pull-down menu)
"Initializing..."
"Initialization complete. Migrate recordings to external drive? [Yes] [No]"
"Migrating recordings. Please wait..."
"Migration complete. Restarting..."
(and it either resets again, or gets to the "Step one of two" screen and continues)
We all know that the internal drive is formatted into 3 partitions, and the 3rd one contains the "raw" recordings on a Linux XFS partition. (Right?)
How hard would it be for D* to initialize the external eSATA as a single partition (XFS volume) and provide a means to move all the recordings over to it, and use that as the partition (instead of the 3rd one on the internal) from that point onwards?