jonli447 wrote:
The best way to really check, is to then run dd to grab all the bytes of sda2.
Well, that's how I'm trying to debug the partition with xfs_db, I don't like to mess with the live partition of my web/mail/ldap/storage server
Quote:
I'll admit, I'm a bit stumped, as I'm still unable to come across anything resembling your problem.
I understand that, however I still think there's something iffy here which could bite us in the back when we least expect it
Quote:
Here's something you can do for me however, since you are not in a position to format sda2. Can you at least give me a) the type of drive, and b) the distro you are using, and c) what versions of the kernel you have tried. It'll give me (or another) a better way to retrace your steps.
the drive
Code:
Intergrated Sata device found
scsi0 : Marvell SCSI to SATA adapter
scsi1 : Marvell SCSI to SATA adapter
Vendor: SAMSUNG Model: SP2504C Rev: VT10
Type: Direct-Access ANSI SCSI revision: 03
SCSI device sda: 488397168 512-byte hdwr sectors (250059 MB)
SCSI device sda: drive cache: write back
SCSI device sda: 488397168 512-byte hdwr sectors (250059 MB)
SCSI device sda: drive cache: write back
sda: sda1 sda2 sda4 < sda5 sda6 >
Attached scsi disk sda at scsi1, channel 0, id 0, lun 0
Attached scsi generic sg0 at scsi1, channel 0, id 0, lun 0, type 0
The distro is freelink, the partitions have been resized using
this tutorial (more or less). The current partitions are as follows:
Code:
Disk /dev/sda: 250.0 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sda1 1 25 200781 83 Linux
/dev/sda2 26 391 2939895 83 Linux
/dev/sda4 392 30401 241055325 5 Extended
/dev/sda5 392 428 297171 82 Linux swap / Solaris
/dev/sda6 429 30401 240758091 83 Linux
The kernels I tried are only the one that came with freelink, my own kernel (same as the one from freelink but basically using the stock config, cross compiled with the 2005q3-2 codesourcery cross toolchain), then I tried lb_worm's 2.6.22, 2.6.21 and yours, all with the same result, so I didn't really use them.
Register
Login
FAQ
Search
The only real way to truly get this down, is to verify the behavior on both "freshly" formatted hdd's (includes deleting the partition tables completely) as well as checking the entire older boxes. The best way to really check, is to then run dd to grab all the bytes of sda2. I'll admit, I'm a bit stumped, as I'm still unable to come across anything resembling your problem.
Hope this helps to clarify.
