- This topic has 6 replies, 2 voices, and was last updated 1 month, 3 weeks ago by
.
-
Posts
-
My Humax 2000T disk (let’s call it H) became unreadable recently. A professional recovery outfit corrected it and also provided a clone disk and its contents on an external USB drive (E).
I happened to have a similar spare disk (S) which I installed in the Humax. I now know this was not a good idea because every time a drive, that is different to the removed drive, is installed the Humax insists on formatting it as a unix EXT3 drive.
Therefore, I could not reinstall the recovered drive (H) or its clone without loss of contents.
I was advised to remove disk (S), connect it to my Windows 10 desktop PC and copy the required files from the USB drive (E). Then I can replace drive (S) in the Humax without having to reformat it and, hopefully, play the recovered files.
I have achieved most of this, but not the copy from (E) to (S).
To enable Windows to access EXT3 drives I installed Linux File System for Windows from Paragon Software. Disk (S) is reported to be mounted in Read-Write mode with 400GB free space. I can Copy files from it and Paste elsewhere but whenever I try to Copy and Paste any file to it I get error message that it is ‘too large for the destination file system’.
How can I copy files to this disk?
k64 – 23 mins ago »
My Humax 2000T disk (let’s call it H) became unreadable recently. A professional recovery outfit corrected it and also provided a clone disk and its contents on an external USB drive (E).
I happened to have a similar spare disk (S) which I installed in the Humax. I now know this was not a good idea because every time a drive, that is different to the removed drive, is installed the Humax insists on formatting it as a unix EXT3 drive.
Therefore, I could not reinstall the recovered drive (H) or its clone without loss of contents.
Why would installing drive (H) cause loss of content? Is it not formatted as EXT3?
I had replaced the original (H) drive with my spare drive (S), which the Humax formatted because it was a new drive.
I have recently tried replacing (S) with the recovered (H) drive but the only option offered is to format it, so losing all recovered content.
k64 – 13 mins ago »
I had replaced the original (H) drive with my spare drive (S), which the Humax formatted because it was a new drive.
I have recently tried replacing (S) with the recovered (H) drive but the only option offered is to format it, so losing all recovered content.
So they have recovered the data but not the correct formatting, is that correct? What have the recovery company said about this?
I understand it to be a Humax ‘feature’ that formatting is always required when changing drives. (See 2nd para of my original post)
e.g.
drive A, remove A, replace A = OK no formatting required.
drive A, replace with B -> format*, remove B, replace A -> format*.
* These formats are required because this drive is not the same as the immediately previous drive.
k64 – 17 mins ago »
I understand it to be a Humax ‘feature’ that formatting is always required when changing drives. (See 2nd para of my original post)
e.g.
drive A, remove A, replace A = OK no formatting required.
drive A, replace with B -> format*, remove B, replace A -> format*.
* These formats are required because this drive is not the same as the immediately previous drive.
It certainly is not the case that changing drives requires a format. The format option is only offered if the drive format is not what the Humax was expecting.
I must have picked up some misinformation from somewhere, certainly not here. Sorry.
On receiving the ‘recovered’ drive (H), its clone (C) and the USB drive (U) from the data recovery people, I tried each of them in the Humax and took a photo of each result. Photos attached. (H) and (C) gave same results, only one shown in photos. I also ran a HDD test on them in the Humax. Result was error code 8, which isn’t in my documentation. Drive (U) was tried in the front USB socket (nothing was expected, just interested).
I have just tried attaching (H) and (C) to my PC but neither were recognised by File Explorer and not by Linux File System either which says no supported volumes have been found.
I am awaiting a response from the data recovery people. Until then I don’t want to mess with drives (H) or (C) so I will replace (S) in the Humax for the weekend and hope I soon receive information on how to copy files to (S) using the Linux File System without error messages.
- You must be logged in to reply to this topic.