F5F Stay Refreshed Software Operating Systems Unidentified area on storage device

Unidentified area on storage device

Unidentified area on storage device

Pages (2): 1 2 Next
X
xXFirewitherXx
Posting Freak
878
01-28-2016, 02:56 PM
#1
Hey everyone, I’ve got two identical hard drives set up for storage and they’re synced. Windows 10, WinDirStat, and TreeSize all display the same file count, but one drive shows 5.2GB less free space in Windows Explorer. WinDirStat labels it as “Unknown.” I’m familiar with checking hidden files, but it seems this isn’t a system file. Any ideas on how to uncover what’s missing? Thanks!
X
xXFirewitherXx
01-28-2016, 02:56 PM #1

Hey everyone, I’ve got two identical hard drives set up for storage and they’re synced. Windows 10, WinDirStat, and TreeSize all display the same file count, but one drive shows 5.2GB less free space in Windows Explorer. WinDirStat labels it as “Unknown.” I’m familiar with checking hidden files, but it seems this isn’t a system file. Any ideas on how to uncover what’s missing? Thanks!

K
kiddswagg_760
Member
211
02-18-2016, 11:35 PM
#2
The system is designed to handle various file systems, especially suitable for compact Unix partitions. Windows often claims it supports any non-Microsoft file system, though this can vary.
K
kiddswagg_760
02-18-2016, 11:35 PM #2

The system is designed to handle various file systems, especially suitable for compact Unix partitions. Windows often claims it supports any non-Microsoft file system, though this can vary.

J
Jrry
Junior Member
20
02-19-2016, 07:32 AM
#3
Thank you for your response. The disk management reports no issues with partitions, and there are no changes I’m aware of. It appears this occurred recently, within the past day.
J
Jrry
02-19-2016, 07:32 AM #3

Thank you for your response. The disk management reports no issues with partitions, and there are no changes I’m aware of. It appears this occurred recently, within the past day.

C
Camsell
Member
207
02-20-2016, 12:17 AM
#4
What operating system are you running?
C
Camsell
02-20-2016, 12:17 AM #4

What operating system are you running?

C
Cl0ud_Client
Member
169
02-27-2016, 02:32 PM
#5
Windows 10, according to its original description.
C
Cl0ud_Client
02-27-2016, 02:32 PM #5

Windows 10, according to its original description.

K
King_James_XVI
Junior Member
23
03-08-2016, 04:08 AM
#6
Additionally, there are systems even older than Unix that are even more efficient in size. Unix mainly eliminated flat files, allowing file systems to shrink dramatically. Devices like palm pilots ran on such compact setups, using just a few kilobytes rather than megabytes.
K
King_James_XVI
03-08-2016, 04:08 AM #6

Additionally, there are systems even older than Unix that are even more efficient in size. Unix mainly eliminated flat files, allowing file systems to shrink dramatically. Devices like palm pilots ran on such compact setups, using just a few kilobytes rather than megabytes.

D
DannyBriere
Member
53
03-09-2016, 07:29 AM
#7
Another consideration: does it receive a negative location?
D
DannyBriere
03-09-2016, 07:29 AM #7

Another consideration: does it receive a negative location?

Z
zack4252
Junior Member
14
03-11-2016, 12:41 AM
#8
I mean I'm clarifying your question. Could you provide more details?
Z
zack4252
03-11-2016, 12:41 AM #8

I mean I'm clarifying your question. Could you provide more details?

D
Derfmiester
Junior Member
16
03-11-2016, 04:07 PM
#9
Maybe someone accidentally removed a Unix partition from your drive. Unix uses various file systems, the oldest being called fs. It was originally built for magnetic tape. I’m considering booting a BSD live CD to check if it can help identify the issue. I haven’t used these systems much myself, but I prefer BSD because some versions support older file systems that others have stopped using.
D
Derfmiester
03-11-2016, 04:07 PM #9

Maybe someone accidentally removed a Unix partition from your drive. Unix uses various file systems, the oldest being called fs. It was originally built for magnetic tape. I’m considering booting a BSD live CD to check if it can help identify the issue. I haven’t used these systems much myself, but I prefer BSD because some versions support older file systems that others have stopped using.

A
alejandrobo1
Posting Freak
877
03-12-2016, 06:32 AM
#10
If the location has a negative address, someone might be concealing something. A common method involves starting addresses at zero and increasing them, but modern drives use a design from an old technology called “drum memory.” They reshape the drive into a cone and flatten it into a platter, keeping the same logic. This means that if you assign a partition a negative address, many systems won’t be able to locate it even though it exists. But if you’re aware of the pattern, it becomes easy to find.
A
alejandrobo1
03-12-2016, 06:32 AM #10

If the location has a negative address, someone might be concealing something. A common method involves starting addresses at zero and increasing them, but modern drives use a design from an old technology called “drum memory.” They reshape the drive into a cone and flatten it into a platter, keeping the same logic. This means that if you assign a partition a negative address, many systems won’t be able to locate it even though it exists. But if you’re aware of the pattern, it becomes easy to find.

Pages (2): 1 2 Next