Cat input output error

Thread: cat input / output error

Thread Tools

Display

cat input / output error

Hi-
I’m attempting to migrate my Windows 7 NTFS installation to a VirtualBox machine according to this guide:

but every time I try, cat crashes with an input / output error at exactly 28.3GB / 50GB of my Windows partition.
I know I have an old hard drive with some bad sectors, but so far chkdsk from the Windows Recovery Console fails to run on boot when I ask it to.
As far as I know, ntfsprogs reports no problems but a chkdsk scan from Windows still tells me about bad sectors.
I have a suspicion that cat is crashing because it’s running into some of these bad sectors, but I could also be totally off on a wild goose chase.
I would be very grateful if anyone here could shed some light on this problem or point me in the right direction.
Thanks in advance

Re: cat input / output error

Hi-
I’m attempting to migrate my Windows 7 NTFS installation to a VirtualBox machine according to this guide:

but every time I try, cat crashes with an input / output error at exactly 28.3GB / 50GB of my Windows partition.
I know I have an old hard drive with some bad sectors, but so far chkdsk from the Windows Recovery Console fails to run on boot when I ask it to.
As far as I know, ntfsprogs reports no problems but a chkdsk scan from Windows still tells me about bad sectors.
I have a suspicion that cat is crashing because it’s running into some of these bad sectors, but I could also be totally off on a wild goose chase.
I would be very grateful if anyone here could shed some light on this problem or point me in the right direction.
Thanks in advance

Don’t use cat because it will stop on any bad blocks, try using dd instead set to ignore errors:

Источник

Arch Linux

You are not logged in.

#1 2021-10-22 15:57:30

BTRFS: broken unexpectedly. Copy/cat/rsync Input/output error. Really?

I use btrfs since 2018. Now my version is btrfs-progs 5.14.2-1

Suddenly and by accident I discovered bug during copy:

I thought — this is the number!

I never see such behavour with ZFS!

Wow! my data is in danger!

Ohh! How does it add numbers like that?

Wow! But these are other files!

Hangs! Absolute freeze! Reboot. It makes me crazy! SOS!

(very long time here)

The number of bugs has increased wildly!

7 errors at final! 7 files lost. 7 Log records:

As a result I feel like an idiot with BTRFS.

Where is my 7 files? What can I do to restore data?

5 working days in the ass (5 dney v zhopu) — its’ a hellish unstable!

Last edited by SunDoctor (2021-10-26 08:47:50)

#2 2021-10-22 16:14:28

Re: BTRFS: broken unexpectedly. Copy/cat/rsync Input/output error. Really?

Please update your post and use code tags for commands and outputs. Also please update your title, the «really?» phrase adds no value and may cause people to ignore your post.

As for your problem: can you post the output of smartctl? Maybe there’s warnings that some folks here can interpret, even if there are no errors reported. It could still be hardware failure.

Where is my 7 files? What can I do to restore data?

As the famous saying goes: «there are two kinds of people: those that plan to make backups and those that make backups».

#3 2021-10-22 16:25:31

Re: BTRFS: broken unexpectedly. Copy/cat/rsync Input/output error. Really?

3 disks. Simple raid5. Where is the reliability of the data with raid?
Why BTRFS works silently — it writes and reads without any notification of corruption?
The very first file «/data/SDK/x64/setup.zip» was written a week ago.

Offtopic: I hate Seagate.

Offtopic2: in that case ZFS would have ruined RAID5 long ago (stopping writes and saves data), but not BTRFS

Last edited by SunDoctor (2021-10-22 16:45:32)

#4 2021-10-22 17:17:26

Re: BTRFS: broken unexpectedly. Copy/cat/rsync Input/output error. Really?

One importance notice:

I remount btrfs «/data» filesystem in readonly mode straight after scrub and start recover.

But after rsync/copy check error counters have increased dramatically.

Besides «btrfs restore» and «rsync» give me different results — rsync found many files not restored at «/usbdisk»

