Jump to content

nauip

Members
  • Posts

    33
  • Joined

  • Last visited

  • Days Won

    3

Everything posted by nauip

  1. Drives A and B are the same make/model. A is on the MB and B is on an add-in controller. (a necessity for the time being) They are formatted exactly the same and Windows says they are the same logical size, as does Steblebit Scanner (the 2 left frames). But DrivePool wants to be weird and call them slightly different sizes. Also the balancing is weird, but I'm not so worried about that. I suspect it is related to DrivePool thinking they are different size drives. I'm not sure if Drive A is getting shorted or Drive B is getting bonus space. 3.65 seems to agree with Windows and Scanner. This is a pretty minor issue, but it's kinda driving me nuts.
  2. Drat. The files are already mixed in the drivepool. (all of the files and the iSCSI volume) This would be a "Nice to Have" feature. Please consider this a feature request.
  3. Is it possible to esure at least 1 copy of every duplicated file is placed on one specific drive? I have a QNAP connected as a drive in my pool via iSCSI. Since it's RAID6 it would be spiffy if at least 1 copy of all duplicated files ended up on it. It has the space for it. All duplicated files in the drivepool already exist there currently in the usual haphhazard way. The logic being that the QNAP is protecting the files with RAID6, but if the control board dies in the thing the data is still within the pool duplicated elsewhere.
  4. Lucky me! I only have 4 of these. One of them is very unhappy. I am also very unhappy because I cannot figure out which one is the culprit. I will likely have to pull them one at a time a boot up each time until my system is less cranky.
  5. Ah, the troubleshooting log seems to be the hint I needed. Thanks!
  6. This issue persists. Any suggestions?
  7. How do I get it to apply these rules? I have clicked "Rebalance" twice now and this message remains.
  8. nauip

    Can I have a hint?

    I never figured out what file(s) caused the error but it seems to have gone away on its own.
  9. nauip

    Can I have a hint?

    I assure you, space is not the problem.
  10. I am running in to something similar to this. Mine is heavily favoring one SSD rather than "spreading the love" to all 4 of my SSDs.
  11. nauip

    SSD Optimiser

    Make sure SSD Optimiser is at the top of the Balancers order. Possibly below Stablebit Scanner if you have this installed. The balancers are used in order they are listed.
  12. I think it would be theoretically possible if you were so inclined to try it. Since drive pool is a service within Windows you would be asking for a good deal of trouble if you decided to try this. I suspect Windows Updating would cause you no end of trouble if you were ever to successfully get it running.
  13. Just ran in to this. Fixed now!
  14. Q1 - Drivepool isn't RAID, it's JBOD with awesome features. Q2 - I don't think it can/will do this. As far as I can tell, once the SSDs are full to their limits or if you use the scheduler it will just empty the SSDs. Others might have figured out what you are asking and likely know better. edited to add: This guy seems to be on to something.
  15. Ah, it's still early here. I'm not reading terribly thoroughly, yet. found.000 is where chkdisk throws "lost" files it finds on scan. For whatever reason the allocation table lost track of those files.I've never seen such a large number of them, but that's not to say it's not possible. Review the folder delete whatever you don't need, move everything else to a Recovered folder within your pool and forget about it. If it happens again, then get worried. If the condition of the disk is bugging you Stablebit Scanner is a good tool Stablebit sells, but there are free options that are just as good (but not automated) such as CrystalDiskInfo (my favorite tool). https://crystalmark.info/en/software/crystaldiskinfo
  16. The 129 MB partition is part of the underlying GPT partition structure and is normal. The scale that Microsoft uses for the representation of the volumes is phenomenally bad. It's only 129 MB and it's normal. IIRC it has something to do with recovery data. You can't allocate it, you can't expand the volume into it. It's just reserved space.
  17. Probably shadowcopy data. Check that Previous Versions tab.
  18. The LSI LOGIC LSI00276 6GB 16PORT adapter is a pretty good deal with the caveat that you will have the cables looping out and then back in to the case. When I got it @ $35 I figured I could deal with my already ugly closet server looking a lil bit funnier. And it's held up quite well. Amazon no longer has them @ $35, but Server Supply has them at $60. That plus some cables and that's still under $100. Amazon's cables to match: CableCreation Mini SAS 36Pin (SFF-8088) Male to 4 SATA ~ $15 each. editing to add: I found another 8 port internal only @ $66 at the same place.
  19. I have to search and look the fix for this up every time. Maybe the UI element to re-set the file system status could be made easier to find and understand? It seems like I have to manually set it to good, and then if I'd like Scanner to re-check it I set it to Unchecked and it should get checked on the next automatic scan.
  20. This answered my question, too. Though I suspected I already knew the answer, it's helpful to be sure.
  21. nauip

    Duplication Warnings

    I only read 2 comments in, I should have finished reading. I've already created a dummy file to resolve it. If it happens again I'll try to collect logs. So... I can't remove the uncensored image. I can't remove an image once uploaded. I can't keep one image out of the post in favor of the other once uploaded. I can't delete the post. How annoying.
  22. I bought 5 x 3 TB WD Red NAS drives all in one shot 3+ years ago. 2 started this around the 2+ year mark. 1 or 2 Pending each. The 3rd waited until the warranty was almost up. I should have acted faster on the RMA. For each I "Ignored the warning" until SMART promoted it to reallocated or un-correctable. I was able to get 2 in for RMA, but the 3rd temporarily went back to normal for a while after a full regular slow format. And then shortly after the warranty ran out in the space of a week it jumped to 3 reallocated, then 5. No data loss, fortunately. I did the slow format 1 at a time so as to move along the progress from Pending to something else. Something to try as it is forcing a write to each sector. That or a Drive Wipe 0+1. Go HGST whenever possible.
  23. So I'm shutting down my server to remove one of the 5 drives showing a ton of bad sectors. I realize a bit too late "Doh! I forgot to jot down the serial" No problem. I have a bunch of notification emails. Surely they tell me which drive in the email, right? Right?! So now I'm restarting my server to jot down the serial number. edit: Actually, skimming through the alerts, there seems to be 2 versions of the alert emails. I think maybe the 1st time the event is noticed by the software, but subsequent notifications do not contain any detailed information.
  24. This can't be repeated enough.You can backup locally and duplicate all you like. Fire doesn't care.
  25. For the log files, the error reports are generally, VERY small. And the service logs get cycled out every 7-10 days, IIRC. So it doesn't keep a HUGH amount. - 6 x 20 MB log files and 1 in progress ~ 9 MB at the moment. That, and the troubleshooter actually compresses the logs prior to upload, so it should take up a relatively small amount of space. - Some people have very slow internet. I have decent internet, so... just sayin' And was this uploaded as part of a ticket? Or did you use the forum email address? - I used the same email address with these forums and my software registration. It was filled in on the Troubleshooter fields provided as was the url for this OP.
×
×
  • Create New...