-
The forum software that supports hummy.tv has been upgraded to XenForo 2.3!
Please bear with us as we continue to tweak things, and feel free to post any questions, issues or suggestions in the upgrade thread.
Fixdisk caused HDR-FOX T2 to want to reformat the drive
- Thread starter aekostas
- Start date
bottletop
Active Member
That is the correct selection . Although I don't know why you have trouble after choosing the default option.
To be perfectly blunt, if you can't get the thing running on either your laptop or desktop pc, I'll be a little concerned of you using using that Live Linux environment - in case you obliterate the wrong drive(s)!
bottletop
Active Member
I have no idea what findroot is. My search results mention mathematical equations or possibly Grub? But I don't see how either will help you explore, repair or initialise a Humax hard drive attached to your desktop PC as an extra drive (assuming that is what you wish to do).
Eg What do you get after you select the default option? Is it not similar to the screenshots - https://www.system-rescue.org/Screenshots/
I also have no idea what you're trying to achieve so maybe someone else can help.
Sorry, findroot is the "Boot a Linux operating system installed on the disk (findroot)" option on my screenshot above.
The default option looks like the screenshots but gparted fails to start because it cannot find the display.
What I am trying to do is run
The default option looks like the screenshots but gparted fails to start because it cannot find the display.
What I am trying to do is run
e2fsck -f -c -c -k -y on the disk in question as per suggestion.
bottletop
Active Member
So, if we look at https://www.system-rescue.org/Screenshots/, how does that compare to the screen that you are on?
Are you stuck on the 1st blue screen, the 2nd black screen or the 3rd desktop screen (but eg without the foreground windows)?
Or maybe you can show us a screenshot of what you see or the actual screen(s) are stuck on?
If you're stuck on a screen similar to the 2nd one - then you're in a Linux CLI environment already (but maybe haven't determined the drive designations).
I just realised, does your desktop PC have a Linux system installed in it? If not then it won't find it.
USE THE FIRST/DEFAULT OPTION
Boot SystemRescue using default options
Although I suspect we may get into a pickle very shortly and repeat - you should be careful to not corrupt the main drive on your desktop pc.
Last edited:
prpr
Well-Known Member
You certainly don't want that on a Humax disk as there isn't an operating system on it, and even if there were, it would be for the wrong processor so wouldn't work anyway (the Humax gear doesn't use x86 processors). Just use the top option.
I got into the second screen, typed "gparted" and got an error message that it cannot connect to the display.
Hmmm, OK, need to type startx.
Black Hole
May contain traces of nut
Personally, I would have chosen the second option on that Grub menu (unless one is hampered by lack of RAM).
I think many inexperienced users would find it unsettling to get booted to a command line prompt rather than a familiar graphical environment, even when they are then instructed to bring up a terminal and use CLI utilities! That YouTube video shows starting the GUI as a boot menu option (or a hint to run "startx" from the command prompt pos-boot) which is not present in the menu shown in Post 41.
I acknowledge the text environment makes the lowest demands on a potentially wonky system one might be trying to rescue, but that is not the case in this situation. It's not the system that's wonky, it's the HDD. Therefore, it might be better advice to use GParted Live.
Personally speaking, I am not sure a GUI is as easy to instruct people to use. When I eventually end up doing the job, I hope to create a concrete cheat-sheet; describing this for GUI requires screenshots etc by someone who know what they are doing (so count me out 
). But for the CL commands, it should be pretty easy.
). But for the CL commands, it should be pretty easy.
bottletop
Active Member
I'm curious. Any chance of an update on this please?
Eg roughly how long did it take to run? Were you trying to recover your TV recordings from 1TB drive? If so how successful was it?
bottletop
Active Member
OK, let's put a pin on that for now.
What was the outcome of this? I.e. Running
e2fsck on the large partition.What are you trying to do with the drive taken out of the Humax?
Black Hole
May contain traces of nut
There seems to be some confusion here. What does "USB dongle" mean - adapter? If you didn't have an adapter, how did you run e2fsck?
It is great that there is so much interest. It is a shame I may not be worthy.
So, I had a powered USB adapter. The problem with it is that it knocks down my network for some reason, and it did so when I started e2fsck (more on that later). I blamed it on its flimsy construction and ordered a new one which, serendipitously, arrived 3 minutes after my earlier message. So, after relocating the desktop (for reasons I will explain in a mo), I plugged the disk in using the new adapter, and it knocked out my network too. The only other thing I can think of is open the desktop and plug the disk in one of the bays; I just don't have the energy just now.
As for the previous run, I aborted it. I had started it in the afternoon and it projected that a non-destructive, read test (all that from memory) would take 10 hours (well, it didn't, but I let it run for an hour, saw the reported percentage done and did a multiplication). As the desktop lives in an occupied bedroom (and given the adapter had killed my network) I just aborted and you know the rest.
Given the pain it has been to move it, connect it to my screen, swap cables, I may give it another go maybe on Sunday. I will keep you posted.
So, I had a powered USB adapter. The problem with it is that it knocks down my network for some reason, and it did so when I started e2fsck (more on that later). I blamed it on its flimsy construction and ordered a new one which, serendipitously, arrived 3 minutes after my earlier message.
So, after relocating the desktop (for reasons I will explain in a mo), I plugged the disk in using the new adapter, and it knocked out my network too. The only other thing I can think of is open the desktop and plug the disk in one of the bays; I just don't have the energy just now.As for the previous run, I aborted it. I had started it in the afternoon and it projected that a non-destructive, read test (all that from memory) would take 10 hours (well, it didn't, but I let it run for an hour, saw the reported percentage done and did a multiplication). As the desktop lives in an occupied bedroom (and given the adapter had killed my network) I just aborted and you know the rest.
Given the pain it has been to move it, connect it to my screen, swap cables, I may give it another go maybe on Sunday. I will keep you posted.
Black Hole
May contain traces of nut
What, you mean a USB-SATA adapter obliterated your WiFi? My bet is on the PSU/wall-wart (or a very lousy WiFi).
The box has two disks already in it and a DVD drive. I connected the Hummy HDD (SATA) using the DVD drive's data cable and powered it through an available power connector. The BIOS sees all three HDDs when I enter the booting process but the system now fails to boot from the System Rescue disk (it loops back to the BIOS or hangs). Should I (re)move the jumper from the Hummy drive, or remove the DVD drive power connector, is any of that relevant?