USB Drive Not Found (Windows)

Well, I finally got a HD Homerun and took an old PC I had lying around. Installed Window 7, updated, etc. Downloaded the DVR software, and attached a 2TB USB drive. Formatted the drive, got it recognized by Windows as drive I:, then installed the DVR software.

When I configured the DVR storage, the only drive showing was C:; the USB drive shows in all other applications on the machine, but not the DVR. I configured the storage on the C: drive, but I really need to be able to use the USB drive.

Any ideas as to what I’m doing wrong?

-Dan

Hmm, this might be a bug. Can you visit http://127.0.0.1:8089/system/disk and copy/paste the results?

Since you already configured the DVR, you can now uncheck the DVR box and change the text box below to say D:, then recheck it.

Okay, I unchecked the box, etc., and now in the Settings screen it shows the disk having 2TB available, instead of the 200GB it was before. We’ll see how it records tonight.

Thanks for the help.

-Dan

Please also let me know what the output of http://127.0.0.1:8089/system/disk says. Perhaps there’s a bug on windows7 where its not detecting external drives.

Also… something that is not usually mentioned, but if you formatted the drive yourself make sure to format it NTFS or exfat for windows. If you formatted it fat32 then you will have an issue with the 2gb file size limit of fat32.

Here’s the output:

[{“device”:“C:”,“mountpoint”:“C:”,“fstype”:“NTFS”,“opts”:“rw.compress”}]

FWIW, the recordings are being written to the USB drive.

-Dan

Thanks for the reply. I did format it NTFS when I set it up.

-Dan

Thanks. I’m not sure why your D drive is not listed…

I’m also using a USB drive on windows 10 and I see:

[{“device”:“C:”,“mountpoint”:“C:”,“fstype”:“NTFS”,“opts”:“rw.compress”},{“device”:“D:”,“mountpoint”:“D:”,“fstype”:“exFAT”,“opts”:“rw”}]

Could you please open powershell and run this command, then copy/paste the results back.

Get-CimInstance Win32_LogicalDisk

The term ‘Get-CimInstance’ is not recognized as the name of a cmdlet, function, script file, or operable program. Check
the spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:16

  • Get-CimInstance <<<< Win32_LogicalDisk
    • CategoryInfo : ObjectNotFound: (Get-CimInstance:String) [], CommandNotFoundException
    • FullyQualifiedErrorId : CommandNotFoundException

Hmm, on windows 7 the version of powershell is older. Try this one:

Get-WmiObject Win32_LogicalDisk

Yeah, that worked better:

DeviceID : C:
DriveType : 3
ProviderName :
FreeSpace : 211188002816
Size : 247001509888
VolumeName :

DeviceID : D:
DriveType : 5
ProviderName :
FreeSpace :
Size :
VolumeName :

DeviceID : E:
DriveType : 2
ProviderName :
FreeSpace :
Size :
VolumeName :

DeviceID : F:
DriveType : 2
ProviderName :
FreeSpace :
Size :
VolumeName :

DeviceID : G:
DriveType : 2
ProviderName :
FreeSpace :
Size :
VolumeName :

DeviceID : H:
DriveType : 2
ProviderName :
FreeSpace :
Size :
VolumeName :

DeviceID : I:
DriveType : 3
ProviderName :
FreeSpace : 1900808732672
Size : 2000363188224
VolumeName : DVR

I think I found a fix for this. Please visit your DVR settings page and click ‘check for update’. Once you’re updated to 2017.05.08.2150, visit http://127.0.0.1:8089/system/disk and let me know if the drive shows up in that list now.

Hate to inform you, but I’m already on version 2017.05.08.2150.

The DVR auto-updates itself. What does http://127.0.0.1:8089/system/disk say now?

Same as before:

[{“device”:“C:”,“mountpoint”:“C:”,“fstype”:“NTFS”,“opts”:“rw.compress”}]

Thanks. Can you try again after upgrading to v2017.05.09.1717

[{“device”:“C:”,“mountpoint”:“C:”,“fstype”:“NTFS”,“opts”:“rw.compress”},{“device”:“I:”,“mountpoint”:“I:”,“fstype”:“NTFS”,“opts”:“rw.compress”}]

Excellent! Looks like the bug is fixed. Thanks for reporting it and helping test.