- Forum
- The Ubuntu Forum Community
- Ubuntu Official Flavours Support
- General Help
- [SOLVED] Gparted Error: Input/Output error during read on /dev/sda
-
Gparted Error: Input/Output error during read on /dev/sda
I was trying to shrink /dev/sda1 ( Label: Windows ) partition 10GB and add it to /dev/sda2 (Label: Files) (See Attachment). After moving 286GB suddenly I got that error message( See Attachment ).
FYI I mounted /dev/sda1 partition after starting moving process. May be this is the cause of the error.
I have noticed another thing, If I clicked on Retry/Cancel/Ignore button on the error message, progress bar of the moving process grows 0.01GB. That means to finish this process I have to click more thousands of clicks!! I also worried about my files.
So, Is there any way to safely complete this process or safely terminate this process, so that I can keep my files / data safe?
Last edited by Ashfaqur Rahman; December 28th, 2013 at 10:06 PM.
Registered Linux User #560763
-
Re: Gparted Error: Input/Output error during read on /dev/sda
Do yourself a favor and only use Windows utilities to manage Windows partitions. Linux utilities can cause issues like above. Use Windows Disk Management or any other such tool for Windows to ‘resize or move’ NTFS partitions.
-
Re: Gparted Error: Input/Output error during read on /dev/sda
FYI I mounted /dev/sda1 partition after starting moving process. May be this is the cause of the error.
No, you really should not have done that.
If you are really lucky, unmounting the partition again might allow the move to continue, but I have my doubts.
-
Re: Gparted Error: Input/Output error during read on /dev/sda
Thanks for you advice. @fantab
Actually I did’t do it, I was careful, I know that at this stage mounting partitions can cause damage. As I saw that this process would take almost 2 hours, I left my laptop for a while and when I came back I saw my brother mounted /dev/sda1 partition!! As soon as I noticed that I unmounted /dev/sda1 but you can see that error occurred@The Cog
But I am really really lucky this time!! I tried clicking ignore again and again and the progress bar upgraded almost 20GBs. But suddenly Live Ubuntu hanged!! Even hidden terminals(Ctrl + Alt + F1-F6) couldn’t work. So I had no option without force shutdown. I did that. When I restarted I noticed that my all files are safe and sound!
But Gparted is showing error sign in /dev/sda2( see attachment ). Under /dev/sda2 when I go to information option It suggest me » 10GB of unallocated space within the partition to grow the filesystem to fill the partition, select the partition and choose the menu item partition —> check «( see attachment )Now my question is, is it safe to do Check? As It is not possible for me now to backup almost 350GB of space and test myself.
Registered Linux User #560763
-
Re: Gparted Error: Input/Output error during read on /dev/sda
Oh, that’s a relief!
The check option says «check and repair». I guess it should be safe though I’ve never used it in anger (tried it just now on a spare partition and it instantly said it had finished).
As always, have a backup first, just in case.
-
Re: Gparted Error: Input/Output error during read on /dev/sda
Update:
I ran «Check» and It repaired my partition safely!Registered Linux User #560763
Tags for this Thread
Bookmarks
Bookmarks

