1 (edited by exdeath 2007-01-04 05:02:41)

Topic: Error Moving/resizing partition

I've used Gparted several times and it is one of those cds you must always have with you. Thanks for the effort!

I've been an happy linux user for around a year now, and what started to be my toy OS became my main OS. Because of that I've been eating more of that ugly windows partition.
The problem came yesterday when I wanted to steal 10gig out of windows (hda1)  and put it in my /home (hda3) partition. I booted up the live cd resized the fat32 partition with no problem, then I moved the hda2 partition in order to have the unused space right by hda3 in order to resize. All of this went without a problem.

Things started to get messy when I tried to resize hda3. I got an error after around 10min. This happened several times, at first I thought it was because of the screensaver coming off so i forced myself to play tetris for a while tongue but it stopped at the same place. Tried just to move hda3 to the left and then do the resize and same thing while moving).
Booted up FC6, logged in at root and installed gparted and unmounted the /home directory (hda3). Started the process and same thing again.

Here is the error:

GParted 0.3.3

Libparted 1.8.1


Grow /dev/hda3 from 10.82 GiB to 24.31 GiB  11:11    ( ERROR )
     
   calibrate /dev/hda3  00:00    ( SUCCES )
     
  path: /dev/hda3
start: 92421945
end: 115105724
size: 22683780 (10.82 GiB)
   calculate new size and position of /dev/hda3  00:01    ( SUCCES )
     
  requested start: 64131480
requested end: 115105724
requested size: 50974245 (24.31 GiB)
  new start: 64131480
new end: 115105724
new size: 50974245 (24.31 GiB)
   check filesystem on /dev/hda3 for errors and (if possible) fix them  01:03    ( SUCCES )
     
  e2fsck -f -y -v /dev/hda3
     
  Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information

37274 inodes used (1.31%)
2223 non-contiguous inodes (6.0%)
# of inodes with ind/dind/tind blocks: 359/95/0
2107106 blocks used (74.31%)
0 bad blocks
1 large file

36007 regular files
1233 directories
0 character device files
0 block device files
0 fifos
0 links
25 symbolic links (20 fast symbolic links)
0 sockets
--------
37265 files

  e2fsck 1.39 (29-May-2006)

   move partition to the left  00:01    ( SUCCES )
     
  old start: 92421945
old end: 115105724
old size: 22683780 (10.82 GiB)
  new start: 64131480
new end: 86815259
new size: 22683780 (10.82 GiB)
   move filesystem to the left  10:05    ( ERROR )
     
   using internal algorithm
   copy 22683780 sectors
   finding optimal blocksize
     
   copy 32768 sectors using a blocksize of 64 sectors  00:04    ( SUCCES )
     
  32768 of 32768 copied
  4.03061 seconds
   copy 32768 sectors using a blocksize of 128 sectors  00:04    ( SUCCES )
     
  32768 of 32768 copied
  3.52672 seconds
   copy 32768 sectors using a blocksize of 256 sectors  00:03    ( SUCCES )
     
  32768 of 32768 copied
  3.16991 seconds
   copy 32768 sectors using a blocksize of 512 sectors  00:03    ( SUCCES )
     
  32768 of 32768 copied
  2.76875 seconds
   copy 32768 sectors using a blocksize of 1024 sectors  00:03    ( SUCCES )
     
  32768 of 32768 copied
  3.25439 seconds
   optimal blocksize is 512 sectors (256.00 KiB)
   copy 22519940 sectors using a blocksize of 512 sectors  09:48    ( ERROR )
     
  4361860 of 22519940 copied
  Error while reading block at sector 96947645
   4525700 sectors copied
   rollback last change to the partitiontable  00:01    ( SUCCES )
     
   move partition to the right  00:01    ( SUCCES )
     
  old start: 64131480
old end: 86815259
old size: 22683780 (10.82 GiB)
  new start: 92421945
new end: 115105724
new size: 22683780 (10.82 GiB)
   libparted messages    ( INFO )
     
  Input/output error durante leitura em /dev/hda

  ========================================

Edit: Tried it once more and same error while reading block at sector 96947645. Bad sector? How do I get around this?

Edit2: Searched the forums for bad sectors and bad clusters. All posts refer to NTFS, we are talking ext3 here.

2

Re: Error Moving/resizing partition

Hi,

please use the exported html next time, it's a bit easier to read smile
This could indeed be a bad block, i think it's a good idea to run 'badblocks'. (see man badblocks for details and make sure you run it read-only wink )

good luck and keep us posted.

3 (edited by exdeath 2007-01-09 21:15:44)

Re: Error Moving/resizing partition

Hi there,
Bad blocks run with no options prints a series of numbers which I deduce are badblocks tongue
How can I fix those?

4

Re: Error Moving/resizing partition

you can't fix badblocks. They are physically damaged sectors on the harddisk. It's best to make a backup asap and replace the disk.

5

Re: Error Moving/resizing partition

Auchh.... A 3 year old drive sad
Thanks for the help anyway and keep up the good work wink