Blk update request io error dev sr0

Hello,
  • Index
  • » Installation
  • » Installation problems: I/O erro: dev sr0

#1 2015-04-07 14:47:18

r3b3l
Member
Registered: 2015-04-07
Posts: 3

Installation problems: I/O erro: dev sr0

Hello,

last week I wanted to reinstall Arch on my Laptop (Lenovo Ideapad G580). First I’ve downloaded the ISO and burned the Live CD.
After I choose ‘Boot Arch Linux (x86_64)’ I got this:

Probing EDD (edd=off to disable)... ok
early console in decompress_kernel

Decompressing Linux... Parsing ELF... done.
Booting the kernel.
:: running early hook [udev]
starting version 218
:: running hook [udev]
:: Triggering unevents...
error: /dev/sdb: No medium found
error: /dev/sdb: No medium found
[	10.004186] blk_update_request: I/O erro, dev sr0, sector 1226752
[	15.950463] blk_update_request: I/O erro, dev sr0, sector 1226752
[	15.950553] Buffer I/O error on dev sr0, logical block 153344, async page read
[	22.443844] blk_update_request: I/O erro, dev sr0, sector 1226752
[	28.330003] blk_update_request: I/O erro, dev sr0, sector 1226752
[	28.330094] Buffer I/O error on dev sr0, logical block 153344, async page read
:: running hook [memdisk]
:: running hook [archiso]
:: running hook [archiso_loop mnt]
:: running hook [archiso_pxe_common]
:: running hook [archiso_pxe_nbd]
:: running hook [archiso_pxe_http]
:: running hook [archiso_pxe_nfs]
:: Mounting '/dev/disk/by-label/ARCH_201504' to '/run/archiso/bootmnt'
Waiting 30 seconds for device /dev/disk/by-label/ARCH_201504 ...
ERROR: '/dev/disk/by-label/ARCH_201504' device did not show up after 30 seconds...
	Falling back to interactive prompt
	You can try to fix the problem manually, log out when you are finished
sh: can't access tty; job contorl turned off
[rootfs /]#

I burned the CD two times and tried it, on a friends laptop. It worked. But my PC doesn’t want to install it.
Now I have Lubuntu on my Laptop hmm
Pls help

r3b3l

Last edited by jasonwryan (2015-04-07 17:04:40)

#2 2015-04-07 15:00:39

satanselbow
Member
Registered: 2011-06-15
Posts: 538

Re: Installation problems: I/O erro: dev sr0

Did you check the hash sums of the Arch ISO?

How did you prepare / what medium did you use to install Lubuntu?

#3 2015-04-07 15:06:04

ewaller
Administrator
From: Pasadena, CA
Registered: 2009-07-13
Posts: 19,010

Re: Installation problems: I/O erro: dev sr0

I am a bit concerned about those I/O errors.   You say the same CD works on your friends machine?
What media are you using?  You might try a CD-R instead of a CD+R or a CD RW.  Avoid DVD media all together.

Is booting from USB an option?  Is booting from PXE (network boot) an option?

Last edited by ewaller (2015-04-07 15:06:16)

Nothing is too wonderful to be true, if it be consistent with the laws of nature — Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. — Alan Turing
—
How to Ask Questions the Smart Way

#4 2015-04-07 15:49:43

dice
Member
From: Germany
Registered: 2014-02-10
Posts: 413

Re: Installation problems: I/O erro: dev sr0

There is a similar thread about this. (https://bbs.archlinux.org/viewtopic.php … 3#p1516893
I’m wondering if there is a wider problem to this. As the I/O errors appear on exactly the same sectors I doubt that two people have exactly the same CD or CD-Drive with exactly the same error. This would be rather unlikely.
Or is there another explanation for this?

I put at button on it. Yes. I wish to press it, but I’m not sure what will happen if I do.  (Gune | Titan A.E.)

#5 2015-04-07 16:28:15

r3b3l
Member
Registered: 2015-04-07
Posts: 3

Re: Installation problems: I/O erro: dev sr0

Thank you for the answers. The hash sums are ok. I’d install Lubuntu from USB, but I didn’t tried it with Arch, because I had a few Problems when I tried it the first time and so I installed it with the CD. The CD I used a year before (when it worked) and the CD I used this time are identical. The CD from the first install, doesn’t work anymore, too >.<
I will try to install debian from another live cd. Only for a try.
After that, I will try to install from USB. Perhaps it will work.

#6 2015-04-07 17:21:55

satanselbow
Member
Registered: 2011-06-15
Posts: 538

Re: Installation problems: I/O erro: dev sr0

r3b3l wrote:

I will try to install debian from another live cd. Only for a try.

Is this disk you will burn yourself or disc from the front of a magazine? (for example)

There are several possible scenarios going on which would be nice to resolve before it comes back to bite you later wink

1) CD drive faulty or failing
2) CD discs faulty, incompatible or inconsistent
3) ‘Current Arch ISO is failing to write correctly on some hardware/software combinations… unlikely as the board is not flooded with the error you are reporting but not impossible…

Would be nice to know as the other post linked above left quite a few questions unresolved sad

#7 2015-04-07 21:31:42

chorlton
Member
Registered: 2015-04-07
Posts: 2

Re: Installation problems: I/O erro: dev sr0

I’m having the same I/O Erro on exactly the same sector.

ISO md5sum was checked after download.
ISO was burned to a CD using Brasero
The disk is labeled ARCH_201504

Trying to install on a fairly standard HP laptop from the last 3 years.

So, looks like it could be option 3 in the previous post?

Last edited by chorlton (2015-04-07 21:34:09)

#8 2015-04-07 23:00:34

arco
Member
Registered: 2015-04-07
Posts: 1

Re: Installation problems: I/O erro: dev sr0

I also had this I/O error yesterday. But for me it was sector 1227352

My steps were as follows:
1. Downloaded archlinux-2015.04.01-dual.iso
2. Verified MD5
3. Burned CD-R (with a verify after burning) selected x86_64 from the bootmenu and had these I/O errors on dev sr0.
4. Burned DVD-R and it worked fine.

#9 2015-04-07 23:07:41

dice
Member
From: Germany
Registered: 2014-02-10
Posts: 413

