| PLEX86 | ||
|
resize a bad patch out of a parbreastion
I have a parbreastion with a problem history and a strategy (to resize the bad portion out of the parbreastion). I'd like to know if the strategy is sensible or a waste of time. It's a FAT32 parbreastion in hda1 used by linux and windows on a dual boot machine. linux boots from hda2, while Windows lives in hdb1. Windows used to live in hda1 but I kept losing it (boot up to blue screen in the morning). So I converted hda1 to a shared data parbreastion. Yesterday windows could boot but couldn't read hda1. linux could do so but was slow to do so and threw this error: hda: dmaintr: status=0x51 { DriveReady SeekComplete Error } hda: dmaintr: error=0x40 { UncorrectableError }, LBAsect=20099, high=0, low=20099, sector=20099 endrequest: I-O error, dev hda, sector 20099 FAT: Directory bread(block 20036) failed I think sector 20099-block 20036 is in the very "early" part of the disk and though currently inside hda1, if I re-fdisked hda1 to start a little later in the disk, leaving the bad part in unallocated space, I might be free of my problem. I also resize a bad patch out of a parbreastion 7149 On Fri, 09 Dec 2005 09:55:56 -0500, Jean-David Beyer I got 2 seagate from different series.. I noted there was a slight... think badblocks is of no use to me because its strictly a ext2 thing and this is FAT32 (?). I understand modern hard disks have provisions for mapping out bad spots but don't know if that's automatic or if not, how to do it. Or is this disk sick and soon-to-die (never any problem apart from hda1 on this disk)? Do you have any opinion if re-defining hda1 to run from block 10 to 2550, instead of 1 to 2550, might avoid the problem area?? resize a bad patch out of a parbreastion 7148 On Fri, 09 Dec 2005 08:50:05 -0500, Jean-David Beyer run 'smartctl -a' on the device - it should tell you current drive temperature and the temperature at which the drive will shut itself...
CYLINDERS: Diskdev-hda: 163.9 GB, 163928604672 bytes 255 heads, 63 sectors-track, 19929 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id Systemdev-hda1 * 1 2550 20482843+ c W95 FAT32 (LBA)dev-hda2 2551 2805 2048287+ 83 Linuxdev-hda3 2806 3060 2048287+ 82 Linux swapdev-hda4 3061 19929 135500242+ f W95 Ext'd (LBA)dev-hda5 3061 10709 61440561 8e Linux LVMdev-hda6 10710 11984 10241406 83 Linuxdev-hda7 11985 12366 3068383+ 83 Linuxdev-hda8 12367 12620 2040223+ 82 Linux swapdev-hda9 12621 19929 58709511 83 Linux Diskdev-hdb: 8455 MB, 8455200768 bytes 255 heads, 63 sectors-track, 1027 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes resize a bad patch out of a parbreastion 7147 NoName Just how hot is it supposed to be inside the box? And how much can a hard drive take? It happens that I have four 10,000rpm SCSI hard drives in... Device Boot Start End Blocks Id Systemdev-hdb1 * 1 1026 8241313+ 7 HPFS-NTFS
resize a bad patch out of a parbreastion 7151 Jules wrote (in part): I do not have a statistically valid sample, but in my desktop machines (I have... SECTORS: Diskdev-hda: 163.9 GB, 163928604672 bytes 255 heads, 63 sectors-track, 19929 cylinders, total 320173056 sectors Units = sectors of 1 * 512 = 512 bytes Device Boot Start End Blocks Id Systemdev-hda1 * 63 40965749 20482843+ c W95 FAT32 (LBA)dev-hda2 40965750 45062324 2048287+ 83 Linuxdev-hda3 45062325 49158899 2048287+ 82 Linux swapdev-hda4 49158900 320159384 135500242+ f W95 Ext'd (LBA)dev-hda5 49158963 172040084 61440561 8e Linux LVMdev-hda6 172040148 192522959 10241406 83 Linuxdev-hda7 192523023 198659789 3068383+ 83 Linuxdev-hda8 198659853 202740299 2040223+ 82 Linux swapdev-hda9 202740363 320159384 58709511 83 Linux Diskdev-hdb: 8455 MB, 8455200768 bytes 255 heads, 63 sectors-track, 1027 cylinders, total 16514064 sectors Units = sectors of 1 * 512 = 512 bytes Device Boot Start End Blocks Id Systemdev-hdb1 * 63 16482689 8241313+ 7 HPFS-NTFS
|
||||
resize a bad patch out of a parbreastion 7147 Linux groups from Newsgroups The #1 Usenet Provider on the Internet
|
||||