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.
With the prelims all but over, I managed to get access to the desktop computer. I got it to boot from the System Rescue USB into Linux (findroot). It seems to report some issues, notably "Failed to find /sbin/init on any block device, cannot continue". It seems to see the Humax drive attached...
Ok, I overcame the rufus problem with the author's advice. My laptop will not boot from the USB key (it does not output to HDMI while rebooting and the screen is very, very broken), so I will have a go when I get a chance to access another computer.
When successful, I will go for this advice.
Just a wee update: the disk arrived, I fitted it in (with my son, extra bonus) and it seems to work. It downloaded the CF, I redeployed the extra packages, I added the two reminders.
System rescue is another story, some things maybe aren’t meant to be.
Mine has recurred: yesterday it booted correctly. But it had recordings stuck in the schedule from the day before yesterday and it clearly wasn't shutting down.
And I did not have BBC1 SD...
So I went in tunefix and told it to stop removing channel 1 (BBC 1 SD). I rescanned the channel that...
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.
With the prelims all but over, I managed to get access to the desktop computer. I got it to boot from the System Rescue USB into Linux (findroot). It seems to report some issues, notably "Failed to find /sbin/init on any block device, cannot continue". It seems to see the Humax drive attached...
Ok, I overcame the rufus problem with the author's advice. My laptop will not boot from the USB key (it does not output to HDMI while rebooting and the screen is very, very broken), so I will have a go when I get a chance to access another computer.
When successful, I will go for this advice.
Just a wee update: the disk arrived, I fitted it in (with my son, extra bonus) and it seems to work. It downloaded the CF, I redeployed the extra packages, I added the two reminders.
System rescue is another story, some things maybe aren’t meant to be.
Mine has recurred: yesterday it booted correctly. But it had recordings stuck in the schedule from the day before yesterday and it clearly wasn't shutting down.
And I did not have BBC1 SD...
So I went in tunefix and told it to stop removing channel 1 (BBC 1 SD). I rescanned the channel that...
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.