Re: Installation problems: I/O erro: dev sr0

To those who have the problem: Did you also check the md5 of the burnt cd?

I put at button on it. Yes. I wish to press it, but I’m not sure what will happen if I do.  (Gune | Titan A.E.)

#10 2015-04-08 07:33:35

r3b3l
Member
Registered: 2015-04-07
Posts: 3

Re: Installation problems: I/O erro: dev sr0

Thank you all for the answers and exspecially to arco. The burned DVD seems to work. I’ll install it friday completely and give reply

#11 2015-04-08 07:38:28

satanselbow
Member
Registered: 2011-06-15
Posts: 538

Re: Installation problems: I/O erro: dev sr0

arco wrote:

3. Burned CD-R (with a verify after burning) selected x86_64 from the bootmenu and had these I/O errors on dev sr0.
4. Burned DVD-R and it worked fine.

Which rather points the blame at the media/software/hardware/user tongue not the ISO itself.

#12 2015-04-13 18:10:31

ewaller
Administrator
From: Pasadena, CA
Registered: 2009-07-13
Posts: 19,010

Re: Installation problems: I/O erro: dev sr0

Update:  I encountered this myself this weekend.   I obtained a new laptop with Window 8.  After checking everything for proper operation, I downloaded and burned Arch to a CD-R from Windows 8 on my new machine.  When I tried to install using that disk, I encountered the exact same problem described here.  As a control, I tried a second disk.  Same thing.

Went to my old machine running Linux.  Downloaded and burned using Linux.  Moved the disk to the new machine and it worked perfectly.  Installed Arch on the new machine and then used the new machine to burn a disk using Arch Linux.  The disk worked just fine.

Looks like a Windows bug.  I’ll not be filing a bug report with Redmond.

Nothing is too wonderful to be true, if it be consistent with the laws of nature — Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. — Alan Turing
—
How to Ask Questions the Smart Way

#13 2015-04-13 19:32:55

juego
Member
Registered: 2015-04-13
Posts: 41
Website

Re: Installation problems: I/O erro: dev sr0

Having the same error.

Downloaded the archlinux-2015.04.01-dual.iso via torrent. Checked the MD5 sum. «burned» it on a brand new blank USB with Unetbootin.
Have gone over the process of formatting the USB twice and «buring» the iso on it with unetbootin twice. Same error.

#14 2015-04-13 19:52:17

Head_on_a_Stick
Member
From: London
Registered: 2014-02-20
Posts: 6,873
Website

Re: Installation problems: I/O erro: dev sr0

juego wrote:

Having the same error.

Downloaded the archlinux-2015.04.01-dual.iso via torrent. Checked the MD5 sum. «burned» it on a brand new blank USB with Unetbootin.
Have gone over the process of formatting the USB twice and «buring» the iso on it with unetbootin twice. Same error.

Your problem is different: the OP is referring to a CD/DVD whilst your situation involves a USB stick.

Try transferring the ISO image using the `dd` command (as per the Beginner’s Guide) rather than unetbootin
https://wiki.archlinux.org/index.php/US … NU.2FLinux

If it still won’t work you should open your own thread and link back to this one.

#15 2015-04-13 22:28:57

juego
Member
Registered: 2015-04-13
Posts: 41
Website

Re: Installation problems: I/O erro: dev sr0

Head_on_a_Stick wrote:

juego wrote:

Having the same error.

Downloaded the archlinux-2015.04.01-dual.iso via torrent. Checked the MD5 sum. «burned» it on a brand new blank USB with Unetbootin.
Have gone over the process of formatting the USB twice and «buring» the iso on it with unetbootin twice. Same error.

Your problem is different: the OP is referring to a CD/DVD whilst your situation involves a USB stick.

Try transferring the ISO image using the `dd` command (as per the Beginner’s Guide) rather than unetbootin
https://wiki.archlinux.org/index.php/US … NU.2FLinux

If it still won’t work you should open your own thread and link back to this one.

My bad. The `dd` command solved it. Thx and sorry for the trouble.

#16 2015-04-14 08:03:50

satanselbow
Member
Registered: 2011-06-15
Posts: 538

Re: Installation problems: I/O erro: dev sr0

ewaller wrote:

Looks like a Windows bug.  I’ll not be filing a bug report with Redmond.

Not unless the ArchISO is created on a windows box???????? At least one of the posts above mentions burning with Brasero… which has always been pretty random IMHO…

#17 2015-04-14 13:57:21

ewaller
Administrator
From: Pasadena, CA
Registered: 2009-07-13
Posts: 19,010

Re: Installation problems: I/O erro: dev sr0

You are right.  There were some postings to the mailing list about issues with Brasero as well.   I don’t understand what you mean by «Not unless the ArchISO is created on a windows box?»  What I am saying is that when I downloaded the binary and burned it using Windows 8’s intrinsic tools I encountered the problem.  When I used wodim on the same computer and drive, I was able to burn a usable disk.  My assumption is that I am not the only one who has tried to burn a disk using Windows — most desktop and laptop Linux machines are born-again Windows boxes.

Last edited by ewaller (2015-04-14 16:53:20)

Nothing is too wonderful to be true, if it be consistent with the laws of nature — Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. — Alan Turing
—
How to Ask Questions the Smart Way

#18 2015-04-14 14:24:43

DanielH
Member
From: Mar del Plata, Argentina
Registered: 2014-03-11
Posts: 28

Re: Installation problems: I/O erro: dev sr0

I see the same CD errors trying to use archlinux-2015.04.01-dual.iso to reinstall Arch in an old P4 (Celeron) machine:

…
[    …] blk_update_request: I/O erro, dev sr0, sector 1226752
[    …] blk_update_request: I/O erro, dev sr0, sector 1226752
[    …] Buffer I/O error on dev sr0, logical block 153344, async page read
…
ERROR: ‘/dev/disk/by-label/ARCH_201504’ device did not show up after 30 seconds…
    Falling back to interactive prompt
    You can try to fix the problem manually, log out when you are finished
sh: can’t access tty; job contorl turned off
[rootfs /]#
….

MD5 and SHA1 sums checked.
ISO burned in two CDs at different speeds via Brasero under LMDE: unable to boot from both disks.

