Ext2-fs Error Read_block_bitmap Cannot Read Block Bitmap
Contents |
15 to Fedora 14 using scp. Humming group descriptors corrupted ext4 along nicely what suddenly it stopped writing files. Saw this
E2fsck
on screen ./evolution-sharp-devel-0.21.1-12.fc15.i686.rpm: Input/output error ./evolution-sharp-devel-0.21.1-12.fc15.x86_64.rpm: Input/output error ./evolution-spamassassin-3.0.1-1.fc15.x86_64.rpm: Input/output error ./evtest-1.27-1.fc15.x86_64.rpm: Input/output error ./ewftools-20100226-3.fc15.x86_64.rpm: Input/output error ./exaile-0.3.2.1-1.fc15.noarch.rpm: Input/output error ./examiner-0.5-7.fc15.noarch.rpm: Input/output error ./exempi-2.1.1-2.fc15.i686.rpm: Input/output error ./exempi-2.1.1-2.fc15.x86_64.rpm: Input/output error ./exempi-devel-2.1.1-2.fc15.i686.rpm: Input/output error ./exempi-devel-2.1.1-2.fc15.x86_64.rpm: Input/output error ./exfalso-2.3-2.fc15.x86_64.rpm: Input/output error ./exim-4.73-3.fc15.x86_64.rpm: Input/output error ./exim-clamav-4.73-3.fc15.x86_64.rpm: Input/output error ^CKilled by signal 2. I obviously killed the copy. In /var/log/messages I see a zillion of these errors May 15 11:03:49 server kernel: [456268.101524] attempt to access beyond end of device May 15 11:03:49 server kernel: [456268.119604] sdb1: rw=0, want=486539272, limit=486303552 May 15 11:03:49 server kernel: [456268.138581] EXT3-fs error (device sdb1): read_block_bitmap: Cannot read block bitmap - block_group = 1856, block_bitmap = 60817408 May 15 11:03:49 server kernel: [456268.178993] attempt to access beyond end of device May 15 11:03:49 server kernel: [456268.197015] sdb1: rw=0, want=486539272, limit=486303552 May 15 11:03:49 server kernel: [456268.215515] EXT3-fs error (device sdb1): read_block_bitmap: Cannot read block bitmap - block_group = 1856, block_bitmap = 60817408 May 15 11:03:49 server kernel: [456268.255915] attempt to access beyond end of device May 15 11:03:49 server kernel: [456268.273927] sdb1: rw=0, want=486539272, limit=486303552 May 15 11:03:49 server kernel: [456268.292675] EXT3-fs error (device sdb1): read_block_bitmap: Cannot read block bitmap - block_group = 1856, block_bitmap = 60817408 May 15 11:03:49 server kernel: [456268.332063] attempt to access beyond end of device May 15 11:03:49 server kernel: [456268.350051] sdb1: rw=0, want=486539272, limit=486303552 May 15 11:03:49 server kernel
I tried unmounting it, but had to be done with the umount -l (lee) version to make it wait until all filelocks was finished - stopped apache and it was umounted correctly.Then I went to fsck /dev/hda > no go:CODE[root@tfcclion root]# fsck /dev/hdafsck 1.27 (8-Mar-2002)e2fsck 1.27 (8-Mar-2002)fsck.ext2: Attempt to read block from filesystem resulted in short read while trying to open /dev/hdaCould this http://forums.fedoraforum.org/archive/index.php/t-263025.html be a zero-length partition?Next well tried several version of fsck, e2fsck .. so forth, read all places, tried specifying superblock and everything, maybe I did it wrong, but I tried... e2fsck -b 8193 /dev/hda1CODE[root@tfcclion root]# e2fsck -b 8193 /dev/hda1e2fsck 1.27 (8-Mar-2002)e2fsck: Attempt to read block from filesystem resulted in short read while http://www.linuxhelp.net/forums/lofiversion/index.php/t7366.html trying to open /dev/hda1Could this be a zero-length partition?Then lets try dmesg CODE sector 35389800end_request: I/O error, dev 03:01 (hda), sector 0EXT2-fs error (device ide0(3,1)): ext2_write_inode: unable to read inode block - inode=2213040, block=4423725end_request: I/O error, dev 03:01 (hda), sector 262192end_request: I/O error, dev 03:01 (hda), sector 0EXT2-fs error (device ide0(3,1)): read_block_bitmap: Cannot read block bitmap - block_group = 1, block_bitmap = 32774end_request: I/O error, dev 03:01 (hda), sector 35389800end_request: I/O error, dev 03:01 (hda), sector 0EXT2-fs error (device ide0(3,1)): ext2_write_inode: unable to read inode block - inode=2213040, block=4423725end_request: I/O error, dev 03:01 (hda), sector 262192end_request: I/O error, dev 03:01 (hda), sector 0EXT2-fs error (device ide0(3,1)): read_block_bitmap: Cannot read block bitmap - block_group = 1, block_bitmap = 32774end_request: I/O error, dev 03:01 (hda), sector 262192end_request: I/O error, dev 03:01 (hda), sector 0EXT2-fs error (device ide0(3,1)): read_block_bitmap: Cannot read block bitmap - block_group = 1, block_bitmap = 32774end_request: I/O error, dev 03:01 (hda), sector 35389800end_request&
and TimingData ConvertersDesign Tools and CalculatorsDirect Digital SynthesisEmbedded Vision SensingEnergy Monitoring and MeteringFPGA Reference DesignsInterface and IsolationLow Power RF TranceiversMEMS Inertial SensorsMotor Control Hardware PlatformsPower ManagementProcessors https://ez.analog.com/docs/DOC-8512 and DSPReference CircuitsRF and MicrowaveSwitches/MultiplexersTemperature SensorsVideoWide Band RF TransceiversWireless Sensor NetworksLog in0SearchSearchSearchCancelError: You don't have JavaScript enabled. This tool uses http://www.linksysinfo.org/index.php?threads/2-questions-on-usb-drives.72578/ JavaScript and much of it will not work correctly without it enabled. Please turn JavaScript back on and reload this page.More ext2-fs error documents in Linux Bug Archive Where is this place located?EngineerZoneAll PlacesProcessors and DSPSoftware and Development ToolsLinux Distribution for BlackfinLinux Bug ArchiveLog in to create and rate content, and to follow, bookmark, and share content with other members.[#5754] Error occurs when write to ext2-fs error read_block_bitmap SD card with spimmc in kernel trunkDocument created by Aaronwu on Sep 5, 2013Version 1Show DocumentHide DocumentLike • Show 0 Likes0 Comment • 0View in full screen modeView in normal mode [#5754] Error occurs when write to SD card with spimmc in kernel trunkSubmitted By: Vivi LiOpen Date2009-12-07 23:59:28 Close Date2010-07-13 01:09:13Priority:Medium Assignee:Sonic ZhangStatus:Closed Fixed In Release:N/AFound In Release:2010R1 Release:Category:N/A Board:N/AProcessor:BF537 Silicon Revision:Is this bug repeatable?:Yes Resolution:FixedUboot version or rev.: Toolchain version or rev.:gcc4.3_trunk3679App binary format:N/A Summary: Error occurs when write to SD card with spimmc in kernel trunkDetails:Error occurs when write to SD card in BF537-stamp with spimmc card in kernel trunk.The last passed version:--kernel: Linux release 2.6.31.6-ADI-2010R1-pre-svn7874, build #66 Thu Nov 26 00:24:00 GMT 2009toolchain: bfin-uclinux-gcc release gcc version 4.3.4 (ADI-trunk/svn-3679)us
in 'Tomato Firmware' started by rs232, Jun 19, 2016. rs232 Network Guru Member - I have formatted an USB stick with ext2 while tomato recognised it out of the box as vfat /dev/sda mke2fs /dev/sda However after a reboot the device was automatically mounted as sdb. Anything I'm missing here? Same port and no other devices plugged. I would like this to be sda only. - Is there any command that can tell me if the USB is performing as USB1, 2 or 3? Thanks rs232 rs232, Jun 19, 2016 #1 koitsu Network Guru Member 1. Filesystem type (or even partition type) has nothing to do with device naming convention. Device probing is done at a different level. "Statically assigning" block devices is difficult on Linux (even moreso on TomatoUSB), but usually the probe order is consistent -- in fact, this is the first case I have ever heard of this happening on TomatoUSB. I'd appreciate seeing output from: dmesg | grep -i sd 2. dmesg | egrep -i "(usb|ohci|uhci|ehci|xhci)" can shed some light on "some" of this (sort of), but it's not necessarily definitive. All it'll be able to tell you is if the device is attached to OHCI/UHCI (USB 1.0/1.1), EHCI (USB 2.0), or XHCI (USB 3.0) -- sometimes it can be attached to multiples simultaneously. Busybox's lsusb command (unlike "normal" Linux) does not provide enough detail in USB host and descriptor data, and hdparm (for testing I/O throughput -- which doesn't necessarily reflect interface speed (i.e. you can have a USB 3.0 device that does not perform at high USB 3.0-quality speeds)) does not come with TomatoUSB by default (Entware-ng does have an hdparm package). One cannot use Busybox dd either (no I/O statistics are provided on SIGUSR1, only blocks sent/received). I do not know of any TomatoUSB-provided /proc entries that can provide this data either. koitsu, Jun 19, 2016 #2 rs232 Network Guru Member Thanks for this Here's the output from the first command: Code: root@tomato213w:/dev# dmesg | grep -i sd EXT2-fs (sda): error: read_block_bitmap: Cannot read block bit