Just to check in. I used a laptop this time, convinced it to see the USB drive and boot from it and got onto the System Rescue menu. I then tried the default option and the in-memory option and both of them finish with a black screen (no cursor, nothing). I am still to test the desktop (room...
Thanks for the advice re desktop. I hadn't appreciated I could use the Linux boot to fix the Windows drives. I will seek a primer.
Re adapter, I have two (one brand new), of different designs, with different power supplies and they both cause the fault. Not impossible for both to be faulty, but...
Thanks again. The drive had worked very well for me for years. I can't quite remember if I had first fitted it in my Toppy, before I got an HD TV thus the Humax. And this is why there was so much in it. :-) This does not mean that I would use one such drive again for this purpose. :)
Re new...
Sorry, I thought I was following your suggestions; it's just not everything went swimmingly. I did not do the secure delete, as I will just junk the drive; the whole point for me was to recover the recordings.
@bottletop, e2fsck -f -v -y /dev/sdxn, having booted with the default option, ran for...
Many thanks, I really appreciate it. It still reports errors very early in the process as per below.
I will try your suggestions after this run. Say it fails, is it ethical for me to format and sell it or is the hw suspect? I don’t have a use for it.
Thanks again. It was on 5-6. What I did before your message was power down, remove jumper, persevere and boot with default option.
I am also two hours into e2fsck -f -c -c -k -y. Is it adviseable to interrupt it and proceed as per your suggestion?
Good morning. I indeed removed the connections from the other drives and (possibly related, I may try to replicate) I got it working. I made two mistakes: I did not redirect output to a log file and I did not call date after the command to see how long it took. But maybe the command logs anyway...
Thanks, I didn’t touch the jumper.
@bottletop I have scared you witless, sorry about that. :-) I am not too worried about running the commands, the filesystems identify themselves quite clearly as linux.
I may try a couple more things, but it doesn’t look good just now.
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...
Two of them did, and it drops the Comtrends too, if nothing else I am thorough. :-) Not obvious how to solve this and I don’t want to stray from the scope for this thread. I will try to fit it in the bays.
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...
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...
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 e2fsck -f -c -c -k -y on the disk in...
The thing about the default option is that I do not know what to do after it boots; it does not look like a standard *nix terminal. I thought findroot would be easier, similar to connecting to the Hummy using telnet, it just cannot see the commands.
Just to check in. I used a laptop this time, convinced it to see the USB drive and boot from it and got onto the System Rescue menu. I then tried the default option and the in-memory option and both of them finish with a black screen (no cursor, nothing). I am still to test the desktop (room...
Thanks for the advice re desktop. I hadn't appreciated I could use the Linux boot to fix the Windows drives. I will seek a primer.
Re adapter, I have two (one brand new), of different designs, with different power supplies and they both cause the fault. Not impossible for both to be faulty, but...
Thanks again. The drive had worked very well for me for years. I can't quite remember if I had first fitted it in my Toppy, before I got an HD TV thus the Humax. And this is why there was so much in it. :-) This does not mean that I would use one such drive again for this purpose. :)
Re new...
Sorry, I thought I was following your suggestions; it's just not everything went swimmingly. I did not do the secure delete, as I will just junk the drive; the whole point for me was to recover the recordings.
@bottletop, e2fsck -f -v -y /dev/sdxn, having booted with the default option, ran for...
Many thanks, I really appreciate it. It still reports errors very early in the process as per below.
I will try your suggestions after this run. Say it fails, is it ethical for me to format and sell it or is the hw suspect? I don’t have a use for it.
Thanks again. It was on 5-6. What I did before your message was power down, remove jumper, persevere and boot with default option.
I am also two hours into e2fsck -f -c -c -k -y. Is it adviseable to interrupt it and proceed as per your suggestion?
Good morning. I indeed removed the connections from the other drives and (possibly related, I may try to replicate) I got it working. I made two mistakes: I did not redirect output to a log file and I did not call date after the command to see how long it took. But maybe the command logs anyway...
Thanks, I didn’t touch the jumper.
@bottletop I have scared you witless, sorry about that. :-) I am not too worried about running the commands, the filesystems identify themselves quite clearly as linux.
I may try a couple more things, but it doesn’t look good just now.
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...
Two of them did, and it drops the Comtrends too, if nothing else I am thorough. :-) Not obvious how to solve this and I don’t want to stray from the scope for this thread. I will try to fit it in the bays.
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...
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...
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 e2fsck -f -c -c -k -y on the disk in...
The thing about the default option is that I do not know what to do after it boots; it does not look like a standard *nix terminal. I thought findroot would be easier, similar to connecting to the Hummy using telnet, it just cannot see the commands.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.