I think btrfs distorts the real situation, incorrectly overwrites data with deliberately destroyed checksums and it is not clear what it displays in my case.

I also have an error with metadata: the definition of raid5-metadata was not optimal:

But this should not affect the integrity of the raid5

Last edited by SunDoctor (2021-10-22 17:20:46)

#5 2021-10-22 17:36:58

Re: BTRFS: broken unexpectedly. Copy/cat/rsync Input/output error. Really?

The official info (may be until v4.12 — 4.14)

Currently raid5 and raid6 profiles have flaws that make it strongly not recommended as per the Status page.
In less recent releases the parity of resynchronized blocks was not calculated correctly, this has been fixed in recent releases (TBD).
If a crash happens while a raid5/raid6 volume is being written this can result in a «transid» mismatch as in transid verify failed.
The resulting corruption cannot be currently fixed.

Some fixes went to 4.12, namely scrub and auto-repair fixes. Feature marked as mostly OK for now.
Further fixes to raid56 related code are applied each release. The write hole is the last missing part, preliminary patches have been posted but needed to be reworked. The parity not checksummed note has been removed.

You should not show anyone a product that is losing data! Any such features should not go beyond the testing development branches!

Last edited by SunDoctor (2021-10-26 08:44:44)

#6 2021-10-22 18:16:56

Re: BTRFS: broken unexpectedly. Copy/cat/rsync Input/output error. Really?

found 2323713069056 bytes used, no error found

BTRFS is fully hairy at the heel!

Last edited by SunDoctor (2021-10-22 18:43:11)

#7 2021-10-25 14:40:31

Re: BTRFS: broken unexpectedly. Copy/cat/rsync Input/output error. Really?

For two days now I have seen the results of

Something is moving

But to be honest, the entire disc was copied in a day. Why it slows down for two days is a mystery.

In my soul only the worst words about my btrfs.

Last edited by SunDoctor (2021-10-25 14:41:53)

#8 2021-10-26 08:40:42

Re: BTRFS: broken unexpectedly. Copy/cat/rsync Input/output error. Really?

Some important analytics about btrfs from WWW:

In my case the array was not degraded and it continued to operate in the «rw» mode with an increasing number of errors.

I continue to observe, trying to rectify the situation with btrfs methods, without resorting to formatting.
Although I am sure that formatting and writing the captured information in place would be much faster.

Last edited by SunDoctor (2021-10-26 08:42:09)

#9 2021-10-26 09:46:05

Re: BTRFS: broken unexpectedly. Copy/cat/rsync Input/output error. Really?

Almost 3 days are useless:

It seems like the errors were corrected. But not.

Nothing is changed since the very beginning.

Apparently, I am forced to format the disks and create the array anew on old disks.

#10 2021-10-28 18:45:29

Re: BTRFS: broken unexpectedly. Copy/cat/rsync Input/output error. Really?

I am happy to report: the very first source of this entire wildest situation has been found!

Reason for everything: memory fault (memtest86, test: 7,8) high address

So, there was a crash in the fourth memory bank in the upper memory addresses. It did not manifest itself at all when its memory was at least a little free. But when I filled up all the memory with virtual machines, then, by chance and very sometimes, there were rare write errors that btrfs swallowed without hesitation.

This garbage was found on a new blank disk with btrfs just at the moment when I once again occupied all the memory with applications, wrote one huge file (50GB) and checked it for reading (and received an «Input/Output error»).

I note that btrfs seriously confused me with its «indicators», and, in general, added fuel to the fire: its behavior was not ideal. But all the information at the moment is intact, and now, finally, I’m starting to put it back in place!

I spent two weeks of my life studying the behavior of btrfs, but now I am even proud that I know it as my girlfriend

Finally, if you are really interested in the attitude of professionals to the BTRFS — translate and read the latest article by Eduard Shishkin (RaiserFS) (from Russian to English):

