-
Posts
11572 -
Joined
-
Last visited
-
Days Won
366
Posts posted by Christopher (Drashna)
-
-
Shane, Good point.
However, I have a rackmount server case (Norco 4220), that I will "eventually" fill.
I just need to move my server into it's own room/area. Away from the cats.
-
Glad to hear that you are loving our products!
And yes, FlexRAID is ... incredibly complicated for doing something that is supposedly simple. But glad you are loving our product.
As for Scanner, there is a Pinned thread that you may want to check out that explains a lot of those settings. Alex (the developer) has a nice long post explaining all the settings. Worth checking out:
http://community.covecube.com/index.php?/topic/48-questions-regarding-hard-drive-spindownstandby/
(and it should answer all your questions, so I'm not going to attempt to here.
Basically, no, DrivePool doesn't add much to the RAID card. Sort of. You can definitely add the RAID array to the pool without any issue. But personally, I'd rather use DrivePool and Scanner over the RAID array. Namely because you should be able to get SMART data if you pass the disks through (as individual drives, though this may require enabling "UnsafeDirectIo").
The reason I use this instead (I have a HighPoint RocketRAID 2720SGL card), is that you get more disk space out of this, and having both installed will add a "Scanner" balancer for DrivePool that will evacuate data from a drive that Scanner detects as failing.
As for DrivePool's disk in Disk Management, that is because we use a "virtual driver" for the drive.
And as for the IO, that's because the DrivePool drive doesn't actually exist, and all IO operations are passed onto the disks directly. This means that you should get better performance.
-
Tallmomof2,
First, let me say I'm sorry that Storage Spaces ate your data. That's never a pleasant experience.
DrivePool operates very similiarly to how WHSv1's DrivePool did. In fact, that's the inspiration for our product. Though we've made a number of improvements.
First, all the files are stored on normal NTFS volumes. So if you decide that you don't want to use DrivePool anymore, you can just uninstall it, and then recover all your data from the hidden "PoolPart.xxxx" folders in the root of each drive.
Also, if you reinstall the OS, or decide to migrate to new hardware, you can just move the disks over. Once you reinstall DrivePool, it will immediately recognize the "old" pool, and "rebuild" it.
I'm not sure if you have had to deal with a system disk failure in WHSv1, but you basically had to completely rebuild Drive Extender's storage pool by copying everything back into the pool. A very time consuming process. Like I indicated, for DrivePool, it would take seconds... just reinstall DrivePool and reattach the drives!
If you decide to go with a dedicated system for WHS2011, then I'd recommend checking out StableBit Scanner as well. Namely, because it gets SMART data from the drives, as well as scans them for issues periodically. And if you have both products installed, Scanner can evacuate a DrivePool drive if it detects errors with it, to help prevent data loss.
-
I live in the San Deigo area, so yeah, lots of dust. That, and lots of animals.
I'd be more inclined to believe it is the box it's in or maybe the controller card. That's where I'd put my money.
But swapping out the cable should be trivial, and very easy/quick to test.
-
Okay, I wasn't sure.
On the DrivePool UI, when it's measuring, it has a small "pac man" type icon in the bottom left corner of the Pie Chart area to indicate that it's still indexing.
And from the sounds of it, it wasn't still indexing. If that is the case, it is possible that it got interrupted. Such as if it got rebooted, or needed to do a balancing/duplication pass.
-
Dust and stuff... I live in an area that everything gets dusty, so I have to clean out my server and other computers every six months.
As for burning out cables... There isn't a cable type that I haven't burned out at least once. that includes SATA cables, cat5(e), and even Coax.
-
Scanner is definitely compatible. The underlying API that it uses has not changed. You can use either the "Windows 7" or the "Windows Home Server 2011" version. The difference is that the WHS2011 version will deploy over the network and will have a dashboard tab.
As for DrivePool, that should be compatible. I know it's been extensively tested with the Preview version, and has no issues with it. And it should work fine with the RTM version.
-
It's possible that it's blocking that. You could check by running the stand alone app for it as well:
-
I can't say that I'm completely surprised by that.
The next time that happens, would you mind getting a memory dump of the system?
http://wiki.covecube.com/StableBit_DrivePool_System_Freeze
This will cause BSOD (it's intentional), but just make sure that you run the "bugcheck off" entry after doing this.
-
ACtually, the other is okay. It's supposed to be there.
There is a nice post about that, as well as a blog post:
But basically, it's any files outside of the pool (such as data on it already when you added it, or shadow copies, or the recycle bin on the hard drive). As well as "misc used space", as in that 1kb file still takes up the 4k sector. And the discrepancy gets reported by NTFS, when is what we read, and calculate the usage.
-
Kihimcarr,
Okay, then something weird is definitely happening here.
I suspect that it may be the "Virtual disk server" not updating properly, but I'm not sure.
Would you mind grabbing the Error Reports and opening a ticket?
http://wiki.covecube.com/StableBit_DrivePool_2.x_Error_Reports
-
Blake,
DrivePool does and can move files around, but that should be completely invisible to you.
I also run utorrent on my server, and I have not had an issue download or seeding from the pool.
However, if you wouldn't mind enabling the "trace logging", so we can help track down this issue:
http://wiki.covecube.com/StableBit_DrivePool_Log_Collection
http://wiki.covecube.com/StableBit_DrivePool_2.x_Log_Collection
-
Glad to hear. If you have any other issues, don't hesitate to ask us.
-
No, neither version supports VSS at the moment.
Microsoft has pretty much *no* documentation about implementing the feature, so getting it to work relies solely on trial and error to get it working.
-
Yeah, that will definitely wear the disk out rather fast. But that 97% is after ~220 days of running it as the system drive.
On my desktop, I have the same SSD (Newegg screwed up), running for ~160 days as well, with the wear at 99%.
Both of these are system disks. But I try to not install anything to the SSDs.
Also, if you're using duplication, you'll want two feeder disks.
-
It's very likely. Unfortunately, it does happen.
Also, Scanner's surface scan will cause the reallocated sectors to show up more often (well "appear" more often, but it just triggers the internal error correction mechanisms, and report it via SMART).
I've also... done the not as great thing, and shelled a bunch of Seagate Backup Plus drives for my 3TBs.
-
I have already replied to your ticket, but :
It sounds like the WIndows Search database got corrupted.
Just try rebuilding that, and it should fix the issues with DrivePool:
http://wiki.covecube.com/StableBit_DrivePool_Q7200705B
Regards
-
Just want to make sure, all the clients are using build 400 as well, right?
And you've double checked that the peer list is still properly configured.
-
Things you lose by upgrading:
- The "Stable" label, for now. It's an RC, but ... still. There are bugs possible. But that's only for now.
- Major dashboard integration.
There is a tab, but you lose the tab under storage - per folder/type information,
- Pie chart of folder distribution
Things you gain
- Remote control, without using the Dashboard
- updated drive for drivePool (most changes are backported, but there is more active development on 2.x)
- larger list of supported OS's
- Per folder duplication
- Greater than 2x duplication
This list isn't comprehensive. It's basically off of the top of my head.
However, balancing shouldn't be affected, nor duplication. At least not significantly. Nor is disk usage (however, it is displayed a bit different)
-
I believe this is information from the Drive's SMART data, so definitely drive dependant. But i'm not 100% certain about that.
-
Well, for Scanner, you can change the disk activity sensitivity.
And do you have the "Read Striping" and "Network IO Boost" options enabled for DrivePool (should be under Pool Options->Performance)
If you already have those enabled, if you wouldn't mind, could you enable "Tracing Logs" on the "server" and try duplicating the "issue" and then submit the logs?
http://wiki.covecube.com/StableBit_DrivePool_2.x_Log_Collection
-
Try resetting the settings for Scanner and DrivePool (you'll have to reactivate):
http://wiki.covecube.com/StableBit_DrivePool_Q2299585B
http://wiki.covecube.com/StableBit_Scanner_Q4200749
If the problem persists, then please let us know.
-
I have seven of the ST3000DM001 drives, and none have any reallocated sectors.
All of them are the -9YN166 model, but still. And they are the CC9E or CC9F firmware. This could make a difference.
It is possible that the drives are from the same batch, and that batch has a defect (this unfortunately does happen, with *all* manufacturers).
If you are very concerned, check with Seagate support and you should be able to RMA the drives. May be a good idea if the reallocated sector count keeps climbing (as this would indicate a serious defect)
-
It sounds like it is reindexing/remeasuring the pool.
This is normal.
If this takes an excessive amount of time... then it may be stuck, and resetting the DrivePool settings may correct the issue (but will force it to reindex it again).
Slow Write Speeds to the Drivepool
in General
Posted
Yeah, messing with stuff late at night is a recipe for disaster.
And yeah, cable management can be a PITA when you need to move stuff around. That's why I tend to just jury-rig things into place. Because I like to tinker. A lot.
As for my server, I think I already have. I'm not sure. But the big thing is the HighPoint RocketRAID 2720SGL card. 2x SAS cables, that break out to 8 HDDs total.