Jump to content

fleggett1

Members
  • Posts

    45
  • Joined

  • Last visited

  • Days Won

    4

fleggett1 last won the day on September 5 2023

fleggett1 had the most liked content!

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

fleggett1's Achievements

Advanced Member

Advanced Member (3/3)

4

Reputation

  1. Oh. That's...interesting. Well, at least that's something I can rule out when it comes to pool mysteries, as I thought for sure I had a huge problem after the chkdsk thing. I suppose I could chkdsk the individual disks myself manually, but I expect Scanner does all that periodically and then some (at least, I hope so).
  2. I actually tried several variations of the copy command, like *.* and *?.?* and none of them worked. However, for some cosmically unknown reason, now it's working under cmd with no elevation. I'm 100% serious. I can only surmise that an application had gotten ahold of the directory at the same time I was attempting the copy command and had temporarily made it exclusive, as I haven't rebooted. However, even if that was the case, it doesn't explain why xcopy and Powershell's copy worked. It gets even better, though. I did an admin-level chkdsk in both cmd and powershell on the pool and got this in return: The type of the file system is RAW. CHKDSK is not available for RAW drives. I don't know what the frak is going on. The pool seems to be working just fine and disk management reports that each drive is NTFS'd, but chkdsk thinks the pool isn't formatted? Is the Sabrent enclosure futzing with things in ways DP and Windows can't understand? Do I need to bring in a witch doctor? I suppose another thing to consider is that the pool wasn't created in my current Windows 11 environment, but in my previous Windows 10 one. I'm beginning to fear that I'm gonna have to start things over from scratch, but that's probably going to necessitate getting a second enclosure since this one is full and I just don't have that kind of cash lying around right now.
  3. The pool is healthy and I'm not using any duplication. I haven't run chkdsk, so that's something to try. No hidden files, no long paths, and no weird unicode stuff involved. I am running the pool off of a Sabrent 10-bay enclosure, but I don't see why that would be a factor. I'll run chkdsk when I can get to the pool again. I just want some stability in my life at this point, as I built a new machine with a screaming Ryzen 9 cpu to replace my old Norco and have had all sorts of problems, with this being just another one. No crashes, just strange stuff that isn't really DP or Scanner related (most of it involving the igpu/HDMI).
  4. What in the sam hell does this mean when trying to do a cmd-based copy using a filename mask? "The system cannot find the file specified." This is what I get when trying to do a "copy * [destination]" in a few directories in Windows 11 on my one (and only) Drivepool pool. I can copy the files if I don't use a wildcard, but I've never seen this sort of error and it's got me really, REALLY spooked. All of the files just have the "A" attribute and there aren't any other hidden or system files in these directories. xcopy under cmd works. And the internal copy command in Powershell works, so it's something endemic to vanilla cmd. I'm confuzzled!
  5. gtaus, the Sabrent is a really nice enclosure. Looks to be all-metal and would undoubtedly kill someone if dropped on their head, even empty. Doesn't even need drive sleds, which a lot of server-style enclosures force onto people, like my old Norco (now Secdin). On the expensive side, but the build quality and it only needing the one USB-C port are terrific selling points. Unfortunately, I have no idea regarding drive speeds, as I haven't run any tests. I would guess that it's just as quick as if the drives were directly connected to the motherboard. I've streamed several near-100 GB UHDs and haven't run into any stuttering, which is all I wanted. It sounds like DP is, to put it charitably, "slow" when it comes to drive evacuations. I'm not sure a faster USB connection would help in this regard, as DP seems to have its own game plan when shuffling stuff around. If you have any other questions about the Sabrent, feel free to ask.
  6. BTW, Amazon has the 10-bay version at 10% off rn, making it $540 (before tax). Dunno how long it'll last. If I had the money, I'd get a second during this discount.
  7. Hmmm. I thought I ran another scan shortly after the long formats were complete, but a lot has been going on in my life for the past couple of months and I can't say with 100% certainty that I did so. So, if the bad sectors were remapped as part of the long format and Scanner is now showing them green across the board, would you re-add them back to the pool or get rid of them?
  8. About a month ago, Scanner reported that two of my drives were exhibiting unreadable sector issues. I evacuated and removed them from the pool, but kept them installed intending to do something about the pair "later" (I'm a master procrastinator). Since they remained installed, Scanner could still access them and do surface scans. As such, all this time, the Scanner tray icon has been gold (I think it's gold) indicating continuing drive problems. Until today. I woke up today with the Scanner icon blue. Weird. I initiated a manual scan of both drives and no unreadable sectors were found. I'm more than a little confused. Did the drives automagically fix themselves at some point? Is it possible the onboard drive firmware remapped the bad sectors to good sectors when my back was turned? Do I dare try to use them at this point or should they still be tossed? I should note that I did a long format of the drives shortly after Scanner reported the bad sector issues. I was hoping that might trigger a remapping, but it didn't seem to do anything, as Scanner still reported that both drives had bad sectors after a scan.
  9. They seem to be alright, though I haven't done any formal testing, just eyeballing the speeds given by Windows when doing copies/moves. I can stream UHDs with no problem. I've since assembled a system with native USB-C, which seems to've solved the spin-up issue I mentioned earlier. It's a really nice enclosure that's built like a tank. If/when I run out of bays, I'll probably get another one. It's expensive, but only needing the one USB cable (two if you count power) is REALLY nice. I also haven't seen any temperature issues since converting from the Norco.
  10. I'm just full of questions lately. This might be a dumb question, but what's "safe" to do with files on drives that are in the process of being moved around, like with a (re)balance? I mean, can you just use the pool as normal (reading, writing, deleting, etc.) or should you wait until the rebalance is done to ensure the pool remains 100% intact? Also, does DP "lock" drives that are being (re)balanced or restrict them in some fashion from being used?
  11. Well, I'm using a Sabrent external enclosure - https://sabrent.com/products/ds-uctb - so I dunno what sort of performance hit I'm running into versus if the drives were plugged directly into a motherboard. But if you think several days to evacuate a large drive is reasonable, that's fine, I just wanted to make sure I wasn't seeing a big problem with my setup.
  12. Is it common for an almost-full 16 TB drive evacuation to take several days? I started the process this past Tuesday and it's not going to complete until tomorrow (Friday). The source and target are bog-standard 6 Gb/s drives (WD and Seagate). I haven't done the math, but the time it's taking just seems a little excessive. All drives are in an external Sabrent enclosure.
  13. Hmmm. HMMMM. I think you might be onto something, as the freespace on my drives was spanned across all of them instead of one or two drives having the 800 GB. I don't know how Sonarr (pre)allocates space on the target, but it may not've made any difference given how that 800 GB was spread across the pool. Yeah, it must've been that, as Sonarr was able to resume transfers once I installed the new drive. DP is now rebalancing everything, which looks like it'll take a couple of days to complete. I'm definitely not turning things off until that's done. BTW, the scrollbar in DP isn't working in my installation - I have to use the scrollwheel, instead. It does work in Scanner, though. Thanks for the quick feedback. I would never have thought of that being the answer.
  14. I recently built a new Windows 11 system, as my old 10 box was showing its age, and I'm running into a very strange problem with Sonarr in conjunction with DP. Both Sonarr and DP report 800 GB of free space. This is based on a target pool with a total of 83 TB (soon to be 101 TB, as I just received another drive today). I know weird things can start to happen when a file system approaches zero space, but 800 GB seems like plenty of play. The problem is that Sonarr can't import anything to the pool, as it doesn't think it has the necessary space. These are (relatively) small episodic files at around 7 GB each. I know this because I went through the latest Sonarr log and saw this rather alarming entry: "System.IO.IOException: There is not enough space on the disk." I've done a few Google searches of this error as it relates to Sonarr, but it looks like whatever bug caused this was fixed long ago. I also scanned their Discord to see if this is a new bug, but no one has reported anything. As such, I can only surmise the problem is on DP's end. So, any ideas? Is there some invisible drivespace overhead DP employs to manage pools that isn't reported to the user? I'm not doing any duplication, but even if I were, 800 GB is still 800 GB of presumably usable space. I'm using the latest versions of both DP and Scanner. Thanks in advance.
  15. It's alive, it's alive! ...but with a caveat. My system is so old that it doesn't have a native USB-C port, so I had to buy an internal card with several that's natively recognized by Windows 10/11. I don't know if that affects anything, but the caveat is that it takes the Sabrent a few seconds after the desktop appears to fully spin-up all the drives. This screws with one application I'm running in a fairly minor way, as the pool isn't initialized at that point, and is work-aroundable. Scanner is...interesting. Every drive on the main menu shows-up as an "ASMT ASM235CM SCSI Disk Device", but if you look at the disk information, it's all good, with the correct manufacturer, model, serial, etc. SMART data also appears to be coming through. This same label also appears in Device Manager for every drive. If you assign a manual name, though, that label appears in Disk Management (I've labeled all mine). The "labeled" name also appears in Drivepool. I guess it doesn't particularly matter, but maybe you can try to have the "labeled name" display in Scanner in a future version, as that would be much handier. Oh, something else that's neat - you don't have to do the 3.3V hack with the Sabrent, which is something I had to do with the Norco. This is doubly good, as you then don't have yellow tape potentially gunking-up the SATA connector. Apart from the spin-up delay and the device names, everything seems good. The fans are super-quiet, so I don't know why people were complaining about that. The one bad thing is that it came with a ridiculously short power cord, so I had to dig-up one of my own. Anyone have any questions?
×
×
  • Create New...