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?
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 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 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:
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 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 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.
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 rebooted my server and out of nowhere the RAID5 array won't assemble. I've tried everything I could think of to reassemble the thing. I fear that the array is ruined, but I can't imagine how. Here are various bits of information: The simplest failure (with and without partition numbers, which have not been needed in the past):
Code:
richard@nas:~$ sudo mdadm --assemble --verbose /dev/md0 /dev/sd[bcd] mdadm: looking for devices for /dev/md0 mdadm: cannot open device /dev/sdb: Device or resource busy
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 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:
For backup purposes, I built a RAID6 array on USB. When during the night the backup filesystem is being mounted, every so many days, a random disk fails:
Code: sd 9:0:0:0: [sdb] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE sd 9:0:0:0: [sdb] Sense Key : Illegal Request [current] sd 9:0:0:0: [sdb] Add. Sense: Invalid field in cdb[code].....
In other words, my RAID set fails every so many mounts, but I know how to fix it.What I want to find out is:
- Why is a random drive failed every now and then?
- How can I prevent that drive from being failed?
BTW: I have a second RAID set that has been functioning for years without error, so the setup I use must be correct. The only difference between both RAID arrays is the different vendor of the disks.
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?
have set up a server with OS on a 250GB disk (sdd) and 3x 1.5TB drives for a RAID5 storage setup (sda, sdb and sdc).Using webmin I can delete and create a primary partition in each one. But while I can also format sda and sdc, it refuses to do sdb for some reason:Executing command mkfs -t ext4 /dev/sdb1 ; partprobe ..mke2fs 1.41.11 (14-Mar-2010) /dev/sdb1 is apparently in use by the system; will not make a filesystem here!
But I'm not using it simon@ubuntu:~$ lsof | grep /dev/sdb simon@ubuntu:~$ lsof | grep /dev/sdb1
I have 10.10 installed and working OK. The Home directory is located on a second 1TB disk (sdb1). Recently, I've started to experience random boot failures where the start-up routine gets as far as showing the '10.10' logo with the progress dots underneath, but then throws up an error message saying that it cannot mount sdb1. I then have an option to Quit or drop into the shell to do a manual restart.
If I then do a Ctrl/Alt/Del, the system reboots, but usually fails again. Powering off and on, sometimes more than once, is the only way to eventually get a clean boot. The drive causing the problem is fairly new and all the diagnostic checks seem to indicate that it's healthy, so I'm not sure what causes the problem.
I am facing a problem while installing backtrack 4.0 on my virtual box. After assigning a hard drive and booting from the live cd, i am receiving a error message as follows:
Loading, please wait... Buffer I/O error on device hdc, logical block 76636 (this statement gets repeated like four times with different logical block id. SQUASHFS error: squashfs_read_data failed to read block 0x5bb337b9 SQUASHFS error: unable to read is index table.
It is not the first time i install operating systems on virtual box though it is the first time i receive such an error with backtrack.
I'm getting the following error Kpackagekit when I'm trying to refresh the packages, so I can manually check if there are any new updates. I have totally uninstalled the software, and reinstalled, but this has no effect. The following is what I see in a seperate popup.
Error Type: Error Value: coercing to Unicode: need string or buffer, exceptions.SystemError found File : /usr/share/PackageKit/helpers/apt/aptBackend.py, line 2216, in main() File : /usr/share/PackageKit/helpers/apt/aptBackend.py, line 2213, in main run(args, options.single)
[Code]...
I am running the 64bit version of 10.04 on a dual core 2GB acer laptop.
I'm getting this error when restarting clamav-daemon:clamd libClamAV Error: cli_dbgets: Line too long for provided bufferThis happened on two systems today after I upgraded via apt. Versions used: Debian Lenny w/ clamav-daemon 0.96.3+dfsg-1~volatile1Has anyone seen this and know what to do? clamd seems to be running, and the
OS: Opensuse 11.4 Webcam: Bus 002 Device 002: ID 046d:08ac Logitech, Inc. QuickCam Cool Error Message: libv4l2: error allocating conversion buffer. The quality of my webcam output is very poor. I am uncertain as to what I can do to re
Since May 12,2009. Our system lifekeeper has the error log "lifekeeper error: DEVICE FAILURE on SCSI device '/dev/add'", but it ran normally. Until last week, it failover to the standby server. The disk still running, the error still come out.
every time I try to connect to the ftp server I setup i am recieving this error Response:*** buffer overflow detected ***: /usr/sbin/vsftpd terminated Error:Could not connect to server
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 just compiled my first own kernel (I'm using Arch Linux), following the tutorial on the german site. Now I tried to boot it, I ended up failing with this message: Code: Waiting 10 seconds for device /dev/sda1 ... Root device '/dev/sda1' doesn't exist, Attempting to create it. ERROR: Unable to determine major/minor number of root device '/dev/sda1' Here is the important part of my menu.lst:
[Code]....
I simply copy&pasted the Arch-entry, i.e. I also had the disk by uuid there. The failure message was the same, just the root device name was the different name Also, at first I did not have the initrd line in my menu.lst (as written in my tutorial that I may not need it). In this case I had this error message:
