March 12, 201016 yr I'm doing a little housekeeping on my unRaid, moving files around and reorganizing the drives. Normally when I move all the files off of a drive, the unRaid webpage will show the number of free bytes as being equal to the disk size. For one of the empty drives though, there is a disparity and the amount of free bytes is less than the disk size by about 70 MB. I did a file system check through unmenu and it didn't show any problems, but I'm worried something is messed up on the disk. The array is not currently parity protected while I am moving everything around and I'd like to fix this problem before repopulating the drive. I tried mkreiserfs and it reformatted, but it did not solve this problem. Anyone have any ideas on how to fix this problem short of spending 12+ hours pre-clearing it?
March 13, 201016 yr Author I now have two drives that are empty and both don't show full free space. I precleared one of them and it didn't change anything. I guess I was wrong about empty drives showing full free space, I must have mis-remembered.
March 13, 201016 yr I now have two drives that are empty and both don't show full free space. I precleared one of them and it didn't change anything. I guess I was wrong about empty drives showing full free space, I must have mis-remembered. By chance, has an HPA been added? hdparm -N /dev/sdX will tell you. What do you consider "full space" Any file-system has its own administrative overhead.
March 13, 201016 yr Author I thought that whenever I stuck in a new drive, that what the webpage showed for "free" was equal to what is showed for "size". I don't have a new drive to test that, but after preclearing one of the old, emptied drives (which I assume would reset it to how it looked "new"), those two values are not the same, so I guess I was wrong about that. There is like a 50 or 60 MB difference. I ran that hdparm command and got the following response: /dev/sdf: max sectors = 976773168/3694640, HPA setting seems invalid I did a random sampling of drives and they all say the HPA seems invalid - is this something I should be concerned about?
March 13, 201016 yr I thought that whenever I stuck in a new drive, that what the webpage showed for "free" was equal to what is showed for "size". I don't have a new drive to test that, but after preclearing one of the old, emptied drives (which I assume would reset it to how it looked "new"), those two values are not the same, so I guess I was wrong about that. There is like a 50 or 60 MB difference. I ran that hdparm command and got the following response: /dev/sdf: max sectors = 976773168/3694640, HPA setting seems invalid I did a random sampling of drives and they all say the HPA seems invalid - is this something I should be concerned about? Nah... many drives say the same thing. The code reading the drive HPA has not caught up with the the latest manufacturers.
Archived
This topic is now archived and is closed to further replies.