Jump to content

nauip

Members
  • Posts

    40
  • Joined

  • Last visited

  • Days Won

    3

nauip last won the day on July 23 2018

nauip had the most liked content!

Contact Methods

  • Website URL
    http://nauip.com

Recent Profile Visitors

1056 profile views

nauip's Achievements

Advanced Member

Advanced Member (3/3)

7

Reputation

  1. I eventually narrowed this down to (probably) a flakey power cable. It was usally specifically one drive affected, but sometimes it's neighbor. But I feel like if the app had told me which drive was affected I would have dove into the case with more specific information and figured this out days earlier. It was just tough to catch because very frequently by the time I could get either remoted into the server or physically back to the server the re-meaure would already be in progress. Regardless, a new power cable is en route from the PSU manufacturer and I will know for sure soon. /grumble grumble - dumb power connectors. But... Please guys - simply replace "A disk" with "[insert volume name here]" is missing from your drive pool. Making users dig through logs when you have the information right there is just plan mean.
  2. I would love to know which disk dropped out and then popped back in. It's done it several times.
  3. Can we get more info on when these messages pop up?
  4. Ignore current file-scan warning similar to the same thing you can do with SMART warnings. I have a couple drives with less than 1 mb of "bad blocks" either at the beginning or end of a drive. My preference would be to create a 10 gb partition to sequester said bad blocks leaving the remainder of the 6 tb drive to use. But since Scanner will tell Drive Pool "don't use that drive" I'm kinda stuck... unless I could tell Scanner - Hey, boss, that's OK. We'll just put some caution tape around that bad spot and keep on keeping on.
  5. I'm willing to roll the dice on it since I just want to use it as a plex transcode swap drive. I have no other good use for a 256 gb ssd that has possible problems and I didn't want to just toss it (yet). Also, I think the Intel SSD should mark them as unusable and replace it with a spare. I don't know that it will, but if using it as a transcode swap drive causes problems then I'll remove it. What I did was mark all as unchecked and turned off automatic scanning on the drive then restarted the service. This removed the alerts in the system tray which made me happy.
  6. Could you please add the drive identifier (letter, volume name, whatever, something). I got the error in the middle of the night. When I woke and checked on it all drives were present and accounted for. It would be nice to know which drive is glitching out and possibly failing in a manner that doesn't get otherwise logged. I suspect it was a firmware update on a switch (NAS-iSCSI connection), but it would be nice to be sure.
  7. I mean, I can make it go away, but not in a desirable manner. I added a nVME ssd into the system. I knew it had 1 unreadable sector (turns out it has 2, but that's not relevant). Stablebit scanner scanned the filesystem overnight and found 2 unreadable sectors. OK, that's fine, I don't care. I want to use it anyway (just not for data storage). It's notified me, quite persistently via the system tray and mobile app. I would like it to stop doing this like it would for a SMART error. Current status is fine, as long as it doesn't get worse. I can "Ignore Warning" for SMART, why can't I do it for file system scanner errors? If I leave the system tray alerts there, I might miss another more important warning - because that notification was there before.
  8. 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.
  9. 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.
  10. 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.
  11. 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.
  12. Ah, the troubleshooting log seems to be the hint I needed. Thanks!
  13. How do I get it to apply these rules? I have clicked "Rebalance" twice now and this message remains.
  14. 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.
×
×
  • Create New...