1 (edited by Alan S 2009-12-30 16:23:28)

Topic: Solved: Error while reading, during move operation

Please do not spend time to resolve this issue. I would delete but don't appear to have that option.
I loaded Easeus Partition Master Home Edition (free) and resized my C: drive with no issues or error and about 10 min of my time.

Thanks,
Alan S
----------------------------------------------------------------------------------
I am trying to increase the size of my C: drive at the expense of my logical D: drive.
I have resized my D: drive and understand that I must move it to the back of the extended drive so that I can make contiguous room available to resize C: In every instance I get a Read Error as I attempt to move the data on D: to the back of the drive.

I have browsed this forum as well as Larry's Tips and have tried several leads for solutions, each resulting in this same error.

Therefore my post to the more experienced users on this forum. Any guidance would be appreciated.

Thanks and Regards,
Alan

(My GParted_Details follow:)

GParted 0.5.0

Libparted 1.9.0

Move /dev/hda5 to the right  00:16:30    ( ERROR )
       
calibrate /dev/hda5  00:00:00    ( SUCCESS )
       
path: /dev/hda5
start: 29302623
end: 67392674
size: 38090052 (18.16 GiB)
calculate new size and position of /dev/hda5  00:00:01    ( SUCCESS )
       
requested start: 35841078
requested end: 73931129
requested size: 38090052 (18.16 GiB)
new start: 35841015
new end: 73931129
new size: 38090115 (18.16 GiB)
check file system on /dev/hda5 for errors and (if possible) fix them  00:01:41    ( SUCCESS )
       
ntfsresize -P -i -f -v /dev/hda5
       
ntfsresize v2.0.0 (libntfs 10:0:0)
Device name : /dev/hda5
NTFS volume version: 3.1
Cluster size : 4096 bytes
Current volume size: 19502100992 bytes (19503 MB)
Current device size: 19502106624 bytes (19503 MB)
Checking for bad sectors ...
Checking filesystem consistency ...
Accounting clusters ...
Space in use : 10159 MB (52.1%)
Collecting resizing constraints ...
Estimating smallest shrunken size supported ...
File feature Last used at By inode
$MFT : 8540 MB 0
Multi-Record : 15044 MB 18077
$MFTMirr : 1 MB 1
Compressed : 720 MB 3123
Ordinary : 15848 MB 17738
You might resize at 10158956544 bytes or 10159 MB (freeing 9344 MB).
Please make a test run using both the -n and -s options before real resizing!
move file system to the right  00:14:48    ( ERROR )
       
perform read-only test  00:14:48    ( ERROR )
       
using internal algorithm
read 38090052 sectors
finding optimal blocksize
       
read 65536 sectors using a blocksize of 128 sectors  00:00:06    ( SUCCESS )
       
65536 of 65536 read
6.01838 seconds
read 65536 sectors using a blocksize of 256 sectors  00:00:06    ( SUCCESS )
       
65536 of 65536 read
6.5737 seconds
read 65536 sectors using a blocksize of 512 sectors  00:00:06    ( SUCCESS )
       
65536 of 65536 read
5.76511 seconds
read 65536 sectors using a blocksize of 1024 sectors  00:00:05    ( SUCCESS )
       
65536 of 65536 read
5.49762 seconds
read 65536 sectors using a blocksize of 2048 sectors  00:00:05    ( SUCCESS )
       
65536 of 65536 read
4.78903 seconds
read 65536 sectors using a blocksize of 4096 sectors  00:00:05    ( SUCCESS )
       
65536 of 65536 read
4.42253 seconds
read 65536 sectors using a blocksize of 8192 sectors  00:00:04    ( SUCCESS )
       
65536 of 65536 read
4.16585 seconds
read 65536 sectors using a blocksize of 16384 sectors  00:00:04    ( SUCCESS )
       
65536 of 65536 read
4.50935 seconds
read 65536 sectors using a blocksize of 32768 sectors  00:00:06    ( SUCCESS )
       
65536 of 65536 read
5.72522 seconds
read 65536 sectors using a blocksize of 65536 sectors  00:00:05    ( SUCCESS )
       
65536 of 65536 read
5.18576 seconds
optimal blocksize is 8192 sectors (4.00 MiB)
read 37434692 sectors using a blocksize of 8192 sectors  00:13:56    ( ERROR )
       
18502980 of 37434692 read
Error while reading block at sector 48226143
19158340 sectors read
libparted messages    ( INFO )
       
Input/output error during read on /dev/hda

2

Re: Solved: Error while reading, during move operation

Thank you Alan S for reporting back.  I am glad that you found a solution.

From the error log you posted, it appears that a problem was encountered reading from sector 48226143 of the disk drive.  This suggests that a hardware problem was encountered.

Hardware problems can start out as intermittent errors that increase in frequency as time goes on.  You might want to ensure that you have good backups of your data, and perhaps check the manufacturer web site for disk diagnostic utilities.  Please be forewarned that many of these disk diagnostic utilities will overwrite your data.