Hardware :: Mem - 'input Output Error On Sr0 Logical Block (a Large Number) After A Long Time The Booting Proceeds To A Point
Aug 29, 2010
I have been having a lot of trouble lately with installing from CD/DVD. The DVD reader/writer on this laptop is new. Nevertheless, trying to install Ubuntu onto an exernal HD, I get 'input output error on sr0 logical block (a large number) After a long time the booting proceeds to a point, but I never get the actual installation started, and have to shut down manually.
The CD is fine, says the Ubuntu-checker. I just installed using my sons laptop, and there was no trouble. Question: does this indicate a motherboard failure? A memory block damaged? Do you know of a diagnostic tool I can use to check the reading of a CD/DVD?
I recently upgraded my file/media server to Fedora 11. After doing so, I can no longer copy large files to the server. The files begin to transfer, but typically after about 1gb of the file has transferred, the transfer stalls and ultimately fails with the message:
"Error writing to file: Input/output error"
I've run out of ideas as to what could cause this problem. I have tried the following:
1. Different NFS versions: NFS3 and NFS4 2. Tried copying the files to different physical drives on the server. 3. Tried copying the files from different physical drives on the client. 4. Tried different rsize and wsize block sizes when mounting the NFS share 5. Tried copying the files via a different protocol. SSH in this case. The file transfers are always successful when I use SSH.
Regardless of what I do, the result is the same. The file transfers always fail after approximately 1gb.
Some other notes.
1. Both the client and the server are running Fedora 11 kernel 22.214.171.124-191.fc11.x86_64
I am out of ideas. Has anyone else experienced something similar?
I'm trying trying to understand dd, and I'd like to know why frequently do we have to use a block read/write size, like "dd bs=1024", "dd ibs=512"... If it executes the operation byte by byte, isn't it irrelevant? What is this block size then?
I am trying to debug the issue of a desktop that has for the last two weeks started having kernel panics at boot time. This machine has been running flawlessly for the last 8 years, and has had three OS upgrades. I am using memtest to try to understand the issue. The following is part of the memtest output: Reading all physical volumes Buffer I/O error device hdc logical block 0 Buffer I/O error device hdc logical block 15
Illegal node for this track or incompatible media (asc=0x64 ascq=0x00) The failed "Read 10" packet command was /dev/hdc: read failed after 0 of 4096 at 0 Input/output error and similar set of mesaages After this udev checks correctly, and hardware, storage and audio are initialized However sometime in the middle of the boot process, a kernel panic occurs with message Kernel panic -- not symcing : Fatal exception in interrupt
I have 2 hdds, with encrypted / and /home. Besides there are four other (encrypted ext4) partitions I use rarely. In Fedora 11 at boottime I gave the luks passphrase for / and home and the system booted as intended.
Whenever I needed those extra encrypted partitions I mounted them in Nautilus. Now, in Fedora 12 at boottime dracut tries to open all the encrypted partitions, / and /home are mounted fine, but opening all the other partitions gave the following messages in messages.log:
dracut: luksOpen /dev/sdb6 luks-02a0e706-a26f-4019-a2a0-88a0366a994d kernel: Buffer I/O error on device dm-0, logical block 124 kernel: device-mapper: ioctl: unable to remove open device temporary-cryptsetup-304 kernel: Buffer I/O error on device dm-0, logical block 124 kernel: Buffer I/O error on device dm-0, logical block 124
...and these messages are repeated with the other partiitions, and the boot time takes very, very long. How can I tell dracut to ignore those extra encrypted partitions at boottime?
i have a inspiron 1520 laptop which is starting to slow down some so i thought linux would help because all i do is internet use, so i download it from another computer and mount it to a usb flash drive like the site says, (netbook remix latest version) then i put it in my laptop and it loads all the way and i press try and after about 10 minutes of loading it lets me try. so that was ok really slow but i thought id install it to hard drive to see if it improved speed. so the next time i start my laptop i get Buffer i/o error on device loop0 logical block xxxxxx so i redo the usbflashdrive no errors switch usb ports and same thing, ive done the switch usb ports and redo the flash drive about 4 times im really getting mad at linux before i even have it installed.
I just downloaded an iso of the latest CentOS dist (5.3) and burned it to disk. I booted from the CD and received the following error: Memory for crash kernel (0x0 to 0x0) not within permissible range Illegal mode for this track or incompatible medium -- (asc=0x64, ascq-0x00) The failed "read 10" packet command was: Buffer I/O error on device hdd, logical block 176935
(This error message repeats for another 9 or 10 times then it says the following) Red Hat nash version 126.96.36.199 starting Setting up new root fs (Then there are some unmounts which are old /dev, /proc, /sys. At this point a series of steps begin).
Setting Clock Starting udev Loading default keymap (us) Setting hostname local host.localdomain Setting up logical volume management Checking file systems
These are just some of the steps that appear after the above error is displayed, all of the steps that load have an ok status. After those are completed I get to a text prompt - localhost login: At this point my keyboard does not seem to respond, pressing enter or any of the other keys seems to have no effect. I noticed that during the load process I could toggle the light for caps and num lock, but at the login screen it does'nt work. So at this point I'm not sure if I'm having a technical issue or if its just another case of an user error.
Create symlink /dev/root and then exit this to continue the boot sequence.
Buffer I/O error on device sr0, logical block ******* sr 4:0:0:0 [sr0] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE,SUGGEST_OK sr 4:0:0:0 [sr0] Sense Key : Medium Error [current] sr 4:0:0:0 [sr0] ASC=0x10 <<vendor>> ASCQ=0x90 end_request: I/O error, dev sr0, sector 1395920 Clocksource tsc unstable (delta = -499902943 ns)
loops that during install. new hard drive fresh out of box. WD 320GB 7200 Toshiba Qosmio intell core duo i've installed with this same disk before previous hard drive died. installed over windows vista. this time im trying to install solo no windows disk to reinstall with, F10 only. I've tried other distros as well, Mandriva one 2009, Dreamlinux, and this one. i've suspected hard drive controller went out but i can format and partition the drive. also the cd/dvd drive is bad but im booting from cd fine. tried removing the cd drive and booting from an external usb cd rom, same errors.
im about to deploy and need my computer up and running ASAP. 7 months no entertainment is not good. when i use a linux boot disk from Ultimate Boot Disk (UBD) i get an error of - hda status no response and something about invalid heads dreamlinux pushes past the error till i get the error about cant start x server. about my graphics
The external hard drive which contains all my photos and where I backed-up all my important documents is no longer recognized. It is a three month old 500GB Iomage Prestige Desktop Hard Drive.When I plug it in, it is recognised as a USB device, because it shows up when I type lsusb, but dmesg gives this error message.
[19712.013250] usb 2-2: new high speed USB device using ehci_hcd and address 21 [19712.145347] usb 2-2: configuration #1 chosen from 1 choice [19712.147214] scsi25 : SCSI emulation for USB Mass Storage devices
I popped the disk out of the casing put it on a SATA connect internally and then tried the file recovery programs testdisk/photorec and SpinRite, but both failed because they couldn't recognize the external hard disk.
I am running Centos 5.3. I ran no updates, performed no installs, nor changed any configuration immediately prior to this issue. My problem is this: when I run the command startx (default runlevel 3), it is a long time (5-10 minutes) before Gnome startx, and once it does start applications will not run. Also, when I try to use sudo (from any environment, even ssh), it is a long time (5-10) before the command is executed.
I cannot say for sure, but it seems like this is an intermittent problem. Sometimes X takes a long time to start, but once it starts it will launch programs. Sometimes X takes a long time to launch, but once it starts it will only launch certain programs. Though presently X always takes a long time to start, and I cannot successfully launch any programs.
A while back a had a similar problem to this (x taking long time to start, sudo taking long time to execute) and it ended up being a DNS problem. Unfortunately, I cannot remember exactly what it was and I stupidly did not document it. Maybe this is also DNS related, I don't know.
I don't know what log files to look at for problems with X, Gnome, and sudo taking a long time to start.
I compiled a new kernel for slackware 13 yesterday and all is going well, except for the fact that during boot I get errors regarding a second hard drive. They are of the form PHP Code:
I wasn't getting this error with the previous 188.8.131.52 kernel. As far as I can tell everything is working fine, but the errors make me nervous as this is where all my data is stored. The partition was previously formatted ntfs-3g and I thought maybe I'd done something with ntfs support while configuring the kernel so I backed up the data, reformatted to ext4 which matches all other linux partitions except for swap of course, and I get the exact same errors.
1. Is there something different in this kernel in reporting errors or maybe something I set in configuration?
2. recommend a good (simple and ubiquitous) cli program to check the disk for errors so that I can run it in both the old and new slack kernels as well as mandriva on the same machine?
Quote:Error benchmarking: helper exited with exit code 1: Error reading 27099136 bytes at 2509258752 from /dev/sda: Input/output errorthis issue is also preventing me from making a copy/backup of the partition with gpartedwhich i decided i should do since i had a scare when booting todayunable to mount / i said fix itthen it said /var was not readyi waited it became readyi am running 10.04.2 would upgrading the kernel to get trim support fix it?
Code: sudo fsck -t ext4 /dev/sda1 fsck from util-linux-ng 2.17.2 e2fsck 1.41.14 (22-Dec-2010) System: clean, 247383/983040 files, 1394162/3907803 blocks Solution: drive is under warranty and it needs to be used this is not software problem
I am using the package Quantum espresso to get electron phonon coefficients for monolayer graphene. While applying one of the executables, I got the error: "At line 356 of file q2r.f90 (Unit 51 "a2Fq2r.51") Traceback not availabel: compile with -ftrace=frame or -ftrace=full. Fortran Runtime error: bad real number in item 1 of list input
My dad is out of town for a while, so I've been using his computer to rip my DVDs with Handbrake. He has Windows Vista installed, so I did a full installation of Fedora 13 on a thumb drive and just run everything off of that. However, when I went to delete some of the encoded videos after I had moved them to my computer, I got a system error that said 'can't delete files: I/O error.' Now, if I try to boot up Windows, his computer is stuck on a black screen checking a bunch of dlls. He'll be back in a couple of weeks, so I'd like to have it fixed by then.
I have dir in my HD that is very important to me,but when I try cd commad to go in the dirI got this message:cannot access `./Lab': Input/output erroralso when use ls to view the currently dir and the other dir's also I got this message:"ls: cannot access Lab: Input/output errorLab"with touch:touch: cannot touch `Lab': Input/output errorwith mkdir:mkdir: cannot create directory `Lab': Input/output error
We are running an C++ application in AWS EC2 instance (CentOS 5.4) mounted with an EBS Volume (say /mymountpoint). We do more simultaneous writes to the EBS Volume from our application. But at some point we get 'ERROR: Input/output error'. After this, 'ls -l /mymountpoint' command itself fails with the i/o error. The filesystem which we use for the EBS Volume is xfs. I unmounted the drive and done xfs_check and again mounted the drive. Now, everything seems to be working fine. But the issue still persists everytime when we do simultaneous writes.
I believe the following details will be useful, [root@domU-12-31-39-07-81-36 StoreGrid]# cat /etc/redhat-release CentOS release 5.4 (Final) .....
Output of dmesg : SGI XFS with ACLs, security attributes, large block numbers, no debug enabled SGI XFS Quota Management subsystem Filesystem "sdh": Disabling barriers, not supported by the underlying device XFS mounting filesystem sdh Ending clean XFS mount for filesystem: sdh ..... Starting XFS recovery on filesystem: sdh (logdev: internal) Ending XFS recovery on filesystem: sdh (logdev: internal) The XFS utilities are in v2.9.4
I'm either missing the obvious or have four identically defective tape drives. Each is a Seagate or IBM Travan drive (yes, I know they're old and I need to access the data; they were in Win boxes) using QIC-80/DC-2120 media. I've been trying to solve this using three Fedora boxes (different versions) and one Debian machine.
The OS's recognize the drives and they show up as /dev/st0.
With no media in the drives, I get a status report; with media inserted, I get the same input/output errors.
Examples (all as root):
With tape inserted:
With no tape in drive:
With tape inserted
Everything I've found on Google suggests that the drives are defective.