BTW: archlinux-2015.03.01-dual.iso works fine for me…
Booting from 2015.03.01-dual.iso, I’m able to arch-chroot in the previously installed Arch and perform commands as root (including full update).

Seemed to be a bug in archlinux-2015.04.01 ISO creation.

Any suggestion?
DanielH

P.S. forgive my bad english, I’m argentinian and only speak spanish.

#19 2015-04-14 15:28:39

DanielH
Member
From: Mar del Plata, Argentina
Registered: 2014-03-11
Posts: 28

Re: Installation problems: I/O erro: dev sr0

EDIT:

@ewaller: you’re right!

It’s a Brasero related bug sad
Using wodim (command line) to burn archlinux-2015.04.01-dual.iso makes a fully bootable CD big_smile

Best regards,
DanielH

#20 2015-05-02 17:07:33

jspicoli
Member
Registered: 2008-06-19
Posts: 10

Re: Installation problems: I/O erro: dev sr0

+1 for using wodim.  Brasero failed for me.

#21 2015-10-14 11:26:56

stefanwilkens
Member
From: Enschede, the Netherlands
Registered: 2008-12-10
Posts: 624

Re: Installation problems: I/O erro: dev sr0

Hi, sorry for bumping this relatively old topic but I’m running into the same issues on two separate machines.

ISO: archlinux-2015.10.01-dual
HASH: MD5 verified
Burn application: https://cdburnerxp.se/en/home (using data verification mode)

I’ve burnt the disc twice to make sure the disc itself wasn’t to blame.

The I/O error occurs on the same sector between both discs on both machines!

To me this indicates a burn / media issue, but data verification completed perfectly?

Dumping the exact same image to USB and booting off that throws no issues.

Inserting the CD in a booted live environment instantly throws the same I/O error. Inserting some other burned discs also result in I/O errors, though not all. Non-burned media seems allright.

relevant section of dmesg:

[    4.706282] ata1.00: Enabling discard_zeroes_data
[    4.709180]  sda: sda1 sda2 sda3 sda4 sda5 sda6
[    4.709696] sr 2:0:0:0: [sr0] scsi3-mmc drive: 24x/24x writer dvd-ram cd/rw xa/form2 cdda tray
[    4.709797] cdrom: Uniform CD-ROM driver Revision: 3.20
[    4.709848] ata1.00: Enabling discard_zeroes_data
[    4.709923] sd 0:0:0:0: [sda] Attached SCSI disk
[    4.719106] sr 2:0:0:0: Attached scsi CD-ROM sr0
[    5.134969] clocksource: Switched to clocksource tsc
[    5.595642] sr 2:0:0:0: [sr0] tag#22 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
[    5.598555] sr 2:0:0:0: [sr0] tag#22 Sense Key : 0x5 [current] 
[    5.601424] sr 2:0:0:0: [sr0] tag#22 ASC=0x26 ASCQ=0x0 
[    5.604279] sr 2:0:0:0: [sr0] tag#22 CDB: opcode=0x28 28 00 00 05 24 00 00 00 02 00
[    5.607160] blk_update_request: I/O error, dev sr0, sector 1347584
[    5.852635] sr 2:0:0:0: [sr0] tag#23 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
[    5.855586] sr 2:0:0:0: [sr0] tag#23 Sense Key : 0x5 [current] 
[    5.858498] sr 2:0:0:0: [sr0] tag#23 ASC=0x26 ASCQ=0x0 
[    5.861372] sr 2:0:0:0: [sr0] tag#23 CDB: opcode=0x28 28 00 00 05 24 00 00 00 02 00
[    5.864256] blk_update_request: I/O error, dev sr0, sector 1347584
[    5.866928] Buffer I/O error on dev sr0, logical block 168448, async page read
[    6.820286] sr 2:0:0:0: [sr0] tag#2 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
[    6.823220] sr 2:0:0:0: [sr0] tag#2 Sense Key : 0x5 [current] 
[    6.826112] sr 2:0:0:0: [sr0] tag#2 ASC=0x26 ASCQ=0x0 
[    6.828962] sr 2:0:0:0: [sr0] tag#2 CDB: opcode=0x28 28 00 00 05 24 00 00 00 02 00
[    6.831827] blk_update_request: I/O error, dev sr0, sector 1347584
[    8.037382] sr 2:0:0:0: [sr0] tag#3 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
[    8.040309] sr 2:0:0:0: [sr0] tag#3 Sense Key : 0x5 [current] 
[    8.043173] sr 2:0:0:0: [sr0] tag#3 ASC=0x26 ASCQ=0x0 
[    8.046010] sr 2:0:0:0: [sr0] tag#3 CDB: opcode=0x28 28 00 00 05 24 00 00 00 02 00
[    8.048862] blk_update_request: I/O error, dev sr0, sector 1347584
[    8.051504] Buffer I/O error on dev sr0, logical block 168448, async page read
[    8.393510] ACPI Warning: _SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150619/nsarguments-95)
[    8.396555] ACPI: _SB_.PCI0.PEG0.PEGP: failed to evaluate _DSM
[    8.399427] ACPI Warning: _SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150619/nsarguments-95)
[  219.655557] random: nonblocking pool is initialized

Arch i686 on Phenom X4 | GTX760

#22 2015-10-14 12:06:47

stefanwilkens
Member
From: Enschede, the Netherlands
Registered: 2008-12-10
Posts: 624

Re: Installation problems: I/O erro: dev sr0

Switched to http://www.imgburn.com/ and suddenly both systems boot perfectly off the newly burned media.

Going to do some more verification, check discs against each other and the like. The burner application seems to have been the cause.

*edit*

Odd, the install media has the exact same MD5 sum. I’m at a loss for words here.

Last edited by stefanwilkens (2015-10-14 12:53:55)

Arch i686 on Phenom X4 | GTX760

#23 2015-11-22 20:28:50

frank_claessen
Member
Registered: 2015-11-22
Posts: 1

Re: Installation problems: I/O erro: dev sr0

Hi all,

I realize this is an old post. Yet, trying to burn the latest iSO — having md5sum-checked the iso after download — having burt with both brasero and wodim, I have the same problem.

