stuza
-
Posts
21 -
Joined
-
Last visited
Posts posted by stuza
-
-
Hi Christopher,
thanks for your reply.
How do I clear the status temporarily because, i've not been presented any option to do so even after file recovery?
The 2 disks that have suddenly devloped lost sectors are an 18tb and 16tb so, not in any rush to replace them if I don't have to. That said, they have both only lost something like 5kb each (and the files were recovered anyway) so, as this isn't huge I'd like to just monitor them for a while first to see if more appear or it remains constant.
If I understand right then, I'd like for Covecube to consider the feature addition to provide the ability to mark these errors as "Acknowldged" and this gets recorded as a known error but one that Scanner will not keep alerting. Right now, every time the PC boots I get a new email and I have to keep checking these to see if it's the same error or new and it's a bit frustrating.
Thanks!
-
Hi Covecube & friends!
I've got a Windows 10 system with 70ish TB over 5 drives connected via USB as a media server. I'm running Scanner version 2.6.2.3920 on Windows 21H1.
I had a lost sectors reported. I attempted file recovery within Scanner and these recovered and saved to another drive. I've since re-run the "File Scan" scanner "Check" but, the gui still shows a red block but reports "No damage to the on disk data was detected" and the disk is is still labelled as Damaged.
First question - is 1 lost sector a sign of trouble or is this normal for a disk that's on 24/7? (temps of disk max out at 45c, usually around 90% of the time they are at 38/39c)
Second question - How do I clear the damaged status as it's annoyingly sending me emails which means I might actually just delete a new error email thinking it's one of the many repitions of the old error?
Thanks!
-
On 3/5/2021 at 10:52 AM, stuza said:
Thank you!
It's a real shame. The very first support issue I had way back yonder days was solved really quickly and helpfully, but the second one (first for this issue) has never been answered to this day and it was a few weeks ago. Hopefully your poke will help this.
Thanks again and have a cracker of a weekend!
Hi Shane,
I've had zero feedback from Covecube however, just today I retried and the license activated. No idea why but, problem is resolved. Thanks for trying to help, much appreciated!
Also, I just found out that DYNAMIC disks cannot be added to a pool, only BASIC disks - type can be checked in Device Manager/Disk Management. Thought i'd add this in case it helps others via Google. -
Thank you!
It's a real shame. The very first support issue I had way back yonder days was solved really quickly and helpfully, but the second one (first for this issue) has never been answered to this day and it was a few weeks ago. Hopefully your poke will help this.
Thanks again and have a cracker of a weekend!
-
Hi Shane,
thanks for your help!
I used the contact form.Both. With and without. Neither work.
-
I'm getting a little bit annoyed right now.
I built a new PC. I tried to use my old license on the new PC (old one is still here) and got "license not found" which is clearly wrong error message. I
emailedused the Contact Form to get support. Got no response. Bought another license because, ya know what, my time is more expensive than waiting for a response that may never happen.Had to rebuild the same PC (rampant random DLL sucking all CPU). That time it said it would migrate license to the same new computer.
Third rebuild - this time due to "System Interrupts" sucking all my CPU (honestly, last fracking time I build on AMD) and now again, I'm being told License not found!!!!
I won't buy another license. If this isn't resolved I'll use another solution.
-
18 minutes ago, gtaus said:
Interesting thread. I think I'll just leave my drives on. Seems the risk of a drive failure from stopping/starting exceeds the cost of electricity saved.
Just be careful to monitor the heat, specially if they are bunched together.
-
9 hours ago, HTWingNut said:
I wouldn't set the sleep to 1 minute. That will kill the drive. Best to set it idle for like 20 minutes because if there's any drive side maintenance being done, it will shut down after 1 minute, wake, shut down, wake, shut down.
Also, are you using stablebit scanner? Does scanner happen to be running at the moment? I would check task manager to see if drives are active.
I'd be concerned with cooling in your system. What case are you using? I was running eight 12TB in my case at idle about 35-37C with slight fan movement. At load never exceeded 42C.
Hi WingNut,
sorry for slow response, was working with Support to test a few things.
I totally agree that 1 minute is excessive but, it was really just to help me test quicker.
The testing completed I can now conclude that this is very unlikely an issue with DrivePool. I disabled the CloveCube device in device mangler and the pool drive went offline. I also stopped both DrivePool services. The drives still did not sleep. So this tells me it's very unlikely to be DrivePool related.
Anyway, here is an excerpt from my response to Christopher in the support team:
QuoteInterestingly, I did come across a similar post on reddit and a guy responded who said he worked in one the big data farm suppliers. He said that drives should NOT sleep as in his experience if they shutdown/startup even just a *couple of times a day* then they found this significantly increased the risk of them not starting up. He said that they have found, in particular for NAS drives, that they should just be left running 100% when the system was on.Given the above, which is far more experience than I have, I think i'm better off leaving them online. I'm not sure what more I can do with the cooling - i've got 3x120mm fans at max speed on them - but they are maxing at 39c and Seagate RECOMMENDED max is 40 with a total max of 60c. I'm sure it's not helping their lifespan but...Anyway, thank you again for your time and assistance, as always with you guys, it's very helpful!
Just to add a little clarity. Of the 8 drives in the case three of the drives *were* maxing out around 42 to 44c but since then I added the third fan AND spaced them out a little more so this is why those three are now maxing out at 39c. The other 5 in the case are maxing out at 32-35 so the CPU case disks I think are now OK.
The external enclosure Oyen Mobius Pro 5C simply can't handle the heat from these disks so, I've gone old school and stuck a USB powered fan in front of it with the door open. This brings the disks in this right down to 32c (Oyen - I hope you see this!!! VERY POOR!). This is only used once a week as an external mirror sync backup so this is an acceptable work around. And actually as the desk fan is USB powered the Mobius enclosure does indeed power the fan from it's outbound USB port.
-
Product: StableBit DrivePool
Version: 2.2.4.1162I've an issue where no matter how many fans and maxing out the speed setting on the fans the hard drives are getting to over 40c. I've set the windows sleep timer for all the disks in Advanced Power to sleep in 1 minute but, this isn't happening and I believe this is due to DrivePool somehow making the OS think the disks are in use when they are in fact idle. I'm currently running 8x8tb pool and also a 4*12tb pool and both pools have exactly the same problem.
Do you think this is a possibility? If so, any tips on how I might be able to let the disks sleep when not being used by anything other than the DrivePool service?
-
15 hours ago, Christopher (Drashna) said:
for everyone, (will update main post), try this build:
http://dl.covecube.com/DrivePoolWindows/rc/download/StableBit.DrivePool_2.2.1.925_x64_RC.exeIt may not fix the issue, but just in case....
All fixed. Thank you very much for the swift work and resolution!
-
1 hour ago, seanvree said:
I"m having this same issue. I enabled driver verifier on covefs.sys and covefs_disk.sys.
However, Windows 10 immediately BSOD on boot now with error "Bug Check 0xC1: SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION"
I also tried installing .922 RC but having the same BSOD
Sincerely hope the team is working on this. Show stopper.
That's not the same error as us, it's totally different. Suggest you start another thread and log a ticket. Also, read through a thread before posting.
-
4 hours ago, aniel said:
we are in the same boat, im still waiting for a fix
6 hours ago, Ryokurin said:It was happening before 1803. I've had it for several months, but I was thinking it was a hardware issue. I recently rebuilt the entire machine and just started to research reasons why.
I uploaded my dump too, Happens every time you run a an executable directly in the pool from a remote computer. Hope that helps.OK, so I just rebuilt my server for a third time in 2 days and it's now at 1511. I've installed the release (not RC) of stablebit and then accessed an exe on the server and ran this on the laptop from the server. Running a remote exe from the DP worked fine for me.
-
11 hours ago, aniel said:
this is a joke, there is new update StableBit.DrivePool_2.2.1.923_x64_RC.exe wich i have been checking periodically yet the change log does not say anything about fixing this issue, this is not fair and also frustrating, if anybody know a way to go back to 1709 without losing anything and without rollback option let me know.
Don't bother with the RC above, it has exactly the same issue (I'm using it).
I can't rollback as mine is a new install straight from Microsoft using the Windows Media Creation tool so I don't have an old version of Windows 10 to install/rollback to. Just FYI: Microsoft no longer host older versions of Windows 10 so I would have to get an older copy from somewhere else.
I'm amazed this got through testing, i mean, it was tested, wasn't it Cove????!!!!
-
Yeap, EXACTLY the same problem here.
Copying files TO the pool via network share creates an instant BSOD.
-
Thanks! Fingers crossed for the future then.
-
That's what I've done, thanks.
What a about the other tabs of Balancers and File Placement?
-
Thanks!
I've got "Do not balance Automatically" selected but I can't find a trigger option to deselect?
Do I have to be concerned with any of the slections in the Balancers tab or the File Placement?
-
Hi Guys
i use DrivePool with SnapRAID and I think i made a silly error and have now lost data.
I setup DrivePool and left it to BALANCE files out across disks. SnapRAID is sort of like a software RAID. I lost a disk and asked SnapRAID to restor but I think in the time between purchasing a new disk/install, DrivePool has re-balanced my files, probably breaking the SnapRAID parity data. Now, if this is correct, and it probably is, this is clearly my fault as I configured stuff wrong.
What I would like to know is how do I make SURE 100% that any and all file balancing/moving is turned off in DrivePool?
Thanks!
-
Hey Mick,
Did you have MM before Drivepool and use a drive map backin the day? MM are correct, drive maps are not supported anymore however, they are wrong in that MM does not always tell you about historically added media. For example, only tonight I found out that my Sons Of Anarchy failed to start. Quick look in collection management and it was mapped to my old X drive. Deleted the show and readied via UNC and all working fine. Does that help?
Other than that, MM works perfectly via Drivepool and UNC maps.
-
Hi Stablebit!
Quick question with DrivePool. I currently have 7 disks FULL of data, NTFS, that I want to pull in to the pool. I've installed Drivepool but, i can't see the existing data within the pool.I tried using this trick http://wiki.covecube.com/StableBit_DrivePool_Q4142489 but even though I have show hidden files etc. I cannot see a hidden directory called PoolPart.xxxx on the test drive (Original drive D:) that I've allocated to the pool (X:)Any ideas?Thanks!
File Scan Reports 1 Sector Lost. File Recovered but disk will not clear "Damaged" status
in General
Posted
Hi all,
thanks for your replies but, the issue has vanished so, i'm really not sure what is going on.
I had to rebuild the machine for other reasons and since it's been rebuilt I've reinstalled Scanner and performed a fresh scan and none of the lost sectors are there. I'm guessing that they've already been marked as bad and replaced by other spare sectors - aparently HDD can actually do this.
Anyway, all good now. We do still need an option to "acknowledge" though as even marking it as suggested by Doug will still bring the errors back again at point of next scan.