Umfriend
-
Posts
1001 -
Joined
-
Last visited
-
Days Won
54
Posts posted by Umfriend
-
-
I have never tried to use File Placement Rules but as I understand it, if you tell DP to place \movies on that 6TB HDD then it will and also spill over to other drives when the 6TB HDD is full. DP will not, I think, through a no space error. Not sure how to ensure that non other data arrives on that drive, that might need a lot of FPRs, but may be easy.
Having said that, I would not add a drive I am suspicious about if, unlike me, you do not use duplication. Do you have Scanner? Maybe run the Seagate tool again.
-
On migration, you already answered yourself correctly in another thread. On the F12 thing, I wonder whether it isn't BIOS related. Others have had this issue but I've not found it attributed to a corrupt OS install. You could also try to repair the W7 Install if you really think it is broken.
-
DP certainly has no issues with long (> 255 char) filenames. Not sure what Unicode is actually but I have never seen that mentioned as an issue for DP.
Note that although Stablebit support does visit this forum, a better way to get support is to open a ticket (https://stablebit.com/Contact).
-
8 hours ago, Spider99 said:
if DP - does not like a file it puts it in the "other" category (box) as its not considered part of the pool
I think this is confusing. Yes, when you remeasure, DP shows all data as Other at first until it is clear what is Pooled data (on within that, what is duplicated and unduplicated). By default however, Other relates to data on the drives comprising the Pool that resides outside of the hidden PoolPart.* folders. This is data that does occupy space on the Pooled drives but is not actually in the Pool itself. I am not convinced OP's issue has anything to do with Other.
@OP: Have you tried to read the manual? It points to some logfiles that you can try to have a look at. It is unfortunate that the message you get is rather generic.
Met vriendelijke groet
-
I would first run a CHKDSK and, if you have Scanner, let it scan the drive as well. I would also have a quick look at EventViewer for any ATAPI/DISK/IDE errors. Finally, I would consider trying to remove the named file manually. Oh, and a reboot.
-
I don't know Plex but normally any application that accesses files through the Pool is neither redundancy nor phyiscal location aware. It is not Plex that needs to know what drive has the data, DrivePool does that for you.
I think that if you have duplication then, yeah, it may read from multiple drives. Mind you, I have never really experienced a performance gain because of this but some say they have.
I guess that when a drive gets removed/offloaded that that may impact performance somewhat but AFAIK, it is a lower priority task and should hardly interfere with regular I/O, especially if you have the option to prioritise network I/O turned on. So I am not sure what would have caused the non-performance.
-
Not that I am aware of. Can you explain a bit more?
What is the setup - 1 PC local only or are we talking a server and shares?
Get any error message?
Can you give an example of a file that you can access one way (what is the full path and filename) but not the other (which full path and filename are you trying)?
Any messages on the DP dashboard/GUI? What does the Pool look like (screenshot)?
-
Well, you currently have a Pool, say P:\. Just go into the Poolpart.* folder on the F:\ drive and copy the contents to P:\
-
I am not entirely sure but I would consider:
1. Remove F:\ and select the force or somesuch option
2. While you're at it, remove the SSD
3. Locate the relevant data on F:\ (in the PoolPart.* folder) and copy (my preference) or move that into the Pool. The data should spread over Disk 1, D, E and H
4. Remove Pool L, any drives in there. If not possible, see of Pool L comes up after reboot.
5. Format F:\
6. Add F:\ to the Pool
7. Pool L should be gone but if it is still there then you should be able to clean it up
8. DP will reallocate files to F:\ once it re-balancesThat's what I would try and if step 3 succeeds then it should be rather risk free.
-
And does the new 8TB HDD get used after balancing?
-
My guess is that that found.000 file is very large? In any case, other than CHKDSK as a first step, I am not sure what to do.
-
Power drain?
Switching SATA cables (assuming the machine is powered off, otherwise less sure) should not affect DP / the Pool. I fear we're not really in DP-area but data recovery area and I am not that well versed in that.
-
OK, so I can't be sure but I think these drives have an issue. So I am not sure what to do but my guess is running a CHKDSK on these drives is a good first step.
-
No worries, we're all friendly here and just trying to help.
So with default settings the new 8TB HDD would indeed be used and data would be offloaded of some other HDDs. On the SSD Cache / SSD Optimizer, I *think* you are right but I never tried it myself so I am not entirely sure. But there is documentation on the website and you can search the forums, it is a treasure for info.
-
Well, duplication can be turned off easily and DP will remove excess duplicates. Not sure how you got duplication on just two drives. Some screenshots might help.
The balancing that has occurred will be harder to revert. Why don't you want balancing?
The only reason to uninstall I can see is if you don;t want to use the software. DP itself is able to reorganise as you want.
-
I don't understand. At default settings, DP would already re-allocate files so that you would have an optimal distribution. Optimal in that case means that each drive has (approximately) the same amount of free space. If you have SSDs as cache and Scanner then you want to have Scanner at top, then SSD Optimizer.
You can use the Disk Space Equalizer, I think to get all drives filled to [x]% but see no reason to do that. IMHO, with DP, default settings work very well without complicating matters.
I think I understand you "seeded" the drives. That is perfectly fine. DP will rearrange files afterwards.
-
Are you showing hidden files and folders as well? I would expect two PoolPart.* folders on these drive...
-
Is thjat 192 read or write. I don't know. SMR drives do well on read and sequential writes. Random writes though above a certain limit though, ouch.
If 20MB/s is a cap you experience on all drives writing through DP then there is a different issue. Time for some research, e.g. waht do you get on writing to those drives directly? You need to measure this with large, non-single file transfers I think.
-
So on the two drives that have close to 100% other, what you may want to do is called "seeding":
1. Stop DP service
2. On each of these drives, move the data in the current Poolpart.* folder to the new Poolpart.* folder
3. Start DP (or reboot)
4. Let DP remeasure / rebalance.With the 12TB, if you have a precise product number you could see if, perhaps, it is a SMR drive (although AFAIK, there are no 12TB SMR HDDs by WD
-
Can you see if Scanner is scanning that drive at that time?
-
In RAID might work. Just adding a few drives as SSD Cache may run into the same problem I fear. Also, one SSD, even if it is SATA, will outperform 4 HDDs I think. I am assuming you don't have actual SAS-drives. Depending on the actual chipset, two RAIDed SSDs might do the job fully.
-
Assuming there is no duplication, wouldn't a single 2TB SSD suffice as a cache? Way simpler for a somewhat specific use case IMHO.
-
Actually, if you have duplication then this procedure is, IMHO, incomplete. When you move files out of the poolpart.* folder, DP may remeasure and suddenly find duplicates are missing and re-duplicate.
If you have duplication, you can just power off the machine, physically remove the drive, reboot and then remove the missing/faulty drive from the Pool through the GUI. Remeasure/re-duplicate and it is done.
If you do not have duplication, then I would attach the new drive, stop the drivepool service (so DP will not interfere), copy the data from the faulty HDD poolpart.* folder to the new drive (to ensure you do not perform any unnecessary writes on the faulty drive), power off, physically remove the drive, reboot, start drivepool service if necessary, remove faulty drive from the Pool through the GUI, add the new drive to the Pool, stop the service, move contents on the new Drive to the poolpart.* folder on that drive, restart drivepool service, remeasure and it is done. I think.
-
I read this is as asking how to identify the actual physical drives in the case. I physically label my drives and stack them in the server according to their labels. Without something like that, I have no clue how you would be able to identify the physical drives...
File Placement, how to add new HDD for only backup files
in General
Posted
I think a 2nd Pool for non-critical data using old hardware is an excellent idea.