The worst thing is that an unprivileged user can almost always deprive everyone of free space in a fairly short time, bypassing any disk quotas. It looks like this (tested for Linux kernel 5.12). On a freshly installed system, a script is launched that, in a loop, creates files with certain names in the home directory, writes data to them at certain offsets, and then deletes these files. After a minute of this script, nothing unusual happens. After five minutes, the portion of the occupied space on the section increases slightly. After two to three hours, it reaches 50% (with an initial value of 15%). And after five to six hours of work, the script crashes with the error «there is no free space on the partition.»
.
How do I position Btrfs for myself? As something that categorically cannot be called a file system, let alone use. For, by definition, FS is an OS subsystem responsible for efficient management of the «disk space» resource, which we do not see in the case of Btrfs.
.
Btrfs was they(=RHEL) only had a «technology preview». So, this very «preview» has not passed. And they cannot launch a flawed by-design product with full support. RHEL is an enterprise, that is, a prescribed commodity-money relationship. Red Hat cannot mock users like it does on the Btrfs mailing list.

Last edited by SunDoctor (2021-10-29 08:04:18)

Источник

cat: rom: Input/output error #4

Hi,It’s seems didn’t work on proxmox 5.4-11
platform：
cpu:i7-3820qm
chipset:hm77
GPU:NVIDIA Corporation GF108M [GeForce GT 635M]

# cd /sys/bus/pci/devices/0000:01:00.0/
root@nserver:/sys/bus/pci/devices/0000:01:00.0# echo 1 > rom
root@nserver:/sys/bus/pci/devices/0000:01:00.0# cat rom > /tmp/image.rom
cat: rom: Input/output error

dmesg:
vfio-pci 0000:01:00.0: Invalid PCI ROM header signature: expecting 0xaa55, got 0xffff

The text was updated successfully, but these errors were encountered:

I have run into the same problem (as i have a optimus laptop too by looking at your spec).

Basically, some dgpu in optimus laptop don’t have the rom loaded from the gpu directly (afaik most desktop gpu do the reverse here) or just don’t have enough permissions to do it, or even because the gpu is still in use (aka most optimus gpu don’t support hotswapping); afaik that’s all the reason i can think of but i could be wrong.
But fortunately, there is still ways to get the rom of the gpu:

• On windows, the rom is loaded as a .reg file in the registry, so you can get it there (more info here)
• You can use either vbiosfinder or romparser on the update/dump of your bios (romparser is already included in vbiosfinder btw).which you can usually find on the manufacturer site or if normal dumping tools support your bios already.
• If the above doesn’t work (which would surprise me, but just in case), you can use binwalk on each file from the bios dump until you see something akin to «manufacturer’s name» or «gpu vendor» or anything similar.

I have some problem with some older cards, especially ATI ones.. On normal desktop PC.

Источник

Thread: Input/output error on ‘cat’?

Thread Tools

Display

Input/output error on ‘cat’?

I just installed Fedora 3 core and am running into a problem. On many system binaries (not all) I am getting ‘Input/output error’.

[root@athena etc]# vim inittab
-bash: /usr/bin/vim: Input/output error
[root@athena etc]# find / -name vim -print
/usr/bin/vim
/usr/share/vim
[root@athena etc]# echo $PATH
/bin:/usr/kerberos/sbin:/usr/kerberos/bin:/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/usr/X11R6/bin:/root/bin
[root@athena etc]# cat inittab
cat: inittab: Input/output error
[root@athena etc]# find / -name cat -print
/bin/cat

You could try supplying the complete path to your objective, such as «cat /etc/inittab». if I’m reading you right.

Yeah, that doesn’t do it. A lot of commands (not all) are doing it. Weirdest thing.

