yes it had 2 but somehow they got deleted. i ran a dskchk G: and it failed to find both parttions. also it said something about the volume. sorry i cant confirm much as i am at work atm will get back to you when need a nerd come in :)
Just because ext3 is the sensible choice for a journalled file system under Linux doesn't mean that's what whoever wrote the software for the 900 HD chose. They certainly didn't choose it for the 980 HD or either my iMac with the suitable utility, or my Vu+ Duo, with built-in ext3 support would have been able to mount a volume formatted by the 980 HD; they couldn't.
Through elimination, I came to suspect that JFS was used, but was unable to confirm this. What the case is with the 900 HD is anyone's guess.
still havnt had a reply for ultrapower. dont think they actually will reply seeing as i know for a certain that they dont want anything to do with this and utterly do not care. if they did they would have looked into a better system and actually documented what is actually under the box. IMO.
xarqi: Just because ext3 is the sensible choice for a journalled file system under Linux doesn't mean that's what whoever wrote the software for the 900 HD chose...
... What the case is with the 900 HD is anyone's guess.
Good point. Viewing the partition table under Linux would help to see what's going on.
I had a drive go to raw once but cant remember how I fixed it. Google Fat32 now raw and go through the solutions there. Maybe something that will work for you
HTPC Intel Pentium G3258 cpu, Gigabyte H97n-wifi motherboard, , 8GB DDR3 ram, onboard graphics. Hauppuage HVR 5500 tuner, Silverstone LC16M case, Windows 10 pro 64 bit using Nextpvr and Kodi
It looks like there are ways to convert some file systems to some others without data loss, especially if there is a lot of free space on the volume. The Linux utility Gparted seems to be the tool of choice.
That doesn't get us much closer to a solution, but it eliminates the need for magic to explain the problem!
Also, in doing some reading on this I learned something that may be obvious to you Windows types, but is worth spelling out I think. "Raw" is the name of the disc volume access method used when Windows either cannot identify, or does not have the necessary capability to use whatever file system is actually present. Essentially, it is a "last resort" allowing programs to access any block of the drive, but there is no file structure information available.
I think it boils down to this: either you'll find a system that can mount the disc using whatever file system it is using (ext3, JFS, something else), allowing you to copy your data off onto another disc, or you can wave goodbye to the files that were there. A variation on that may be to use Gparted to convert file system X back to FAT32, if that is what you want, while retaining the files. That path calls for a skilled and confident Linux user.
Whoops. My mistake, the unit can format in either FAT32 and JFS according to the manual. I misread that. Sorry. Those EXT3 drivers will be of no use in this case.
update its gotten worse.it cannot be detectd on anything now whatsoever the status light is solid no flashing whatsoever so disapointed. what to do what to do?
oh and by the way i think this should be moved to another topic? harddrives maybe
Edit: just went onto Device manager and the fault said code 10. i wish i could swear on this forum cos thats all i feel like doin atm!!!!!!!
OK, I have one of these and as far as I can see, it recognizes only two file systems; FAT32 and NTFS. I put my ext2 (non-journalling linux) formatted drive in the system and it wouldn't recognize it.
However, it did nothing to that drive, only failed to recognize it.
I then got the box to format it NTFS and have been moving the drive between the box and a (ubuntu linux) laptop without problems since, (other than being unable to play the recorded files on my laptop).
It is very unlikely the box will do anything to a drive unless you ask it to.
Did you use the box to correctly unmount the drive before you unplugged it? Removing mounted drives is a common way to cause file system corruption...
oh snap. i could have done this because it froze up on me when i tried to open my music folder with over 30000 songs so i just unplugged it without thinking. FML anyway to fix this?
I am sorry I am not much help to you there. I long ago decided backups were better than file recovery and I haven't used FAT32 (other than on memory sticks which I regard as temporary storage) for a long time.
If you search the web for FAT32 partition or file recovery, I'm sure you'll find something. But even with a good utility, file system recovery can be hit or miss on file systems which are implemented as linked lists or any non-journalled file system for that matter...
Spoke to need a nerd. they explained it to me like i was a dummie;
"Once i plug my Chineese Speaking harddrive into a Japanese speaking classroom the teacher discipline's the device to speak japanese and japanese only."
Spoke to need a nerd. they explained it to me like i was a dummie;
"Once i plug my Chineese Speaking harddrive into a Japanese speaking classroom the teacher discipline's the device to speak japanese and japanese only."
I lold at this
Your problem could have a number of explanations;
(1) The box unilaterally reformatted your drive to another file system without asking you.
If this were true, this would be a box killer problem. But think about it for 10 seconds, even if it didn't recognize the file system on your drive, what manufacturer would be stupid enough to silently reformat an unrecognized drive on a box that advertises media player capabilities, i.e. they know that people are going to plug in devices with existing files and will probably be quite upset to lose them.
Enough speculation. In my first post, I suggested I had plugged an unrecognized file system into my box and as far as I can tell, it was not reformatted until I asked the box to reformat it, and then the only two choices I was given were FAT32 and NTFS. I chose NTFS because FAT32 is braindead.
Furthermore, using your need a nerd's analogy, the 900hd speaks chinese. That is, FAT32 is one of the file systems that it recognizes, so it would have no need to reformat.
It seems to me that (1) is a very unlikely explanation of your problem.
(2) When you navigated to your 30,000 file media directory, you caused the box's FAT32 file system driver to run out of memory and lock the box which either then, or on reboot caused file system corruption. This is a guess based on information you provided in a previous post.
(3) Your drive is failing.
(4) Something else, some other unreproducible system event such as a power surge...
If it is (2), it is not good for the 900hd as many storage devices are formatted FAT32 by default. However, this problem should be reproducible (with some testing) so that a bug report could filed and the problem fixed.
In the meantime, why would anyone be using the FAT32 file system for streaming media files which are reasonably likely to be greater than 4GB in size? NTFS is also compatible with windows and has no such limitations.
I know none of this helps you recover your files, sorry.
Are you subscribed to our RSS feed? You can download the latest headlines and summaries from our stories directly
to your computer or smartphone by using a feed reader.
