Recent content by thoughton

I mean, it's possible I used that blog - it was a long time ago - but honestly I don't remember doing so. I was wracking my brain just last night trying to remember how I formatted the disk originally, but could not recall anything. I genuinely concluded I must've just put the drive straight in...

Holy moly, it looks like it's worked! No more error message on startup, I can pause/rewind again, and my recordings are all present! I couldn't find these two recordings listed in the Media anymore, but honestly it's not a problem; that's a small price to pay. The random selection of other...

Oh whoops, sorry! Could that be why my previous fix-disk failed...? Looks like my fix-disk after formatting P1 was potentially more successful though: Please select option: fixdisk Any additional options (-h for list or press return for none): -d -P -y Are you sure you wish to run the hard...

Formatting P1 seems to have gone without issue. humax# mkfs.ext3 -m 0 -O sparse_super /dev/sda1 mke2fs 1.42.13 (17-May-2015) Creating filesystem with 263065 4k blocks and 65808 inodes Filesystem UUID: 678912f7-5c03-4270-b955-e2b2d9d75cee Superblock backups stored on blocks: 32768...

Ok I re-ran fixdisk again after rebooting, and it wasn't particularly successful... Please select option: fixdisk Any additional options (-h for list or press return for none): -d -P -y Are you sure you wish to run the hard disk checker (-d -P -y)? [Y/N] y Running /bin/fix-disk PART: [3 1 2]...

Ah, just attempted a fixdisk and immediately encountered this: Please select option: fixdisk Any additional options (-h for list or press return for none): -d -P -y Are you sure you wish to run the hard disk checker (-d -P -y)? [Y/N] y Running /bin/fix-disk PART: [3 1 2] FSCKOPTS: [] Checking...

Whoops, good point! Creating the swap seems to have been successful: humax# dd if=/dev/zero of=/mnt/hd3/.swap bs=1M count=128 128+0 records in 128+0 records out 134217728 bytes (128.0MB) copied, 2.337000 seconds, 54.8MB/s humax# humax# mkswap /mnt/hd3/.swap Setting up swapspace version 1...

I've updated the partition table so it now looks like this: Command (m for help): p Disk /dev/sda: 2000 GB, 2000396321280 bytes 255 heads, 63 sectors/track, 243201 cylinders, total 3907024065 sectors Units = sectors of 1 * 512 = 512 bytes Device Boot Start End Blocks...

Just to clarify, should I still mount P3 and do the swapon command after updating the partition table? Or just run fix-disk (without SMART) straight after updating the table?

It has actually just finished (or, at least, it has ended without me canceling it). Here's the output: humax# e2fsck -n /dev/sda2 e2fsck 1.42.13 (17-May-2015) Warning: skipping journal recovery because doing a read-only filesystem check. The filesystem size (according to the superblock) is...

Hmmm, could it in fact be stuck? It seemingly hasn't progressed still 25 minutes later...

e2fsck /dev/sda3 seemed pretty uneventful (hopefully a good thing): humax# e2fsck /dev/sda3 e2fsck 1.42.13 (17-May-2015) /dev/sda3 has been mounted 5901 times without being checked, check forced. Pass 1: Checking inodes, blocks, and sizes Pass 2: Checking directory structure Pass 3: Checking...

Should I try the previously mentioned e2fsck /dev/sda3 now before attempting to mount it?

Oh, an even quicker failure this time: humax# e2fsck -n /dev/sda1 e2fsck 1.42.13 (17-May-2015) ext2fs_open2: Bad magic number in super-block /usr/lib/ext2/bin/e2fsck: Superblock invalid, trying backup blocks... /usr/lib/ext2/bin/e2fsck: Bad magic number in super-block while trying to open...

Thanks. Below is the output from my attempt at changing partition 1's first sector to 56. humax# gfdisk /dev/sda GNU Fdisk 1.3.0a Copyright (C) 1998 - 2006 Free Software Foundation, Inc. This program is free software, covered by the GNU General Public License. This program is distributed in...