Same error messages as below, just a different sector number.

I am side stepping this problem now by trying to install from a knoppix live distro — which boots perfectly by the way — even if burnt with brasero.

Burning on Ubuntu 15.04

Anybody knows what I causing this?

Regards

Frank

#24 2015-11-23 10:27:12

Lone_Wolf
Member
From: Netherlands, Europe
Registered: 2005-10-04
Posts: 10,650

Re: Installation problems: I/O erro: dev sr0

Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.

(A works at time B)  && (time C > time B ) ≠  (A works at time C)

#25 2015-11-23 19:39:14

Jarry
Member
Registered: 2015-11-23
Posts: 1

Re: Installation problems: I/O erro: dev sr0

I’d just like to confirm that after an identical problem trying to install from a CD, Lone_Wolf and LK’s solution of burning the disk using SAO(DAO) mode worked for me.  Many thanks; I don’t think I would ever have sussed that one out on my own.

Источник

I have Ubuntu Server 20.04 installed in virtual machine on my Windows Hyper-V host.
I’d like it to get IP address from my Windows DHCP-server in local network
But it doesn’t work and I don’t know why. Virtual machine with Windows with same configuration works fine.

ip a output:

1: lo: <L00PBACK,UP,L0WER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
 inet 127.0.0.1/8 scope host lo
    valid.lft forever preferred.lft forever
 inet6 ::1/128 scope host
    valid.lft forever preferred.lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
 link/ether 00:15:5d:00:28:18 brd ff:ff:ff:ff:ff:ff
 inet6 fe80::215:5dff:fe00:2818/64 scope link
    valid.lft forever preferred.lft forever

Content of /etc/netplan/00-installer-config.yaml:

network:
  ethernets:
    eth0:
      dhcp4: true
  version: 2

Output of sudo netplan --debug generate

DEBUG:command generate: running ['/lib/netplan/generate']
** (generate:1818): DEBUG: 12:50:00.358: Processing input file /etc/netplan/00-installer-config.yaml..
** (generate:1818): DEBUG: 12:50:00.359: starting new processing pass
** (generate:1818): DEBUG: 12:50:00.360: We have some netdefs, pass them through a final round of validation
** (generate:1818): DEBUG: 12:50:00.360: eth0: setting default backend to 1
** (generate:1818): DEBUG: 12:50:00.361: Configuration is valid
** (generate:1818): DEBUG: 12:50:00.361: Generating output files..
** (generate:1818): DEBUG: 12:50:00.362: openvswitch: definition eth0 is not for us (backend 1)
** (generate:1818): DEBUG: 12:50:00.363: NetworkManager: definition eth0 is not for us (backend 1)
(generate:1818): GLib-DEBUG: 12:50:00.363: posix_spawn avoided (fd close requested)
(generate:1818): GLib-DEBUG: 12:50:00.365: posix_spawn avoided (fd close requested)

Output of sudo netplan --debug apply

** (generate:1826): DEBUG: 12:53:09.513: Processing input file /etc/netplan/00-installer-config.yaml..
** (generate:1826): DEBUG: 12:53:09.514: starting new processing pass
** (generate:1826): DEBUG: 12:53:09.515: He have some netdefs, pass them through a final round of validation
** (generate:1826): DEBUG: 12:53:09.516: eth0: setting default backend to 1
** (generate:1826): DEBUG: 12:53:09.517: Configuration is valid
** (generate:1826): DEBUG: 12:53:09.518: Generating output files..
** (generate:1826): DEBUG: 12:53:09.519: openvswitch: definition eth0 is not for us (backend 1)
** (generate:1826): DEBUG: 12:53:09.520: NetworkManager: definition eth0 is not for us (backend 1)
(generate:1826): GLib-DEBUG: 12:53:09.521: posix_spawn avoided (fd close requested)
(generate:1826): GLib-DEBUG: 12:53:09.523: posix_spawn avoided (fd close requested)
DEBUG:netplan generated networkd configuration changed, restarting networkd
DEBUG:eth0 not found in {}
DEBUG:Merged config:
network:
  ethernets:
    eth0:
      dhcp4: true
  version: 2
  
DEBUG:no netplan generated NM configuration exists
DEBUG:eth0 not found in {}
DEBUG:Merged config:
network:
  ethernets:
    eth0:
      dhcp4: true
  version: 2
  
DEBUG:Link changes: {}
DEBUG:netplan triggering .link rules for lo
DEBUG:netplan triggering .link rules for eth0
DEBUG:eth0 not found in {}
DEBUG:Merged config:
network:
  ethernets:
    eth0:
      dhcp4: true
  version: 2

cat /etc/network/interfaces output

cat: /etc/network/interfaces/: No such file or directory

ls -al /etc/netplan output

total 12
drwxr-xr-x 2    root    root    4096    Nov 26  14:01
drwxr-xr-x 106  root    root    4096    Nov 25  16:45
-rw-r--r-— 1    root    root    115     Nov 26  14:01   00-installer-config.yaml

