e2fsck closed with exit code 9

[Peso]

I’m not too concerned here about saving this disk if its not easy or not possible. So please, no one go out of their way.

Quick background, have taken a 500GB out of a donated HDR to put in my Mum’s faulty T2. Had found a 320GB out of a HDR that's been laying around from years ago, so put it in the donated HDR.
I can’t remember if I had taken the 320 out just to put a bigger a drive into one of various HDR’s I have, or replaced it because it was going funny. If it was going funny I should have left a note with it for my future self.

Been running fix-disk on it for a day and half, with it doing things to Inodes at lightening speeds. "fix-disk" did crash at one point with a message about running out of space. I failed to make a screen shot of exactly what it said, so will justifiably burn in hell forever. I now get...see attached when I run fix-disk.

A google around and I see reference to bad sectors in relation to error 9. Should I just toss it?

 

[Luke]

What does the smart data say for the disk?

 

[Peso]

Good question. Overall health passed. No reallocated sectors, no pending.

 

[bottletop]

As it's an old drive, you probably can't remember what's on it.
Why not save some time and just reformat the drive?

 

[Peso]

As it's an old drive, you probably can't remember what's on it.
Why not save some time and just reformat the drive?

I had formatted it after fitting in back in a HDR.
Then ran fix-disk and did a day and half of inodes.
I shall format it again and see what fix-disk says.
Thank you.

 

[Peso]

Just to reiterate, I can bin this disk. But it's turning out interesting.
I had formatted it when I put it back in a HDR. I formatted the HDD with the Humax software. I went in with a browser and had to complete the install of the CFW as it was in the flash from the days with the HDD I've taken away for other duties.
I was then presented with a blank basic CFW interface in a browser.

Having just reformatted the drive in the HDR I got the web interface of the machine it was taken out of year ago, with it's name in the bar at the top and programs.
Opened telnet and put in fix-disk. Rather than telling me it was to reboot into maintenance mode, it just ran fix-disk. When it got to hda3 the interface stopped working. Ended with same error 9. Rebooted, repeated, same result.

Pending any further suggestions I can try in the HDR, will extract the HDD and check and format it off my laptop. But it might be a few weeks till I've such time.
Thanks everyone for now.

 

[prpr]

I formatted the HDD with the Humax software.

If the Foxsat's formatter is as crappy as the T2's then it's not unexpected to get inode problems.

When it got to hda3 the interface stopped working. Ended with same error 9.

Just format that partition (and all the others) from the command line. I don't have access to a Foxsat any more to give you the exact command, but it will be something like mkfs.ext3 /dev/hda3

Pending any further suggestions I can try in the HDR, will extract the HDD and check and format it off my laptop.

Laptop running what, and format it with which filesystem? You need a Linux machine to format with ext3.

(And it's not helpful to refer to things as "HDR" as both the Foxsat and the Fox-T2 are HDRs - confusion or ambiguity reigns.)

 

[Luke]

As an alternitve, back in 2017, at prpr's suggestion I on an extremely long running fix-disk I found it much easier to just blank the disk using dd, (and then followed up with a normal Humax HDR-FOX T2 reformat).

I knew nothing about dd but after reading a few results of an internet search came up with:
dd if=/dev/zero of=/dev/sda bs=1M

Is that possible on a Humax Freesat HDR?

 

[prpr]

It is possible (substituting hda for sda, and other prerequisites) but I don't think it will achieve anything useful in this case.
(It would be nice to quote the reference post!)

 

[Peso]

Laptop running what, and format it with which filesystem? You need a Linux machine to format with ext3.

(And it's not helpful to refer to things as "HDR" as both the Foxsat and the Fox-T2 are HDRs - confusion or ambiguity reigns.)

It would be a Linux laptop. I wouldn't dare use anything else around here. I made the move last month to all Linux, as aren't going to buy a new computer just to run Windows 11.
Sorry for any HDR/T2 ambiguity.

Success by the way.
I formatted all 4 partitions with mkfs.ext3. On reboot requested to re-download the rest of the CFW. Instigated fix-disk, this time I got the warning message and it rebooted. Ran fix-disk and it completed in half and hour with no errors or anything to fix.

Note. I couldn't unmount any partitions at first. unmount /dev/hda3 returned unmount not found. So had the idea to run fix-disk which unmounted all 4 partitions then ctl+c to stop fix-disk. Then could reformat with mkfs.

Thank you prpr and everyone else.

 

[Black Hole]

Sorry for any HDR/T2 ambiguity

To be clear, you can't just say "HDR" (HDR-FOX, FOXSAT-HDR) or "T2" (HDR-FOX T2, HD-FOX T2) if you want to be understood, unless the thread title makes it clear. It would be nice if everyone posted in the relevant forum section so the context is implied, but not everybody does (so we end up having to check), and not all readers realise which section a post is in (if reading posts by "most recent" for example, rather than by browsing the forum sections directly).

Therefore, all new threads should at least spell out model descriptions in full, even if then abbreviated subseqeuntly.

"HD" similarly. Does that mean High Definition or Hard Disk? Use HD for High Definition and HDD for Hard Disk Drive.

For more style tips, see Newbies Guide and Glossary.

 

[prpr]

It would be a Linux laptop. I wouldn't dare use anything else around here. I made the move last month to all Linux, as aren't going to buy a new computer just to run Windows 11.

Just say no to forced hardware obsolescence and compulsory M$ accounts!

Success by the way.
I formatted all 4 partitions with mkfs.ext3. On reboot requested to re-download the rest of the CFW. Instigated fix-disk, this time I got the warning message and it rebooted. Ran fix-disk and it completed in half and hour with no errors or anything to fix.

Excellent.

unmount /dev/hda3 returned unmount not found. So had the idea to run fix-disk which unmounted all 4 partitions then ctl+c to stop fix-disk.

For future reference, the command is "umount", without the n. You could have read the script to see how it did it, but nice bit of thinking.