1 Topic by cerebro84 (edited by cerebro84 2007-04-20 12:57:57)

  • cerebro84
  • New member
  • Offline
  • From: Agrigento - Sicily
  • Registered: 2007-04-20
  • Posts: 1

Topic: [resolved] parted cancelled while working - data lost?

This is gparted log:

Grow /dev/sdb2 from 99.92 GiB to 199.80 GiB  04:49    ( ERROR ) 
      
   calibrate /dev/sdb2  00:01    ( SUCCES ) 
      
  path: /dev/sdb2
start: 415585485
end: 625137344
size: 209551860 (99.92 GiB) 
   calculate new size and position of /dev/sdb2  00:01    ( SUCCES ) 
      
  requested start: 206130015
requested end: 625137344
requested size: 419007330 (199.80 GiB) 
  new start: 206130015
new end: 625137344
new size: 419007330 (199.80 GiB) 
   check filesystem on /dev/sdb2 for errors and (if possible) fix them  00:23    ( SUCCES ) 
      
  ntfsresize -P -i -f -v /dev/sdb2 
      
  ntfsresize v1.13.1 (libntfs 9:0:0)
Device name : /dev/sdb2
NTFS volume version: 3.1
Cluster size : 4096 bytes
Current volume size: 107290546688 bytes (107291 MB)
Current device size: 107290552320 bytes (107291 MB)
Checking for bad sectors ...
Checking filesystem consistency ...
Accounting clusters ...
Space in use : 107217 MB (99,9%)
Collecting resizing constraints ...
Estimating smallest shrunken size supported ...
File feature Last used at By inode
$MFT : 93 MB 0
Multi-Record : 107264 MB 28192
$MFTMirr : 30290 MB 1
Ordinary : 107291 MB 20039
You might resize at 107216728064 bytes or 107217 MB (freeing 74 MB).
Please make a test run using both the -n and -s options before real resizing!
 
   move partition to the left  00:01    ( SUCCES ) 
      
  old start: 415585485
old end: 625137344
old size: 209551860 (99.92 GiB) 
  new start: 206130015
new end: 415681874
new size: 209551860 (99.92 GiB) 
   move filesystem to the left    ( EXECUTING ) 
      
   perform readonly test    ( EXECUTING ) 
      
   using internal algorithm 
   read 209551860 sectors 
   finding optimal blocksize 
      
   read 32768 sectors using a blocksize of 128 sectors  00:01    ( SUCCES ) 
      
  32768 of 32768 read 
  0.876353 seconds 
   read 32768 sectors using a blocksize of 256 sectors  00:00    ( SUCCES ) 
      
  32768 of 32768 read 
  0.823979 seconds 
   read 32768 sectors using a blocksize of 512 sectors  00:01    ( SUCCES ) 
      
  32768 of 32768 read 
  0.7981 seconds 
   read 32768 sectors using a blocksize of 1024 sectors  00:01    ( SUCCES ) 
      
  32768 of 32768 read 
  0.795769 seconds 
   read 32768 sectors using a blocksize of 2048 sectors  00:01    ( SUCCES ) 
      
  32768 of 32768 read 
  0.727686 seconds 
   read 32768 sectors using a blocksize of 4096 sectors  00:00    ( SUCCES ) 
      
  32768 of 32768 read 
  0.750913 seconds 
   optimal blocksize is 2048 sectors (1.00 MiB) 
   read 209355252 sectors using a blocksize of 2048 sectors    ( EXECUTING ) 
      
  12816884 of 209355252 read

is there any way to resume its work? I think it was doing a not-destroying task... Thanks in advance for any help

** EDIT **
Resolved using gpart that worked greatly. Thanks however!