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
i've just burned a livecd (fedora 11), but it doesn't work correctly.it says after i hit boot:
BUFFER I/O error on device sr0 logical block 352328
and then something else, which is similar so i didn't write it down.i read on bugzilla, that is should try to append the boot command with pci=nomsi, but it doesn't work for me
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 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 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:
Quote:
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
[code]....
...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 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 5.1.19.6 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.
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
[code]....
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 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:
[code]....
I wasn't getting this error with the previous 2.6.29.6 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?
I have a one problem when i mapped a SAN to the linux box RHEL 5.3 i show the following messeage Buffer IO error on Device /dev/sdband unable to find it in fdisk -l
I have an external usb disk connected to a Debian desktop. A couple of days ago these messages started appearing in dmesg
Code: [154343.010908] EXT3-fs error (device sdb1): ext3_get_inode_loc: unable to read inode block - inode=14352940, block=57409572 [154343.014425] EXT3-fs error (device sdb1): ext3_find_entry: reading directory #13272620 offset 0 [154343.014913] EXT3-fs error (device sdb1): ext3_find_entry: reading directory #3440641 offset 0 [154343.022172] Buffer I/O error on device sdb1, logical block 53138974 [154343.022209] lost page write due to I/O error on sdb1 [154343.022218] Buffer I/O error on device sdb1, logical block 53138976 [154343.022252] lost page write due to I/O error on sdb1 [154343.022256] Buffer I/O error on device sdb1, logical block 53138977
When this appears the disk becomes unavailable and I have to remove and plug it in and mount again. After that it works couple of hour and then the problem appears again. Is this a hardware problem?
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?
So when i install ubuntu it gets to 47% and than i get this error message. After that the install doesn't really seem to do much.Code:Device /dev/sbd has a logical sector size of 4096. Not all parts of GNU Parted Support this at the moment, and the working code is HIGHLY EXPERIMENTAL.Now i did search and i found another topic where someone had the same problem. His solution was to reburn the CD and try again. I did that and it still got me the same messageP.S. I do have two boot options now however. One for ubuntu and one for windows though i already ran the uninstall.
i got a Thinkpad R61 with a Matshita drive and, as the title says, I cannot play audio cds. After inserted a cd, syslog shows:
[Code]...
I did't know if this is an hardware issue so i tried an external dvd drive but i got the same errors. To play cds i tried different programs: xmms2, cdcd, mplayer and sound-juicer and different cds (all original if this matter) but without luck. I also tried a different kernel version, actually i'm using a custom one, using a debian precompiled ones (package linux-image-2.6.32-5-amd64) but again without luck. Here a relevant kernel configuration:
I'm trying to upgrade my kernel. When i get to the step where i should build the img for grub (i guess the command below is doing that) I get this error: yaird error: bad device link in /sys/block/sda (fatal)Since I installed debian using a USB drive, HDD1 was /dev/sdb and HDD2 was /dev/sdc, the USB was /dev/sda. Is there a way to force mkinitrd.yaird to build the img for /dev/sdb?
I virtualized a PC with VMware vCenter Converter. But when I boot my virtual PC, I have an error.I found this link but I can't mount /dev, /sys and /proc. I have this error message : mount: /dev is not a block device.
After fixing drive partition numbers, I got the following error from cfdisk: Code: FATAL ERROR: Bad logical partition 6: enlarged logical partitions overlap Press any key to exit cfdisk However, I can see all my partitions with fdisk and gparted, I can mount and use all of them.I used the following guide to fix the drive numbers order: Reorder partition drive numbers in linux | LinkedBits Does somebody know whet is cfdisks problem and how can I fix it?
I had found the following error messages one of my Linux server. the file system using for this partition is EFI GPT. Is this cause because of RAID controller incompatibility or Driver mismatch? PHP Code:
I was able to write a script on Linux Shell for send and read data to a serial port. But I�m facing a problem now. If by any mean I send to de device anything else than the predefined strings, stated by the manufacturer, the device ceases to respond. The only way I found its to turn off and then turn on the thing again. Which its very impractical. Its there any way to "reset de UART chip on the device" or send some string based on the RS232 standard that clean the device buffer?
I decided to take an old Gateway that I bought off a guy cheaply and turn it into a file and web server.I purchased copies of Debian 5.0.4 i386 disks (31 in all) on the advice of a friend, the disks weren't expensive, but now that Ive installed all the disks, I'm having a variety of errors
[443.110940 end request: I/O error, dev hde, sector 76021855 [443.111074] EXT3-fs error (device hde1): ext3_get_inode_loc: unable to read inode block - inode=2375715, block=9502724 INIT: cannot execute "/sbin/getty"
the message on the title only happens with Ubuntu. In Fedora, it just stops booting from LiveCD with "WARNING: Cannot find root file system!". The rest of the symptoms are the same.I'm trying to install Fedora LiveCD on an IBM i Series notebook (model 1161-21X). It's a Celeron powered unit with RAM expanded to 512MB. It has a 10GB HDD, and an internal CD-ROM drive. Although it has two USB ports (1.1), it cannot boot from a USB drive, so no pendrive nor external CD unit solution possible.When I boot from LiveCD, it stops booting with the message above. Looking atsg, there's no CD-ROM driver loaded. Also, there's a char device for sg0, but no block device for it, so no way to mount it. It seems that the driver module has been removed from the kernel. I'm currently running Fedora Core 5 in it. This very same problem happens with any Ubuntu newer that 6 or any Fedora post 7.
I'm running 11.04 off of a 32gb flash drive. Something about grub on my install is messed up. When trying to boot after a normal shutdown, I get the following errors.
I think something about grubenv under /boot/grub is being corrupted. Loggin in under Ubuntu 10, I can make my way to the files on the 11.04 flash drive and issue the following commands to make it boot normally [URL]... file corruption happening? How can I fix it?
I'm trying to install Kubuntu on an old Windows system. I am getting tons of errors such as:
I/O error SQUASHFS error:unable to read page, block XXXXXX SQUASHFS error: unable to read fragment cache block
It then reports that it's loading ACPI modules and starting the ACPI services, starting the system log daemon, doing Wacom setup, starting kernel log daemon.....and then it reads sb_bread failed reading block umptysquat.I have a feeling that this hard drive is toast. I can't get it to install Windoze or Linux. I can't even get a prompt so I can do a low-level format. Unfortunately, I'm not super savvy with Linux and don't know what to do next.
It's been a real battle, but I am getting close.I won't go into all the details of the fight that I have had, but I've almost made it to the finish line. Here is the set up. ASUS Z8PE-D18 mother board 2 CPU, 8 Gig Ram. I recently added an OCZ Agility SSD, defined a raid 1 virtual disk on the 1 terabyte WD HDD drives, which will holds all of my user data, the SSD is for executables.The bios is set to AHCI. Windows 7 installed fine, recognizes the raid VD just fine.
I installed Ubuntu 10.04 by first booting into try and mode, then opening a terminal and issuing a "sudo dmraid -ay" command. Then performing the install. I told it to install the raid components, and told it to let me specify the partitions manually. When setting up the partitions, I told it to use the free space I set aside on the SSD from the Windows 7 install as ext4 and to mount root there. Ubuntu installed just fine, grub2 comes up just fine, and Windows 7 boots with out a hitch, recognizing the mirrored partition as I indicated previously. When I tell grub to boot linux however, it pauses and I get the "no block devices found" message. It will then boot, but it does not recognize the raid array. After Ubuntu starts up I can run "dmraid -ay" and it recognizes the raid array, but shows the two component disks of the raid array as well. It will not allow the component disks to be mounted, but they show up which is annoying. (I can live with that if I have to)
I have fixed a similar problem before by setting up a dmraid script in /etc/initramfs-tools/scripts/local-top ... following the instructions found at the bottom of this blog:[URL].. To recap: My problem is that after grub2 fires up Ubuntu 10.04.1 LTS (Lucid Lynx), it pauses, and I get "no block devices found" It then boots but does not recognize the raid array untill I manually run "dmraid -ay". I've hunted around for what to do but I have not found anything. It may be some timing issue or something, but I am so tired of beating my head against this wall.