I had an old DVR system which I was recording my CCTV cameras
with it. Product is:
http://www.adk-security.com/lx-zeus-8-h264-channel-lite-silent-
with-mobile-login--usb-1240-p.asp
or in fact
http://www.qvissecurity.com/Catalogue/CEARANCE-BARGAINS/Analog-
Dvr/PROFESSIONAL-DVRs/APOLLO-PROLITE-LX/8-CHANNEL/LX-PRO-LITE-8-
Chn-1TB-LXAPOPROLITE-8-1TB
Now I found my CCTV disk, it's normal 1TB HDD. I want to see RAW
videos recorded from CCTVs in this HDD. File system is not
detected by FindAndMount, Partition Magic, Recover My Files, etc.
Windows says it's RAW disk.
I can't access videos, but when I open disk image and read sector
by sector I see data there. How can I properly read and extract
data from this disk?
Thanks
These are stored in xfs or a linux file system on this unit,
go to pendrivelinux.com and get a windows installer to make a bootable pendrive.
I prefer ubuntu or debian, choose one of the two and make a thumb drive on a fresh thumb drive.
boot that up on a computer, plug in the dvr drive via USB-ide/SATA converter (About $14) most places.
you should see the disk mount and the files will be viewable.
you can then plugin a NTFS formatted hard disk and copy those off to the external drive and view them in VLC player for windows videolan.org
Related
I was given a new 32GB USB 3.0 Flash Drive for Christmas. I have just downloaded a 4k version of a movie that is 4.53GB and I am trying to copy that file to the USB stick however whenever I try my laptop shows me a message saying the file is too large for my USB drive. However that is plainly not the case as it has 28.6GB free and should leave me with over 24GB after copying.
I am not sure what is using up the first 4GB on the drive as the existing SanSecureAccess folder and files are only 10MB or so. Therefore something hidden is using up the best part of 3GB on a brand new USB stick I have just popped out the wrapper. What I don't know but even so with 28GB I should be able to copy the file to my USB.
Is there some sort of limit on the size of a file you can "copy" and then "paste" from a folder to another drive in Windows or something, as that is the only thing I can think of as there is plenty of room so unless there is a process preventing the copy n paste I don't know what is going on.
I have had this issue many times before with files that are over a GB or so, when I have tried to copy them to USB sticks with plenty of space however the PC always shows me a message saying the file is too big for the USB drive when it isn't. However this is brand new USB stick just opened and nothing else has been copied to it.
I don't know if it's an issue with my PC, the file or the USB. I have got a new HP laptop for XMAS so I could try copying it once I have set that new laptop up but I am not sure why I would get issues on my current HP 64bit, laptop anyway.
Here is a screenshot of the folder, the message, and you can see how much space is on the drive as it's brand new.
Any help would be appreciated as I have no clue to why something that is only 4.5GB is too large for a 32GB drive.
Try to format your usb flash drive and you will see a choice of system file change it into NTFS
look like this
for USB Flash Drive ussualy the default setting was FAT32, there will be 2 option NTFS and FAT32, choose the Ntfs :)
What is the difference between a QNX "Flash filesystem image" and a "OS image"?
I've got an old PC104(x86) unit that works solely with a CompactFlash card drive and now I'm wondering if I need the first or the second one to put on my CF card. The QNX docs [1] states that only the OS image is bootable. I need the CF card to be bootable since there's no other drive to boot from. Thus, does that mean I can't benefit from the Flash file system image approach with my current setup?
I don't want to use the System Builder to customize my QNX OS or anything, since I still need the QNX SDP to run on the target.
It's been a while since I dealt with this, but the term "Flash filesystem image" is the bigger of the two. The filesystem image is the collection of bytes required to represent the filesystem on the flash device. It may hold such things as the OS image, your /tmp directory, your /home directory, and so on. The OS image, on the other hand, holds a second stage boot loader, the OS itself, and possibly some drivers.
I need to build a custom Suse Linux NFS Server that does compression on certain files that are stored on the disk, and decompresses files as they are read from the disk. This needs to be transparent to the remote users of the file system, meaning that if a user saves a 10MB file named XYZZY.tif on /archiveDirectoryOnNFSServer, that when they do a ls -l on that mounted directory, they will see a 10MB file called XYZZY.tif, even though the actual file stored on the disk on the NFS server will be XYZZY.tif.compressed, and it will be 2MB in size.
I'm expecting that I need to build this as a driver that sits below the NFS Server software stack, but, I'm having difficulty finding where to start. Are there existing NFS Servers that provide this level of customization through APIs? Will I need to modify source of an open source NFS Server, and, if so, is there one that would be easiest to start with, and are they modularly structured such that this will be straight forward? I'm having difficult locating relevant content on the internet, and any pointers will be greatly appreciated.
IMO that kind of functionality is absolutely not the NFS server's responsibility (an nfs server should, well, serve files over nfs), but the underlying filesystem's. However, there's not that much choice in Linuxland but you could start by checking out fusecompress and btrfs.
This post is a bit old so you may already be aware of some options here, but there are a couple others (both for server side).
http://zfsonlinux.org/
zfs filesystem has built-in compression. I typically use lzjb as it is the fastest compression algorithm and does a reasonable job (MySQL DB's get 2-4x compression, filesystems with non-compressed data get around 4). you have a choice of algorithm depending on how much CPU time you wish to offer the compression.
if you want different file types compressed then you may consider laying gluster on top of a set of zfs filesystems.
gluster will allow you to store certain file types (by extension) on different underlying filesystems.
in this case, you specify the underlying filesystem as a zfs volume with the particular options you need (for example, .zip and .png go on an uncompressed filesystem, while things you write once and read many like static html files might go on a higher compression--you'll pay once when it's written but reads should be really fast since it scans fewer disk blocks and decompression is very fast)
zfs will manage the nfs mounts if you use it as your nfs server--you wont want this if you lay gluster on top.
it's easy to specify dynamically other attributes per filesystem (atime/noatime, # of copies if you want redundancy other than your normal raid, you can add SSD's as cache devices to get more performance).
in these solutions, you still send the full uncompressed files over the wire, so it doesn't make up for network performance but gives a lot of options if you're trying to speed up Disk IO or get more utilization out of your drives.
I am working on Blackberry database dependent application. On click of button i just show some useful data on other screen by fetching data from .db file stored in my sd card. Initially I provide that ".db" file from my ASSETS.
Now, i have seen some users review, they are getting problem in using SD-Card.
My question is "Is is possible to use sql database/.db file without using SD-Card in my application in blackberry"
Please let me know if it is possible....!
There are two separated filesystems supported. The first - internal device filesystem, the second - memory sd card filesystem.
Internal device filesystem does not depend on memory sd card and it is possible to create file there. But note that if your database consumes all available internal memory then device becomes mad.
Internal memory is an important resource to support vital operating system activies and when there is a shortage of this kind of memory then weird things occur, like sudden restarts, freezing issues etc.
It's a little bit more complicated than just having write access to the filesystem. Only certain types of internal storage support SqLite. See BlackBerry SqLite db creation: “filesystem not ready”
I have two disks as .vmdk files, and four as .vdi files. I can boot virtual machines on them with Sun xMV VirtualBox, and they work just fine. However, I want to mount them on my local computer so I can read some files off of them without starting a virtual machine. I downloaded the vmware-mount utility, but I get this error:
Unable to mount the virtual disk. The disk may be in use by a virtual
machine, may not have enough volumes or mounted under another drive
letter. If not, verify that the file is a valid virtual disk file.
Thinking it's a problem with the utility, I downloaded the SDK and made my own simple program in C to try to mount a disk. It just initializes the API, connects to it, then attempts to open the disk. I get this error, once again claiming it is not a virtual disk:
**LOG: DISKLIB-DSCPTR: descriptor above max size: I64u
**LOG: DISKLIB-LINK : "f:\programming\VMs\windowstrash.vdi" : failed to open (The file specified is not a virtual disk).
**LOG: DISKLIB-CHAIN : "f:\programming\VMs\windowstrash.vdi" : failed to open (The file specified is not a virtual disk).
**LOG: DISKLIB-LIB : Failed to open 'f:\programming\VMs\windowstrash.vdi' with flags 0x1e (The file specified is not a virtual disk).
** FAILURE ** : The file specified is not a virtual disk
The files are clearly virtual disks, though, since I can actually mount and use them with a virtual machine. I tried detaching them from any VMs and trying again, but I got the same results.
Any ideas? Maybe the "descriptor above max size" is a hint?
.vdi is a VirtualBox supported format, but not supported by VMWare.
The .vmdk files are VMWare images - you should be able to load them fine using the vmware tool (VirtualBox supports these too, but the converse is not true).
However, if you are trying to just mount the VDI image somehow....
Try this blog
http://bethesignal.org/blog/2011/01/05/how-to-mount-virtualbox-vdi-image/
This is what you exactly should watch, if you wanna get this done within seconds.
I only posted this, since the other people who visit this page would find it easier.
Thanks.
In a case of removal of this blog in Future, posting the content briefly here would be helpful. So I would extract the contents and post it here as well.
Be the super user
sudo su
Load the nbd kernel module. - the network block device module
modprobe nbd
run qemu-nbd, which is a user space loopback block device server for QEMU-supported disk images. Basically, it knows all about weird disk image formats, and presents them to the kernel via nbd, and ultimately to the rest of the system as if they were a normal disk.
qemu-nbd -c /dev/nbd0 <vdi-file>
That command will expose the entire image as a block device named /dev/nbd0, and the partitions within it as subdevices. For example, the first partition in the image will appear as/dev/nbd0p1.
Now you could, for instance, run cfdisk on the block device, but you will most likely want to mount an individual partition.
mount /dev/nbd0p1 /mnt
When you’re done, unmount the filesystem and shut down the qemu-nbd service.
umount /mnt
qemu-nbd -d /dev/nbd0