Hi all,
This issue first manifested itself as a delete-loop issue, box not recording and continiously showing * deleting...
When I fire up maintenance mode, disk-fix gives the following
OK, so what's up with this partition type?
Comparing with another similar post, I see someone else has the same numbers with the single exception on the block count on sda1 showing as 1052226. The plus here aparently means 'extended partition'. Hmmm not sure what to make of that.
My suspicion is that sda1 has too many blocks allocated and is somehow splilling over into sda2 thus causing sda2 partiton to appear corrupt. Is this a reasonable analysis?
I've tried
on all three sectors, all behaving the same way.
So, I'm a bit stumped now. Any guidance anyone can offer would be greatly appreciated.
cheers,
Rob
This issue first manifested itself as a delete-loop issue, box not recording and continiously showing * deleting...
When I fire up maintenance mode, disk-fix gives the following
Code:
Running /bin/fix-disk
Custom firmware version 3.00
Checking disk sda
Unmounted /dev/sda1
Partition /dev/sda2 is already unmounted
Partition /dev/sda3 is already unmounted
Running short disk self test
No pending sectors found - skipping sector repair
Using superblock 0 on sda1
Partition sda2 - Unrecognised partition type, aborting...
OK, so what's up with this partition type?
Code:
humax# fdisk -lu /dev/sda
Disk /dev/sda: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders, total 976773168 sectors
Units = sectors of 1 * 512 = 512 bytes
Device Boot Start End Blocks Id System
/dev/sda1 2 2104514 1052256+ 83 Linux
/dev/sda2 2104515 955787174 476841330 83 Linux
/dev/sda3 955787175 976768064 10490445 83 Linux
Comparing with another similar post, I see someone else has the same numbers with the single exception on the block count on sda1 showing as 1052226. The plus here aparently means 'extended partition'. Hmmm not sure what to make of that.
My suspicion is that sda1 has too many blocks allocated and is somehow splilling over into sda2 thus causing sda2 partiton to appear corrupt. Is this a reasonable analysis?
I've tried
Code:
hdparm --read-sector 1 /dev/sda
/dev/sda:
reading sector 1: succeeded
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
[snip ..]
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
So, I'm a bit stumped now. Any guidance anyone can offer would be greatly appreciated.
cheers,
Rob