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"
I am using Wind River Linux- 126.96.36.199-WR3.0bg_standard. The problem is whenever I execute "reboot, ls, cd" and many other commands the OS prompts me an error- "end request: i/o error, dev sda, sector "(different sector each time)" and EXT3-fs error (device sda1):ext3_get_inode_loc:unable to read inode block- inode-4088001, block-4097027 I also executed "dmesg", it also showed similar errors. Has the disk gone bad or the kernel is corrupted?
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 have a centOS 5 box with 3ware 8 port raid cards.I run fsck.ext3 -y /dev/sdb1 and it shows as clean.But after writing to the FS for about 2 minutes, it becomes read-only.When I umont -l /data, and run the fsck I get that another program is using the system an I should wait.If I reboot the server , the array comes back as clean.
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):
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
About a month and a half ago I purchased two new 500GB serial ATA hard drives from Best Buy to replace my other, very old 186GB SATA hard drive. Since then I've had issues with Linux. Sometimes when it's booting it gives a bunch of error messages, such as "failed to set xfermode," and then it boots. Other times, after INIT has started, I get ext3 errors about failing to read an inode block, then "cannot start /sbin/agetty" and "ID c5 respawning too fast," and at this point booting fails altogether. These errors seem to happen randomly. However, once the system has booted, everything seems to work fine, and there are no further issues.
I know it's not a faulty hard drive or filesystem because I've tried Linux on both hard drives numerous times, and I've reformatted many times, one time I even tried erasing one of the hard drives byte for byte and then formatting it, and still had issues.
I've tried Arch Linux, Gentoo, VectorLinux, and openSUSE, and all of them have given me these problems. The live CD's for Ubuntu 10.04, Clonezilla, and GParted all have trouble partitioning/cloning/installing to these hard drives. At this point, it's obvious to me that there is a universal problem with this particular model.
GRUB and Syslinux both work fine, and Windows XP works fine too. It's only Linux that's giving me issues.
I would rather not buy a new hard drive if I can help it, seeing as these two are almost brand new. Is there some BIOS setting that could be causing these problems? Is it some unsupported feature in the hard drives? Is it a bug in the Linux kernel?
The hard drive model is WD5000AADS. Both hard drives are this same model. My motherboard is an NForce 680i SLI.
EDIT: I've tried ext2/3, ReiserFS, and XFS, and all of them do this, so I don't think it's a filesystem issue.
I've been tasked with fixing a Red Hat system that dies with a kernel panic during the boot stage:
EXT3-fserror (dev sda1): ext3_check_descriptors: Inode bitmap for group 4 not in group (block 67239937)! EXT3-fs: group descriptors corrupted! mount: error mounting /dev/root on /sysroot as ext3: Invalid argument
I can boot into a Rescue CD, but I'm a bit out of my element because I don't use EXT3 myself, and I've never had to repair a corrupted file system before.
I'm having trouble mounting hard drives and partitions - and am rather nervous about using Yast partitioner to do this. Is there something that would tell me about mount points in Yast partitioner? So far I haven't been able to find that information anywhere. I don't want to lose information on existing drives and partitions but do want to be able to access them.Some of them appear under disk information in "My Computer" but if I try to mount them I get this error message.There is no application installed that can open files of the type block device (inode/blockdevice).I was trying to edit fstab,his didn't seem straightforward either. I've been hacking this about in other Linux distros - so not entirely clueless
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 been using CentOS 5. for around 3 months. It was all fine and was having a pleasant experience using CentOS. Today when i turned on my computer and booted CentOS i am having the below error: Grub comes up, allows me to select CentOS 5.4 kernel image. and displays RedHat Nash version: and then the below error occurs:
I am getting this error every night at 4am (right about when the cron.daily runs). when it does this, it remounts the filesystem read only. In the AM I get yelled at by users. all it takes is an fsck to fix the problem, but it does it every night. I have tried to rebuild the journal by removing the has_journal flag, running an fsck, and then re-adding the journal... same problem.. and its always the same inode.
I have added new member "i_mymember" to inode on-disk structure in ext3_fs.h file and tried to access this in userspace program, but gives me error that "error: ï¿½struct ext3_inodeï¿½ has no member named ï¿½i_mymemberï¿½ "
I was trying to move my home partition on Ubuntu, and the computer hibernated on me. I restarted it up on the live disk to survey the damage, to find that the home partition, according to fsck, "Superblock has an invalid journal (inode Clear? <y>"
my server is fedora-7 and it was working fine till yesterday yester I have power failu problem after we got problem. while booting following error coming Inode 3640928 has a bad extended atribute block
I have HP ML350 G6 Server with RAID10 enabled on bios While trying to install Centos 5.5 64 bit OS I am getting the error mentioned below. "An Error Occured trying to initialize swap on device cciss/codop3. This problem is serious and the install cannot continue."
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 188.8.131.52 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.
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.
1st. I lost my usb drives. Im using Puppy Studio(Lucid, Full HDD install, latest ver) on a Toshiba Satellite 2805-S201... My 1st Linux treasure... Anyway... I was recording audio thru audacity. Shutdown. L8r started and inserted a Flash drive and the icon never showed even though I used it hours prior with no issues. The drives are working fine meaning I can access the data on other devices. Now the newb... I cant find the USB info anywhere. i followed System-Status & Configure-Hardware info-Devices-USB devices and theres nothing there. The optical drive & sda1 are registered but the flash drives are not. Does it sound like my 2 USB ports are dead? My mouse & keyboard dont register either!
2nd. B4 today reboot was the only command I knew (so sad...) but I learned dmesg and tried that and dmesg reads