cat /etc/netplan/*.yaml output

# This is the network config written by 'subiquity'
network:
  ethernets:
    eth0:
      dhcp4: true
  version: 2

sudo lshw -C network output

[77792.441265] blk_update_request: I/O error, dev sr0, sector 0 op 0x0: (READ) flags 0x80700 phys_seg 4 prio class 0     
[77792.442325] blk_update_request: I/O error, dev sr0, sector 0 op 0x0: (READ) flags 0x0 phys_seg 1 prio class 0
[77792.443250] Buffer I/O error on dev sr0, logical block 0, async page read       
[77792.444154] blk_update_request: I/O error, dev sr0, sector 1 op 0x0: (READ) flags 0x0 phys_seg 1 prio class 0
[77792.445145] Buffer I/O error on dev sr0, logical block 1, async page read       
[77792.446145] blk_update_request: I/O error, dev sr0, sector 2 op 0x0: (READ) flags 0x0 phys_seg 1 prio class 0
[77792.447102] Buffer I/O error on dev sr0, logical block 2, async page read       
[77792.448088] blk_update_request: I/O error, dev sr0, sector 3 op 0x0: (READ) flags 0x0 phys_seg 1 prio class 0
[77792.449085] Buffer I/O error on dev sr0, logical block 3, async page read       
[77792.450098] blk_update_request: I/O error, dev sr0, sector 4 op 0x0: (READ) flags 0x0 phys_seg 1 prio class 0
[77792.451058] Buffer I/O error on dev sr0, logical block 4, async page read       
[77792.452411] blk_update_request: I/O error, dev sr0, sector 5 op 0x0: (READ) flags 0x0 phys_seg 1 prio class 0
[77792.453448] Buffer I/O error on dev sr0, logical block 5, async page read       
[77792.454518] blk_update_request: I/O error, dev sr0, sector 6 op 0x0: (READ) flags 0x0 phys_seg 1 prio class 0
[77792.455569] Buffer I/O error on dev sr0, logical block 6, async page read       
[77792.456646] blk_update_request: I/O error, dev sr0, sector 7 op 0x0: (READ) flags 0x0 phys_seg 1 prio class 0
[77792.457762] Buffer I/O error on dev sr0, logical block 7, async page read       
[77792.458901] blk_update_request: I/O error, dev sr0, sector 0 op 0x0: (READ) flags 0x0 phys_seg 1 prio class 0
[77792.460028] Buffer I/O error on dev sr0, logical block 0, async page read       
[77792.461166] Buffer I/O error on dev sr0, logical block 1, async page read       
    *-network
        description: Ethernet interface
        physical id: 1
        logical name: eth0
        serial: 00:15:5d:00:28:18
        size: 1Gbit/s
        capabilities: ethernet physical
        configuration: autonegotiation=off broadcast=yes driver=hv_netvsc duplex=full firmware=N/A link=yes multicast=yes speed=lGbit/s

Источник


blk_update_request: I/O error, dev sr0, sector 9180400 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0

Bug #1900388 reported by
navycat
on 2020-10-19

This bug affects 8 people

Affects Status Importance Assigned to Milestone


linux (Ubuntu)

Confirmed

Undecided


Unassigned

Bug Description

blk_update_request: I/O error, dev sr0, sector 9180400 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0

PIONEER BD-RW BDR-205

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: linux-image-5.8.0-23-generic 5.8.0-23.24
ProcVersionSignature: Ubuntu 5.8.0-23.24-generic 5.8.14
Uname: Linux 5.8.0-23-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu50
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC2: navycat 2032 F…. pulseaudio
 /dev/snd/controlC0: navycat 2032 F…. pulseaudio
 /dev/snd/controlC1: navycat 2032 F…. pulseaudio
CasperMD5CheckResult: skip
Date: Mon Oct 19 10:11:53 2020
InstallationDate: Installed on 2020-10-07 (11 days ago)
InstallationMedia: Ubuntu-MATE 20.10 «Groovy Gorilla» — Beta amd64 (20201007)
IwConfig:
 lo no wireless extensions.

 eno1 no wireless extensions.
MachineType: BASE_BOARD_MANUFACTURER MODEL_NAME
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-23-generic root=UUID=98343bbf-e244-4e6d-889d-fa14ff0254ed ro quiet splash vt.handoff=7
PulseList: Error: command [‘pacmd’, ‘list’] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-5.8.0-23-generic N/A
 linux-backports-modules-5.8.0-23-generic N/A
 linux-firmware 1.190
RfKill:

SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/09/2018
dmi.bios.release: 4.6
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 4.6.5
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: 150-SE-E789
dmi.board.vendor: EVGA
dmi.board.version: Patsburg
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd04/09/2018:br4.6:svnBASE_BOARD_MANUFACTURER:pnMODEL_NAME:pvrBASE_BOARD_VERSION:rvnEVGA:rn150-SE-E789:rvrPatsburg:
dmi.product.family: X86 AT
dmi.product.name: MODEL_NAME
dmi.product.sku: PROJECT_SUB_TAG
dmi.product.version: BASE_BOARD_VERSION
dmi.sys.vendor: BASE_BOARD_MANUFACTURER

Источник

I’m using a 16-to-18-years-old laptop, a Clevo Zeus M3CW, on which I recently installed antiX Linux 19.3. The kernel version is 4.9.235 (compiled for 486).

Now, whenever I boot, the kernel complains about I/O errors from device /dev/sr0 — my laptop’s built-in CD-ROM. This is what lsblk says about the device:

# lsblk -o +VENDOR,MODEL | head -1 ; lsblk -o +VENDOR,MODEL | grep sr0
NAME   MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT VENDOR   MODEL
sr0     11:0    1  1024M  0 rom             TEAC     DW-224E-A

The drive is empty — no CD in there.

Later while the system runs, I get innumerable dmesg entries such as the following:

[   53.250051] sr 1:0:0:0: [sr0] tag#0 unaligned transfer
[   53.250056] sr 1:0:0:0: [sr0] tag#0 unaligned transfer
[   53.250066] sr 1:0:0:0: [sr0] tag#0 unaligned transfer
[   53.250071] sr 1:0:0:0: [sr0] tag#0 unaligned transfer
[   53.250076] sr 1:0:0:0: [sr0] tag#0 unaligned transfer

and also this:

[   53.312725] REISERFS warning (device sr0): sh-2006 read_super_block: bread failed (dev sr0, block 16, size 512)
[   53.312746] sr 1:0:0:0: [sr0] tag#0 unaligned transfer
[   53.312754] REISERFS warning (device sr0): sh-2006 read_super_block: bread failed (dev sr0, block 128, size 512)
[   53.359602] sr 1:0:0:0: [sr0] tag#0 unaligned transfer
[   53.359617] EXT4-fs (sr0): unable to read superblock
[   53.405593] sr 1:0:0:0: [sr0] tag#0 unaligned transfer
[   53.405606] EXT4-fs (sr0): unable to read superblock
[   53.464594] sr 1:0:0:0: [sr0] tag#0 unaligned transfer
[   53.464608] EXT2-fs (sr0): error: unable to read superblock
[   53.533449] sr 1:0:0:0: [sr0] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[   53.533461] sr 1:0:0:0: [sr0] tag#0 Sense Key : Medium Error [current] 
[   53.533478] sr 1:0:0:0: [sr0] tag#0 Add. Sense: Unable to recover table-of-contents
[   53.533490] sr 1:0:0:0: [sr0] tag#0 CDB: Read(10) 28 00 00 00 00 00 00 00 02 00
[   53.533516] SQUASHFS error: squashfs_read_data failed to read block 0x0
[   53.533528] squashfs: SQUASHFS error: unable to read squashfs_super_block

and these:

[ 2852.951421] sr 1:0:0:0: [sr0] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[ 2852.951431] sr 1:0:0:0: [sr0] tag#0 Sense Key : Medium Error [current] 
[ 2852.951444] sr 1:0:0:0: [sr0] tag#0 Add. Sense: Unable to recover table-of-contents
[ 2852.951453] sr 1:0:0:0: [sr0] tag#0 CDB: Read(10) 28 00 00 07 ff fc 00 00 02 00
[ 2852.951458] blk_update_request: 1680 callbacks suppressed
[ 2852.951462] blk_update_request: I/O error, dev sr0, sector 2097136
[ 2852.951509] sr 1:0:0:0: [sr0] tag#0 unaligned transfer
[ 2852.951514] blk_update_request: I/O error, dev sr0, sector 2097136
[ 2852.951521] buffer_io_error: 1670 callbacks suppressed
[ 2852.951525] Buffer I/O error on dev sr0, logical block 2097136, async page read
[ 2852.951540] sr 1:0:0:0: [sr0] tag#0 unaligned transfer
[ 2852.951544] blk_update_request: I/O error, dev sr0, sector 2097137
[ 2852.951550] Buffer I/O error on dev sr0, logical block 2097137, async page read
[ 2852.951563] sr 1:0:0:0: [sr0] tag#0 unaligned transfer

I should also note that if I insert a CD, it automounts and reads fine.

My questions:

  1. What makes the kernel try to read from /dev/sr0 all the time? Especially on boot, when it’s not in /etc/fstab nor mentioned in the grub configuration.
  2. How can I make the kernel give up on this device? From the get-go or after failing a few times?
Источник

Mine are these:

Φεβ 18 22:37:49 ioannis-desktop kernel: ACPI BIOS Warning (bug): Optional FADT field Pm2ControlBlock has valid Length but zero Address: 0x0000000000000000/0x1 (20190816/tbfadt-615)
Φεβ 18 22:37:49 ioannis-desktop kernel: RAS: Correctable Errors collector initialized.
Φεβ 18 22:37:49 ioannis-desktop kernel: kfd kfd: error getting iommu info. is the iommu enabled?
Φεβ 18 22:37:49 ioannis-desktop kernel: kfd kfd: Error initializing iommuv2
Φεβ 18 22:37:49 ioannis-desktop kernel: kfd kfd: device 1002:130f NOT added due to errors
Φεβ 18 22:37:49 ioannis-desktop kernel: ACPI BIOS Error (bug): Could not resolve symbol [_SB.ALIB], AE_NOT_FOUND (20190816/psargs-330)
Φεβ 18 22:37:49 ioannis-desktop kernel: ACPI Error: Aborting method _SB.PCI0.VGA.ATC0 due to previous error (AE_NOT_FOUND) (20190816/psparse-529)
Φεβ 18 22:37:49 ioannis-desktop kernel: ACPI Error: Aborting method _SB.PCI0.VGA.ATCS due to previous error (AE_NOT_FOUND) (20190816/psparse-529)
Φεβ 18 22:37:49 ioannis-desktop kernel: random: 7 urandom warning(s) missed due to ratelimiting
Φεβ 18 22:37:49 ioannis-desktop kernel: EXT4-fs (dm-1): re-mounted. Opts: errors=remount-ro
Φεβ 18 22:38:00 ioannis-desktop kernel: usb 6-1: Warning! Unlikely big volume range (=496), cval->res is probably wrong.
Φεβ 18 22:38:00 ioannis-desktop kernel: usb 6-1: Warning! Unlikely big volume range (=1008), cval->res is probably wrong.
Φεβ 18 22:38:00 ioannis-desktop kernel: usb 6-1: Warning! Unlikely big volume range (=496), cval->res is probably wrong.
Φεβ 18 22:38:02 ioannis-desktop systemd[1]: Starting GRUB failed boot detection…
Φεβ 18 22:38:04 ioannis-desktop systemd[1]: Finished GRUB failed boot detection.
Φεβ 18 22:38:06 ioannis-desktop thermald[923]: [WARN]NO RAPL sysfs present
Φεβ 18 22:38:07 ioannis-desktop thermald[923]: I/O warning : failed to load external entity «/etc/thermald/thermal-conf.xml»
Φεβ 18 22:38:07 ioannis-desktop thermald[923]: [WARN]error: could not parse file /etc/thermald/thermal-conf.xml
Φεβ 18 22:38:07 ioannis-desktop thermald[923]: [WARN]Unsupported cpu model, use thermal-conf.xml file or run with —ignore-cpuid-check
Φεβ 18 22:38:07 ioannis-desktop thermald[923]: [ERR]THD engine start failed
Φεβ 18 22:38:07 ioannis-desktop udisksd[925]: failed to load module mdraid: libbd_mdraid.so.2: cannot open shared object file: No such file or directory
Φεβ 18 22:38:07 ioannis-desktop udisksd[925]: Failed to load the ‘mdraid’ libblockdev plugin
Φεβ 18 22:38:09 ioannis-desktop NetworkManager[906]: <warn> [1613680689.9866] sup-iface: failed to cancel p2p connect: P2P cancel failed
Φεβ 18 22:38:10 ioannis-desktop NetworkManager[906]: <warn> [1613680690.8612] device (wlp1s5): no secrets: No agents were available for this request.
Φεβ 18 22:38:10 ioannis-desktop NetworkManager[906]: <info> [1613680690.8612] device (wlp1s5): state change: need-auth -> failed (reason ‘no-secrets’, sys-iface-state: ‘managed’)
Φεβ 18 22:38:10 ioannis-desktop NetworkManager[906]: <warn> [1613680690.8626] device (wlp1s5): Activation: failed for connection ‘devolo-f4068d22fdba’
Φεβ 18 22:38:10 ioannis-desktop NetworkManager[906]: <info> [1613680690.8629] device (wlp1s5): state change: failed -> disconnected (reason ‘none’, sys-iface-state: ‘managed’)
Φεβ 18 22:38:11 ioannis-desktop networkd-dispatcher[1122]: WARNING: systemd-networkd is not running, output will be incomplete.
Φεβ 18 22:38:42 ioannis-desktop cinnamon-session[1158]: WARNING: t+17,88042s: Detected that screensaver has appeared on the bus
Φεβ 18 22:38:47 ioannis-desktop pulseaudio[1157]: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Φεβ 18 22:38:47 ioannis-desktop dbus-daemon[905]: [system] Failed to activate service ‘org.bluez’: timed out (service_start_timeout=25000ms)
Φεβ 18 22:38:56 ioannis-desktop NetworkManager[906]: <warn> [1613680736.8471] device (wlp1s5): no secrets: No agents were available for this request.
Φεβ 18 22:38:56 ioannis-desktop NetworkManager[906]: <info> [1613680736.8472] device (wlp1s5): state change: need-auth -> failed (reason ‘no-secrets’, sys-iface-state: ‘managed’)
Φεβ 18 22:38:56 ioannis-desktop NetworkManager[906]: <warn> [1613680736.8489] device (wlp1s5): Activation: failed for connection ‘devolo-f4068d22fdba’
Φεβ 18 22:38:56 ioannis-desktop NetworkManager[906]: <info> [1613680736.8493] device (wlp1s5): state change: failed -> disconnected (reason ‘none’, sys-iface-state: ‘managed’)
Φεβ 18 22:50:49 ioannis-desktop kernel: sr 6:0:0:0: [sr0] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Φεβ 18 22:50:49 ioannis-desktop kernel: blk_update_request: I/O error, dev sr0, sector 0 op 0x0:(READ) flags 0x80700 phys_seg 4 prio class 0
Φεβ 18 22:50:49 ioannis-desktop kernel: blk_update_request: I/O error, dev sr0, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Φεβ 18 22:50:49 ioannis-desktop kernel: Buffer I/O error on dev sr0, logical block 0, async page read
Φεβ 18 22:50:49 ioannis-desktop kernel: blk_update_request: I/O error, dev sr0, sector 1 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Φεβ 18 22:50:49 ioannis-desktop kernel: Buffer I/O error on dev sr0, logical block 1, async page read
Φεβ 18 22:50:49 ioannis-desktop kernel: blk_update_request: I/O error, dev sr0, sector 2 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Φεβ 18 22:50:49 ioannis-desktop kernel: Buffer I/O error on dev sr0, logical block 2, async page read
Φεβ 18 22:50:49 ioannis-desktop kernel: blk_update_request: I/O error, dev sr0, sector 3 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Φεβ 18 22:50:49 ioannis-desktop kernel: Buffer I/O error on dev sr0, logical block 3, async page read
Φεβ 18 22:50:49 ioannis-desktop kernel: blk_update_request: I/O error, dev sr0, sector 4 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Φεβ 18 22:50:49 ioannis-desktop kernel: Buffer I/O error on dev sr0, logical block 4, async page read
Φεβ 18 22:50:49 ioannis-desktop kernel: blk_update_request: I/O error, dev sr0, sector 5 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Φεβ 18 22:50:49 ioannis-desktop kernel: Buffer I/O error on dev sr0, logical block 5, async page read
Φεβ 18 22:50:49 ioannis-desktop kernel: blk_update_request: I/O error, dev sr0, sector 6 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Φεβ 18 22:50:49 ioannis-desktop kernel: Buffer I/O error on dev sr0, logical block 6, async page read
Φεβ 18 22:50:49 ioannis-desktop kernel: blk_update_request: I/O error, dev sr0, sector 7 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Φεβ 18 22:50:49 ioannis-desktop kernel: Buffer I/O error on dev sr0, logical block 7, async page read
Φεβ 18 22:51:01 ioannis-desktop kernel: sr 6:0:0:0: [sr0] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Φεβ 18 22:51:01 ioannis-desktop kernel: blk_update_request: I/O error, dev sr0, sector 0 op 0x0:(READ) flags 0x80700 phys_seg 3 prio class 0
Φεβ 18 22:51:01 ioannis-desktop kernel: blk_update_request: I/O error, dev sr0, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Φεβ 18 22:51:01 ioannis-desktop kernel: Buffer I/O error on dev sr0, logical block 0, async page read
Φεβ 18 22:51:01 ioannis-desktop kernel: blk_update_request: I/O error, dev sr0, sector 1 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Φεβ 18 22:51:01 ioannis-desktop kernel: Buffer I/O error on dev sr0, logical block 1, async page read
Φεβ 18 22:51:01 ioannis-desktop kernel: blk_update_request: I/O error, dev sr0, sector 2 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Φεβ 18 22:51:01 ioannis-desktop kernel: Buffer I/O error on dev sr0, logical block 2, async page read
Φεβ 18 22:51:01 ioannis-desktop kernel: blk_update_request: I/O error, dev sr0, sector 3 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Φεβ 18 22:51:01 ioannis-desktop kernel: Buffer I/O error on dev sr0, logical block 3, async page read
Φεβ 18 22:51:01 ioannis-desktop kernel: blk_update_request: I/O error, dev sr0, sector 4 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Φεβ 18 22:51:01 ioannis-desktop kernel: Buffer I/O error on dev sr0, logical block 4, async page read
Φεβ 18 22:51:01 ioannis-desktop kernel: blk_update_request: I/O error, dev sr0, sector 5 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Φεβ 18 22:51:01 ioannis-desktop kernel: Buffer I/O error on dev sr0, logical block 5, async page read
Φεβ 18 22:51:01 ioannis-desktop kernel: blk_update_request: I/O error, dev sr0, sector 6 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Φεβ 18 22:51:01 ioannis-desktop kernel: Buffer I/O error on dev sr0, logical block 6, async page read
Φεβ 18 22:51:01 ioannis-desktop kernel: blk_update_request: I/O error, dev sr0, sector 7 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Φεβ 18 22:51:01 ioannis-desktop kernel: Buffer I/O error on dev sr0, logical block 7, async page read
Φεβ 18 23:16:24 ioannis-desktop gnome-terminal-[6291]: g_menu_insert_item: assertion ‘G_IS_MENU_ITEM (item)’ failed

Источник
  • Печать

Страницы: [1] 2  Все   Вниз

Тема: ошибки dev fd0, hv_vmbus и другие  (Прочитано 7443 раз)

0 Пользователей и 1 Гость просматривают эту тему.

Оффлайн
blank

сервер Ubuntu 16.04.1 LTS
в dmesg присутствуют ошибки

blk_update_request: I/O error, dev fd0, sector 0
hv_vmbus: probe failed for device vmbus_10 (-19)
пытался бороться с флопиком добавлением его в /etc/modprobe.d/blacklist

blacklist floppyа также коментированием строки в fstab

# /dev/fd0        /media/floppy0  auto    rw,user,noauto,exec,utf8 0       0 ошибка остается, как бы отключить флопик?

по vmbus даже не знаю что и думать. в гугле даже близко ничего не нашел.

также в syslog иногда появляется warning

acpid: input device has been disconnected, fd 5 что это за устройство отключается?

ТС не появлялся на Форуме более полугода по состоянию на 14/07/2019 (последняя явка: 12/12/2018). Модератором раздела принято решение закрыть тему.
—zg_nico

« Последнее редактирование: 14 Июля 2019, 03:53:42 от zg_nico »

Оффлайн
ARTGALGANO

blank,
виртуалка в hyper-v?

Оффлайн
blank

blank,
виртуалка в hyper-v?

да, server 2008 R2

Оффлайн
ARTGALGANO

И что вы хотите от виртуалки, да еще  мелкософта?
ОС загружается, работает?

Оффлайн
blank

И что вы хотите от виртуалки, да еще  мелкософта?
ОС загружается, работает?

загружается и работает, а хочется избавиться от ошибок, хотя бы от большей части. Или отключить флопик в Ubuntu неразрешимая задача? Я линукс поставил пару дней как и решения не нашел, вот и решил спросить у профессионалов.да и не очень понимаю что это за устройство fd 5, что-то мне кажется это не флопи, может и ошибаюсь.

Оффлайн
ARTGALGANO

blank, если ошибки не критичны, то можно их проигнорировать. Тем более для виртуалки в гипер-в, который вроде как официально не поддерживает *nix-системы (или уже ).
Смотрите, какие настройки заданы для виртуалки в гипер-в.

Оффлайн
blank

blank, если ошибки не критичны, то можно их проигнорировать. Тем более для виртуалки в гипер-в, который вроде как официально не поддерживает *nix-системы (или уже ).
Смотрите, какие настройки заданы для виртуалки в гипер-в.

судя по https://technet.microsoft.com/en-us/windows-server-docs/compute/hyper-v/supported-ubuntu-virtual-machines-on-hyper-v вполне себе поддерживает, пускай и не все функции в 2008 сервере, да и драйвера hyper-v интегрированы в ядро. как минимум сеть и диски работают из коробки.
в настройках hyper-v для линукса заданы статическая оперативка и статические же диски (хотя работа с динамическими и заявлена, но решил перебдеть). флопик для виртуалки вытравить невозможно, он там есть и удалить не вмешиваясь в остальные виртуальные машины не получится, если вообще получится.
а по сути вопросов мыслей нет?

Оффлайн
snowin

и не очень понимаю что это за устройство fd 5

file /dev/fd/5

Оффлайн
blank

file /dev/fd/5

/dev/fd/5: cannot open `/dev/fd/5' (No such file or directory)

:/dev/fd$ ls
0  1  2  255

« Последнее редактирование: 23 Января 2017, 18:46:08 от blank »

Оффлайн
Pilot6

blank,
Ну флоппик не находит. Это критичная ошибка?

Я в личке не консультирую. Вопросы задавайте на форуме.

Оффлайн
blank

blank,
Ну флоппик не находит. Это критичная ошибка?

да нет, не критичная, но если от нее можно избавиться почему бы и нет? да и копаясь в этом всем приходит некоторое понимание.

Оффлайн
snowin

/dev/fd/5: cannot open `/dev/fd/5′ (No such file or directory)

а там вообще чего-нить есть, по пути /dev/fd

Оффлайн
Pilot6

да нет, не критичная, но если от нее можно избавиться почему бы и нет?

Да нельзя от нее избавиться, да и зачем. Эмулятор биоса заявляет, что есть флопик, а его на самом деле нет. Вот ядро и ругнулось. Все правильно. Избавиться от этого можно за пределами Ubuntu, если вообще можно, но это не к нам.

Я в личке не консультирую. Вопросы задавайте на форуме.

Оффлайн
blank

а там вообще чего-нить есть, по пути /dev/fd

/dev/fd ссылается на /proc/2269/fd в ней есть несколько символических ссылок @0 @1 @2 @255
если я правильно все понял.

file /dev/fd/2
/dev/fd/2: symbolic link to /dev/pts/0
file /dev/fd/1
/dev/fd/1: symbolic link to /dev/pts/0
file /dev/fd/0
/dev/fd/0: symbolic link to /dev/pts/0
file /dev/fd/255
/dev/fd/255: cannot open `/dev/fd/255' (No such file or directory)

Пользователь добавил сообщение 23 Января 2017, 19:02:51:

Да нельзя от нее избавиться

нельзя значит нельзя, собственно я и ждал или совета как избавиться или подтверждения невозможности исправления. спасибо.

ага, похоже, что ошибка с fd 5 возникает если я закрываю терминал не выполнив логоф.
snowin, спасибо за направление поиска, пройдя по всем ссылкам и попав в /dev/pts/ что-то мне это напомнило и точно ошибка при закрытии терминала без выхода.

« Последнее редактирование: 23 Января 2017, 19:31:05 от blank »

Оффлайн
ReNzRv

  • Печать

Страницы: [1] 2  Все   Вверх

Источник

Понравилась статья? Поделить с друзьями:
  • Blk update request i o error dev fd0 sector 0 centos
  • Blk update request critical target error
  • Blizzard ошибка привязки телефона
  • Blizzard как изменить регион
  • Blizzard time manager ошибка загрузки