[root@athena bin]# ls *sh
ash bash bsh csh ksh sh tcsh zsh
[root@athena bin]# ./ksh
-bash: ./ksh: Input/output error
[root@athena bin]# ./sh
sh-3.00# file ksh
sh: /usr/bin/file: Input/output error
sh-3.00# ping localhost
sh: /bin/ping: Input/output error
sh-3.00# cat /etc/inittab
cat: /etc/inittab: Input/output error
sh-3.00# ls /root
anaconda-ks.cfg install.log install.log.syslog
sh-3.00# cat /root/install.log
cat: /root/install.log: Input/output error
sh-3.00# cd
sh-3.00# ls -a
. .bashrc .gnome2 install.log.syslog
.. .cshrc .gnome2_private .tcshrc
anaconda-ks.cfg .gconf .gstreamer-0.8 .Xauthority
.bash_logout .gconfd .gtkrc
.bash_profile .gnome install.log
sh-3.00# cat .bash_logout
cat: .bash_logout: Input/output error
sh-3.00# cat ./.bash_logout
cat: ./.bash_logout: Input/output error
sh-3.00# cat .bash_profile
# .bash_profile

# Get the aliases and functions
if [ -f

# User specific environment and startup programs

export PATH
unset USERNAME
sh-3.00#

Источник

Thread: ‘Input/output error’ on serial port

Thread Tools

Display

‘Input/output error’ on serial port

The objective is to calibrate my monitor (connected via VGA) with the colorimeter X-Rite Colormunki Display connected via usb.
The device is recognized :

my environment:
Sony Vaio SVE14A2C5E
Ubuntu 12.04 (precise) 64-bit
Kernel Linux 3.5.0-44-generic
GNOME 3.4.2

Some weeks ago, I had windows 8 on this laptop without problem with the calibrator and Argyll.
I spent my last days reading the numerous topics about it without success.

I show you the outputs of some command lines:

The problem seems to come from the UART: unknown. So I tried to do:

After a reboot UART is unknown again.

and the device is still not working.

The command below changes apparently nothing.

In the Serial port setup menu I get:
| A — Serial Device : /dev/tty8
| B — Lockfile Location : /var/lock
| C — Callin Program :
| D — Callout Program :
| E — Bps/Par/Bits : 115200 8N1
| F — Hardware Flow Control : Yes
| G — Software Flow Control : No

I changed tty8 by ttyS0 but it changes nothing
In some discussions the users where modifying some files system, but as I do not understand well what they are doing and if it is appropriate to my case, I prefer to stop here and wait for your advises.

Thank you very much for you help.

Last edited by hadrien15; December 29th, 2013 at 09:23 PM .

Re: ‘Input/output error’ on serial port

I don’t have any experience with these devices but the most likely issue would seem to be that it’s not actually connecting on /dev/ttyS0 surely?

AFAIK real-time udev messages go to /var/log/syslog rather than /var/log/dmesg, so I’d suggest running

in a terminal and then plugging the device in — you should see exactly what tty file it is attaching to — if it’s connecting via /dev/ttyUSBn for example but the software insists on using /dev/ttySn then it may be a question of providing a udev rule to create the desired symlink

Last edited by steeldriver; December 29th, 2013 at 10:08 PM .

Источник

1

1

# cat /data/work/2021Q3.txt > /dev/null
cat: /data/work/2021Q3.txt: Input/output Error

[/dev/sdd].corruption_errs  6
[/dev/sdf].corruption_errs  22

btrfs balance start -mconvert=raid1 -sconvert=raid1 /data

Hi!

I use btrfs since 2018. Now my version is btrfs-progs 5.14.2-1

Suddenly and by accident I discovered bug during copy:

rsync: [sender] read errors mapping "/data/SDK/x64/setup.zip": Input/output error

I thought — this is the number!

# btrfs device usage /data

/dev/sdd, ID: 1
   Device size:             2.73TiB
   Device slack:              0.00B
   Data,RAID5/3:            1.06TiB
   Metadata,RAID5/3:        3.00GiB
   System,RAID5/3:          8.00MiB
   Unallocated:             1.67TiB

/dev/sde, ID: 2
   Device size:             2.73TiB
   Device slack:              0.00B
   Data,RAID5/3:            1.06TiB
   Metadata,RAID5/3:        3.00GiB
   System,RAID5/3:          8.00MiB
   Unallocated:             1.67TiB

/dev/sdf, ID: 3
   Device size:             2.73TiB
   Device slack:              0.00B
   Data,RAID5/3:            1.06TiB
   Metadata,RAID5/3:        3.00GiB
   System,RAID5/3:          8.00MiB
   Unallocated:             1.67TiB

I never see such behavour with ZFS!

# btrfs device stat /data

[/dev/sdd].write_io_errs    0
[/dev/sdd].read_io_errs     0
[/dev/sdd].flush_io_errs    0
[/dev/sdd].corruption_errs  6
[/dev/sdd].generation_errs  0
[/dev/sde].write_io_errs    0
[/dev/sde].read_io_errs     0
[/dev/sde].flush_io_errs    0
[/dev/sde].corruption_errs  0
[/dev/sde].generation_errs  0
[/dev/sdf].write_io_errs    0
[/dev/sdf].read_io_errs     0
[/dev/sdf].flush_io_errs    0
[/dev/sdf].corruption_errs  22
[/dev/sdf].generation_errs  0

Wow! my data is in danger!

# btrfs scrub start -Bdr /data

  Corrected:      1
  Uncorrectable:  1
  Unverified:     0

  Error summary:    no errors found

  Corrected:      0
  Uncorrectable:  17
  Unverified:     1

ERROR: there are uncorrectable errors

Ohh! How does it add numbers like that?

# btrfs check --check-data-csum -p /dev/disk/by-label/RAID5

# journalctl --dmesg --grep 'checksum error'

kernel: BTRFS warning (device sdd): checksum error at logical 1081319096320
kernel: BTRFS warning (device sdd): checksum error at logical 1522947457024

# btrfs inspect-internal logical-resolve 1081319096320 /data
# btrfs inspect-internal logical-resolve 1522947457024 /data

/data/VIDEO_TS/VTS_16_1.VO
/data/00000000000000059072.xml

Wow! But these are other files!

# btrfs rescue chunk-recover /dev/by-label/RAID5

Hangs! Absolute freeze! Reboot… It makes me crazy! SOS!

# smartctl -t long /dev/sdd ; smartctl -t long /dev/sde ; smartctl -t long /dev/sdf

No errors! What?!!

# btrfs restore by-label/RAID5 /mnt/usbdisk

(very long time here)

# btrfs device stats /data

[/dev/sdd].write_io_errs    0
[/dev/sdd].read_io_errs     0
[/dev/sdd].flush_io_errs    0
[/dev/sdd].corruption_errs  90
[/dev/sdd].generation_errs  0
[/dev/sde].write_io_errs    0
[/dev/sde].read_io_errs     0
[/dev/sde].flush_io_errs    0
[/dev/sde].corruption_errs  165
[/dev/sde].generation_errs  0
[/dev/sdf].write_io_errs    0
[/dev/sdf].read_io_errs     0
[/dev/sdf].flush_io_errs    0
[/dev/sdf].corruption_errs  202
[/dev/sdf].generation_errs  0

The number of bugs has increased wildly!

# rsync --dry-run -ri --delete --checksum /data/ /mnt/usbdisk/ 2>&1 | tee rsync.log

# cat rsync.log  | grep -v skipping | grep ERROR | nl

7 errors at final! 7 files lost. 7 Log records:

1	ERROR: 1tb/work/2021Q3.txt failed verification -- update discarded
...

As a result I feel like an idiot with BTRFS.

Where is my 7 files? What can I do to restore data?

5 working days in the ass (5 dney v zhopu) — its’ a hellish unstable!

Last edited by SunDoctor (2021-10-26 08:47:50)