Posting Permissions
Skip to forum content
GParted forum
Support forum for users of GParted and the GParted Live media
You are not logged in. Please login or register.
Active topics Unanswered topics
GParted forum → GParted → Input/output error during partition creation; can no longer see drive.
Pages 1
You must login or register to post a reply
1 2019-02-21 08:49:50
- ilikecats
- New member
- Offline
- Registered: 2019-02-21
- Posts: 3
Topic: Input/output error during partition creation; can no longer see drive.
Hello, I use to have a 3TB external hard drive formatted in NTFS.
In GParted I attempted to change the drive into an ext4 drive but, in the process, ran into an input/output error.
First I deleted the drive’s partitions, then created a new partition table (Device —> Create Partition Table.) Once the new partition table was created, I created a new ext4 partition.
Problem is while GParted was creating a new ext4 partition I got an «Input/output error during write on /dev/sdb» error. Now I can no longer even see the drive in GParted, or with these commands:
The drive use to show itself in the command line with those commands, but not any more.
I suspect that this error may have been caused by the fact that I deleted a MS Windows partition on a GNU/Linux machine. After encountering this error, I read on the Ubuntu forums that messing around with Windows partitions on GNU/Linux can cause errors just like this one.
Is there any way to find the drive again, and fix it in GNU/Linux? Or should I just wait until I can get a windows machine to try to find the drive?
Thank you in advance for your time!
For reference, here’s the GParted error message: https://0bin.net/paste/CgrzfZNJHRqzGRBl … auEPeixhtC
Edit: mfleetwo: Add text from linked gparted_details
GParted 0.25.0 --enable-libparted-dmraid --enable-online-resize
Libparted 3.2
Create Primary Partition #1 (ext4, 2.73 TiB) on /dev/sdb 00:26:14 ( ERROR )
create empty partition 00:26:14 ( ERROR )
libparted messages ( INFO )
Input/output error during write on /dev/sdb
Input/output error during write on /dev/sdb
Input/output error during write on /dev/sdb
Input/output error during write on /dev/sdb
Error fsyncing/closing /dev/sdb: Input/output error
Error opening /dev/sdb: No such file or directory
Error opening /dev/sdb: No such file or directory
========================================
2 Reply by class413 2019-02-21 12:01:17
- class413
- Moderator
- Offline
- Registered: 2007-05-25
- Posts: 2,368
Re: Input/output error during partition creation; can no longer see drive.
«Input/output error» messages are usually associated with hardware errors like bad sectors, faulting cables / connectors, perhaps a faulty power supply or even more severe problems like a dying hard disk.
So I would suggest to check the hardware: disconnect / reconnect power and data cables (SATA ? ) , and check the SMART data of the drive by the command
sudo smartctl -a /dev/sdb
(from a terminal window as root). It gives the eventual hardware issues with the drive as well as a «health» evaluation.
Another point is related to the partition table type: to make partitions bigger than 2 TiB (2.73 in your case) you have to use the GUID partition table (GPT) type, not the legacy msdos type. So, if you have made an msdos partition table, this could be an error source. As you have nothing on the drive, you can create a new partition table as GPT and try again.
*** It is highly recommended to backup any important files before doing resize/move operations. ***
3 Reply by ilikecats 2019-02-22 04:38:50 (edited by ilikecats 2019-02-22 05:01:40)
- ilikecats
- New member
- Offline
- Registered: 2019-02-21
- Posts: 3
Re: Input/output error during partition creation; can no longer see drive.
Hello class413 thank you for your helpful reply!
Reconnecting the cable connectors helped! I can now see the drive with commands like «sudo fdisk -l» again. Sometimes I don’t see the drive, and I see it after I reconnect the cable.
The external hard drive is connected to the computer by USB. The drive’s disklabel type is gpt.
sudo smartctl -a /dev/sdb
Returned this:
smartctl 6.5 2016-01-24 r4214 [x86_64-linux-4.4.0-141-lowlatency] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org
Read Device Identity failed: scsi error device will be ready soon
A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options.
I’m not sure how to enable SMART. After I plug in the external hard drive correctly, gparted takes a long time to load the drives and then gives this error message as a pop-up: «Remote I/O error during write on /dev/sdb.» I guess this is the drive’s fault.
4 Reply by class413 2019-02-22 15:01:39
- class413
- Moderator
- Offline
- Registered: 2007-05-25
- Posts: 2,368
Re: Input/output error during partition creation; can no longer see drive.
USB is normally supported by smartctl under Linux (except perhaps some old kernels in the past).
I read that there was no error message while creating the new partition table. The error message appeared when trying to create the new partition. So, something happened between the two operations, or there is something wrong in the place where the new partition’s sectors are located.
You can repeat the entire procedure, by creating a new GUID partition table, and next create a new partition for half of the entire disk space.
Another check is to run the command dmesg (as root) in the terminal.
You run the command, and after that you plug the external drive’s USB connector. The terminal will display everything the system tries to do, including drive connection and any errors encountered. When the system recognizes and connects the drive, you’ll see something related appearing in the terminal window. If you see the system trying again and again with no success, then probably something wrong happens with the device.
If the drive is connected, you can run the smartctl command (from another window). The dmesg terminal will continue to monitor the activity and give further messages.
In case the USB controller of the hard drive isn’t compatible with smartctl , you can look for any special check tool provided by the drive’s manufacturer. Western Digital, Seagate and other manufacturers offer such tools in their support web pages.
*** It is highly recommended to backup any important files before doing resize/move operations. ***
5 Reply by class413 2019-02-22 16:25:56
- class413
- Moderator
- Offline
- Registered: 2007-05-25
- Posts: 2,368
Re: Input/output error during partition creation; can no longer see drive.
Another thing to try, just in case the drive isn’t fully supported:
Use the ‘-T permissive’ option according the error report.
The error message is:
A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options.
Device’s firmware isn’t always fully compatible with the software. Norms often change, and manufacturers often implement their own (documented or not) commands. So, these «failures» appear.
The -T option means «tolerance» to command failures. The default setting is
-T normal
The available arguments for this option are:
conservative, normal, permissive, verypermissive
verypermissive will ignore any failure and try further.
permissive will ignore the first failure.
So, you can try
sudo smartctl -a -T permissive /dev/sdb
or
sudo smartctl -a -T verypermissive /dev/sdb
to see if you can get anything more. Of course, you don’t have to fully trust the output, however it can give some indication.
*** It is highly recommended to backup any important files before doing resize/move operations. ***
6 Reply by ilikecats 2019-03-06 02:49:29
- ilikecats
- New member
- Offline
- Registered: 2019-02-21
- Posts: 3
Re: Input/output error during partition creation; can no longer see drive.
Hello sorry for the late reply.
I would just like to mark this thread as resolved since I found another satisfactory way to fix the drive for now. I’m not really sure how to mark posts as «resolved» yet though.
Thank you so much for your willingness to help me.
7 Reply by class413 2019-03-06 10:48:35
- class413
- Moderator
- Offline
- Registered: 2007-05-25
- Posts: 2,368
Re: Input/output error during partition creation; can no longer see drive.
You can edit your initial post to add [SOLVED] in the thread’s title.
*** It is highly recommended to backup any important files before doing resize/move operations. ***
Posts: 7
Pages 1
You must login or register to post a reply
GParted forum → GParted → Input/output error during partition creation; can no longer see drive.
I was so dumb, to turn of the power on my Readynas Ultra 4 when it was installing the disk (3TB WD Green), I had no time to wait for it as I was going to return it (It was too damn noisy) The disk installation was at 0% and stayed like that for 2 minutes, so I decided to turn it off without really thinking about the consequences. Anyways, now it’s done, and I need to put it into my new NAS (Synology 413j), but that’s not going very good.
The disk is recognized in BIOS, and I get it up as /dev/sdc when I run gparted live on USB. But it is not shown in Windows device manager or in Ubuntu.
When I run sudo gparted on a live Ubuntu USB, I get Input/output error during read on /dev/sdc.
I have tried more stuff in gparted live, but to sum it up, it is very similar to what’s happening here: http://ubuntuforums.org/archive/index.php/t-1492414.html
Up to the part where he runs badsectors, and get alot of errors, I ran badsectors -vs (I guess that is just read, and show output. I ran it for about 3000sectors, and for each block it counted the output was: (and so on)
1
2
3
4
5
6
7
8
9
10
11
12
13
140.00% done, 0:01 elapsed. (14/0/0 errors)
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
310.00% done, 0:02 elapsed. (31/0/0 errors)
In gparted(live) the /dev/sdc disk shows, but its all unallocated, and it shows an input/output read error when it scans all disks. When I try to create a new partition, I get an error with no partition table. I go to device — create partition table, and select gpt, I get about 5-6 errors with input/output read and also write on /dev/sdc.
When I enter gdisk on gparted(live) I get:
Warning! Read error 5; strange behavior now likely!
Warning! Read error 5; strange behavior now likely!
Partition table scan:
MBR: not present
BSD: not present
APM: not present
GPT: not present
Creating new GPT entries.
When I run smartctl:
ubuntu@ubuntu:~$ sudo smartctl --all /dev/sdc
smartctl 5.41 2011-06-09 r3365 [x86_64-linux-3.2.0-29-generic] (local build)
Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net
=== START OF INFORMATION SECTION ===
Device Model: WDC WD30EZRX-00MMMB0
Serial Number: WD-WCAWZ2205xxxxx
LU WWN Device Id: 5 0014ee 25c5f8480
Firmware Version: 80.00A80
User Capacity: 3,000,592,982,016 bytes [3.00 TB]
Sector Sizes: 512 bytes logical, 4096 bytes physical
Device is: Not in smartctl database [for details use: -P showall]
ATA Version is: 8
ATA Standard is: Exact ATA specification draft version not indicated
Local Time is: Sat Sep 29 15:53:44 2012 UTC
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
General SMART Values:
Offline data collection status: (0x84) Offline data collection activity
was suspended by an interrupting command from host.
Auto Offline Data Collection: Enabled.
Self-test execution status: ( 0) The previous self-test routine completed
without error or no self-test has ever
been run.
Total time to complete Offline
data collection: (50700) seconds.
Offline data collection
capabilities: (0x7b) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
Offline surface scan supported.
Self-test supported.
Conveyance Self-test supported.
Selective Self-test supported.
SMART capabilities: (0x0003) Saves SMART data before entering
power-saving mode.
Supports SMART auto save timer.
Error logging capability: (0x01) Error logging supported.
General Purpose Logging supported.
Short self-test routine
recommended polling time: ( 2) minutes.
Extended self-test routine
recommended polling time: ( 255) minutes.
Conveyance self-test routine
recommended polling time: ( 5) minutes.
SCT capabilities: (0x3035) SCT Status supported.
SCT Feature Control supported.
SCT Data Table supported.
SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 0
3 Spin_Up_Time 0x0027 199 140 021 Pre-fail Always - 7050
4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 483
5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0
7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0
9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 572
10 Spin_Retry_Count 0x0032 100 100 000 Old_age Always - 0
11 Calibration_Retry_Count 0x0032 100 100 000 Old_age Always - 0
12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 142
192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 31
193 Load_Cycle_Count 0x0032 198 198 000 Old_age Always - 8522
194 Temperature_Celsius 0x0022 114 095 000 Old_age Always - 38
196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0
197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 1
198 Offline_Uncorrectable 0x0030 200 200 000 Old_age Offline - 0
199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0
200 Multi_Zone_Error_Rate 0x0008 200 200 000 Old_age Offline - 0
SMART Error Log Version: 1
No Errors Logged
SMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
# 1 Short offline Completed: read failure 90% 569 42084912
# 2 Short offline Completed without error 00% 388 -
SMART Selective self-test log data structure revision number 1
SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS
1 0 0 Not_testing
2 0 0 Not_testing
3 0 0 Not_testing
4 0 0 Not_testing
5 0 0 Not_testing
Selective self-test flags (0x0):
After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.
My gdisk session under here: But the most usefull I got to in the end:
Warning! Main partition table overlaps the first partition by 34 blocks!
You will need to delete this partition or resize it in another utility.
user@debian:~$ sudo gdisk
GPT fdisk (gdisk) version 0.8.5
Type device filename, or press <Enter> to exit: /dev/sdc
Warning! Read error 5; strange behavior now likely!
Warning! Read error 5; strange behavior now likely!
Partition table scan:
MBR: not present
BSD: not present
APM: not present
GPT: not present
Creating new GPT entries.
Command (? for help): ?
b back up GPT data to a file
c change a partition's name
d delete a partition
i show detailed information on a partition
l list known partition types
n add a new partition
o create a new empty GUID partition table (GPT)
p print the partition table
q quit without saving changes
r recovery and transformation options (experts only)
s sort partitions
t change a partition's type code
v verify disk
w write table to disk and exit
x extra functionality (experts only)
? print this menu
Command (? for help): n
Partition number (1-128, default 1): 1
First sector (34-5860533134, default = 2048) or {+-}size{KMGTP}: 2048
Last sector (2048-5860533134, default = 5860533134) or {+-}size{KMGTP}: 5860533134
Current type is 'Linux filesystem'
Hex code or GUID (L to show codes, Enter = 8300): l
0700 Microsoft basic data 0c01 Microsoft reserved 2700 Windows RE
4200 Windows LDM data 4201 Windows LDM metadata 7501 IBM GPFS
7f00 ChromeOS kernel 7f01 ChromeOS root 7f02 ChromeOS reserved
8200 Linux swap 8300 Linux filesystem 8301 Linux reserved
8e00 Linux LVM a500 FreeBSD disklabel a501 FreeBSD boot
a502 FreeBSD swap a503 FreeBSD UFS a504 FreeBSD ZFS
a505 FreeBSD Vinum/RAID a580 Midnight BSD data a581 Midnight BSD boot
a582 Midnight BSD swap a583 Midnight BSD UFS a584 Midnight BSD ZFS
a585 Midnight BSD Vinum a800 Apple UFS a901 NetBSD swap
a902 NetBSD FFS a903 NetBSD LFS a904 NetBSD concatenated
a905 NetBSD encrypted a906 NetBSD RAID ab00 Apple boot
af00 Apple HFS/HFS+ af01 Apple RAID af02 Apple RAID offline
af03 Apple label af04 AppleTV recovery af05 Apple Core Storage
be00 Solaris boot bf00 Solaris root bf01 Solaris /usr & Mac Z
bf02 Solaris swap bf03 Solaris backup bf04 Solaris /var
bf05 Solaris /home bf06 Solaris alternate se bf07 Solaris Reserved 1
bf08 Solaris Reserved 2 bf09 Solaris Reserved 3 bf0a Solaris Reserved 4
bf0b Solaris Reserved 5 c001 HP-UX data c002 HP-UX service
ef00 EFI System ef01 MBR partition scheme ef02 BIOS boot partition
fd00 Linux RAID
Hex code or GUID (L to show codes, Enter = 8300): ef01
Changed type of partition to 'MBR partition scheme'
Command (? for help): ?
b back up GPT data to a file
c change a partition's name
d delete a partition
i show detailed information on a partition
l list known partition types
n add a new partition
o create a new empty GUID partition table (GPT)
p print the partition table
q quit without saving changes
r recovery and transformation options (experts only)
s sort partitions
t change a partition's type code
v verify disk
w write table to disk and exit
x extra functionality (experts only)
? print this menu
Command (? for help): w
Final checks complete. About to write GPT data. THIS WILL OVERWRITE EXISTING
PARTITIONS!!
Do you want to proceed? (Y/N): Y
OK; writing new GUID partition table (GPT) to /dev/sdc.
Unable to save backup partition table! Perhaps the 'e' option on the experts'
menu will resolve this problem.
Warning! An error was reported when writing the partition table! This error
MIGHT be harmless, or the disk might be damaged! Checking it is advisable.
Command (? for help): o
This option deletes all partitions and creates a new protective MBR.
Proceed? (Y/N): Y
Command (? for help): p
Disk /dev/sdc: 5860533168 sectors, 2.7 TiB
Logical sector size: 512 bytes
Disk identifier (GUID): 3995C753-D73D-4386-8818-3A9AF06E3B2C
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 5860533134
Partitions will be aligned on 2048-sector boundaries
Total free space is 5860533101 sectors (2.7 TiB)
Number Start (sector) End (sector) Size Code Name
Command (? for help): o
This option deletes all partitions and creates a new protective MBR.
Proceed? (Y/N): Y
Command (? for help): w
Final checks complete. About to write GPT data. THIS WILL OVERWRITE EXISTING
PARTITIONS!!
Do you want to proceed? (Y/N): Y
OK; writing new GUID partition table (GPT) to /dev/sdc.
Unable to save backup partition table! Perhaps the 'e' option on the experts'
menu will resolve this problem.
Warning! An error was reported when writing the partition table! This error
MIGHT be harmless, or the disk might be damaged! Checking it is advisable.
Command (? for help): p
Disk /dev/sdc: 5860533168 sectors, 2.7 TiB
Logical sector size: 512 bytes
Disk identifier (GUID): F1AE4B7D-9CCE-4211-BE3D-88DFFCCD3696
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 5860533134
Partitions will be aligned on 2048-sector boundaries
Total free space is 5860533101 sectors (2.7 TiB)
Number Start (sector) End (sector) Size Code Name
Command (? for help): o
This option deletes all partitions and creates a new protective MBR.
Proceed? (Y/N): n
Command (? for help): ?
b back up GPT data to a file
c change a partition's name
d delete a partition
i show detailed information on a partition
l list known partition types
n add a new partition
o create a new empty GUID partition table (GPT)
p print the partition table
q quit without saving changes
r recovery and transformation options (experts only)
s sort partitions
t change a partition's type code
v verify disk
w write table to disk and exit
x extra functionality (experts only)
? print this menu
Command (? for help): d
No partitions
Command (? for help): i
No partitions
Command (? for help): r
Recovery/transformation command (? for help): ?
b use backup GPT header (rebuilding main)
c load backup partition table from disk (rebuilding main)
d use main GPT header (rebuilding backup)
e load main partition table from disk (rebuilding backup)
f load MBR and build fresh GPT from it
g convert GPT into MBR and exit
h make hybrid MBR
i show detailed information on a partition
l load partition data from a backup file
m return to main menu
o print protective MBR data
p print the partition table
q quit without saving changes
t transform BSD disklabel partition
v verify disk
w write table to disk and exit
x extra functionality (experts only)
? print this menu
Recovery/transformation command (? for help): f
Warning! This will destroy the currently defined partitions! Proceed? (Y/N): Y
Problem loading MBR! GPT is untouched; regenerating protective MBR!
Recovery/transformation command (? for help): ?
b use backup GPT header (rebuilding main)
c load backup partition table from disk (rebuilding main)
d use main GPT header (rebuilding backup)
e load main partition table from disk (rebuilding backup)
f load MBR and build fresh GPT from it
g convert GPT into MBR and exit
h make hybrid MBR
i show detailed information on a partition
l load partition data from a backup file
m return to main menu
o print protective MBR data
p print the partition table
q quit without saving changes
t transform BSD disklabel partition
v verify disk
w write table to disk and exit
x extra functionality (experts only)
? print this menu
Recovery/transformation command (? for help): v
No problems found. 5860533101 free sectors (2.7 TiB) available in 1
segments, the largest of which is 5860533101 (2.7 TiB) in size.
Recovery/transformation command (? for help): b
Recovery/transformation command (? for help): c
Warning! This will probably do weird things if you've converted an MBR to
GPT form and haven't yet saved the GPT! Proceed? (Y/N): Y
Warning! Read error 5! Misbehavior now likely!
Caution! After loading partitions, the CRC doesn't check out!
Recovery/transformation command (? for help): w
Warning! Main partition table overlaps the first partition by 34 blocks!
You will need to delete this partition or resize it in another utility.
Aborting write of new partition table.
No matter what I try to do, I seem to get the input/output error, I tried installing Ubuntu on it, and it seems to create the partition table, but when I start the install — input/output error.
Anyone have any idea on how I can fix this? I’m happy to post more logfiles or whatever, but I’m not experienced with Linux, I just use it for this kind of stuff. The disk is very new, just some months, so I doubt it’s any bad sectors.
Apprentice
Joined: 05 Jan 2007
Posts: 161
Location: Deeper Underground
|
||||
|
||||
Hi folks This evening I discovered a really annoying error on my gentoo box. I tried to resize the partition gentoo is installed on to the «left side» using gparted live-cd. But suddenly gparted stopped an gave me the message «input/output error during read». Following partition scheme: Gentoo is installed on /dev/hda8, between hda7 and hda8 I freed up 3 gigs with a properly working resize of partition 6+7. This worked fine but not the resizing of hda8.
First question: Second: Is it possible to find out the file, delete it and voila: gparted works fine? Gparted error log says:
third: Thanks for your help. |
Apprentice
Joined: 05 Jan 2007
Posts: 161
Location: Deeper Underground
|
||
|
||
I solved my first question, while doing
It found 5 bad blocks which could be repaired or whatever. But I still have no answer to question no. 2 and no. 3. |
Display posts from previous:
Forum rules
There are no such things as «stupid» questions. However if you think your question is a bit stupid, then this is the right place for you to post it. Please stick to easy to-the-point questions that you feel people can answer fast. For long and complicated questions prefer the other forums within the support section.
Before you post please read how to get help. Topics in this forum are automatically closed 6 months after creation.
-
ClutchDisc
Input/output error on 2nd HDD [SOLVED]
Hey guys, I am having an issue with a second HDD that I was thinking of either adding to my desktop or making an external drive out of. It’s a 500 GB that came out of my laptop when I upgraded to a SSD. This laptop originally had Ubuntu 14.04 installed on it, and I tried to reformat it to be a data backup disk, but it won’t go past being unallocated. When I try to open Gparted (from a live mint usb) I get this error message: «Error fsyncing/closing /dev/sda:Input/output error»
Any ideas of what to try next? If you need more info than I have given, let me know!
Thanks!
Last edited by LockBot on Wed Dec 28, 2022 7:16 am, edited 2 times in total.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
-
kyphi
- Level 9
- Posts: 2732
- Joined: Sat Jul 09, 2011 1:14 am
- Location: The Hunter Valley, Australia
Re: Input/output error on 2nd HDD
Post
by kyphi » Sat Dec 27, 2014 8:13 pm
There are a lot of entries on the web regarding this issue but there does not seem to be a definitive solution other than to click on «Retry» repeatedly when it is suddenly supposed to work.
Sounds very unscientific, doesn’t it.
It may be of benefit to hook it up to one of your existing computers to see if it registers as an extra drive.
Also consider assuming ownership and resetting permissions:
Code: Select all
sudo chown ClutchDisc:ClutchDisc -R /media/disk
and
Linux Mint 21.1 Cinnamon
-
coffee412
- Level 6
- Posts: 1356
- Joined: Mon Nov 12, 2012 7:38 pm
- Location: I dont know
- Contact:
Re: Input/output error on 2nd HDD
Post
by coffee412 » Sat Dec 27, 2014 9:42 pm
If you can get the drive slaved in on a computer and get mint up and running then please run «disks» and select the smart tests to make sure the drive is ok. You will find ‘disks’ in the accessories menu.
Stranger things have happened and you can swear the drive is fine but when tested you find problems. Also check the cable to the drive.
Just be sure thats all Iam saying.
coffee
Ryzen x1800 Asus Prime x370-Pro 32 gigs Ram RX480 graphics
Dell PE T610, Dell PE T710
MeshCentral * Virtualbox * Debian * InvoiceNinja * NextCloud * Linux since kernel 2.0.36
-
austin.texas
- Level 20
- Posts: 12003
- Joined: Tue Nov 17, 2009 3:57 pm
- Location: at /home
Re: Input/output error on 2nd HDD
Post
by austin.texas » Sun Dec 28, 2014 12:04 am
You said you are «thinking of» adding it to your desktop or making it an external drive. But you didn’t say how it is installed now. Is it still in the laptop?
When I hear «I/O error» I suspect a USB connection. Sometimes on older machines it could be slow IDE connections, also.
Mint 18.2 Cinnamon, Quad core AMD A8-3870 with Radeon HD Graphics 6550D, 8GB DDR3, Ralink RT2561/RT61 802.11g PCI
Linux Linx 2018
-
ClutchDisc
Re: Input/output error on 2nd HDD
Post
by ClutchDisc » Sun Dec 28, 2014 1:27 am
Hi guys, thanks for the help so far! I will try to answer some questions:
1. I did it from a live USB because I had it in an older laptop that I don’t use, that’s all!
2. kyphi: I tried running the commands that you gave, but I got a «No such file or directory» error. Did I do something wrong, I changed the username to the correct one for my computer, left everything else the same.
3. Doesn’t even give me the option to run a smart test on the HDD…
4. The HDD is now in the Dell in my signature as a second HDD. It is giving me the same error message as before, see below.
Here are some screenshots that I hope help!
- Attachments
-
-
-
-
ClutchDisc
Re: Input/output error on 2nd HDD
Post
by ClutchDisc » Mon Dec 29, 2014 12:11 am
This is solved!! I remembered that I had set a password on the HDD a while back when it was in my laptop, so I put it back in the laptop, turned the password off in the setup menu, and it works now!!