The kernel supports all important file systems (ext3/ext4, xfs, btrfs, reiserfs, jfs, vfat, ntfs), as well as network filesystems such as Samba and NFS. This rescue system requires no installation as it can be booted from a CD/DVD drive or USB stick, but it can be installed on the hard disk if you wish. It can be used for both Linux and windows computers, and on desktops as well as servers. It comes with a lot of Linux system utilities such as GParted, fsarchiver, filesystem tools and basic tools (editors, midnight commander, network tools). It aims to provide an easy way to carry out admin tasks on your computer, such as creating and editing the hard disk partitions. How can one purposely corrupted a FS/journal for testing?SystemRescueCd is a Linux system rescue disk available as a bootable CD-ROM or USB stick for administrating or repairing your system and data after a crash. So maybe I found a new, slightly different bug? I couldn't delay to do any further testing as it was a laptop of a university Lecturer that had to prepare classes for this week coming (emergency situation). I ended up using Slax 6.1.2 with e2fsprogs 1.41.3 to fix the partition and allow the Ubuntu 10.10 system to boot normally. Maybe Gentoo has missed your upstream patch for this bug? I did a "equery list|grep e2fsprog" on the systemrescueCD to confirm it is ver 1.41.14. The output from e2fsck /dev/sda1 was the same as others are having:įsck.ext4: Device or resource busy while trying to open /dev/sda1 (I do have 10 years of Linux experience.) I checked /proc/mounts (grep sda1 /proc/mounts), the mount -l command itself and also issued several umount /dev/sda1 to be sure. Using a systemrescuecd-x86-2.1.0 CD's e2fsck from the e2fsprogs package 1.41.14 failed to check an ext4 disk with errors saying the aforementioned error. Unless Gentoo's e2fsprogs 1.41.14 missed this patch? "Fixed a bug in e2fsck where if both the original and backup superblock are invalid in some way, e2fsck will fail going back to the original superblock because it didn't close the backup superblock first, and the exclusive open prevented the file system from being reopened." This leads me to think that this has not been fixedĮ2fsprogs 1.41.13 (December 13, 2010) states: Using a Slax 6.1.2 CD's e2fsck from the e2fsprogs package 1.41.3 (2008) checked and fixed an ext4 disk with errors.Įven though the Slax CD could not mount or do anything with the partition as it does not have ext4 support. 0 CD's e2fsck from the e2fsprogs package 1.41.14 failed to check an ext4 disk with errors saying the aforementioned error. Using Ubuntu 10.10 LiveCD's e2fsck from the e2fsprogs package 1,41,12 failed to check an ext4 disk with errors saying the aforementioned error. This seems to me as a bug from upstream that is filtering down through the distro's. Write(1, "Filesystem mounted or opened exc"., 61) = 61 Write(1, "fsck.ext4: Group descriptors loo"., 65) = 65 Then tries to open it a second time and fails. The bug above is that the program opens /dev/sde1 once, forgets to close it, trying backup blocks.įsck.ext4: Bad magic number in super-block when using the backup blocksįsck.ext4: going back to original superblockįsck.ext4: Device or resource busy while trying to open /dev/sde1 Done and over.įsck.ext4: Group descriptors look bad. I use the installer-CD written to the thumb drive (Startup Disk creator).Ĭonfirmed: Because when I boot with a 9.04 thumb drive, I can easily open a terminal and run fsck. Impossible to ever exit this process, I tried with Ctrl-C, Ctrl-Z, andĮven with kill -9 from another console. It starts the mount process, but never finishes, and also it is If not, I still consider the behaviour somewhat wrong: if not in Is there any way to trick fsck into believing EXT4-fs warning (device [01 31m [Ksda2 [m [K):Įxt4_clear_ journal_ err: Filesystem error recorded from previous mount:Įxt4_clear_ journal_ err: Marking fs in need of filesystem check.īut this fsck does never materialise, and can't be done manually.įinally, I tried to delete the journal, but to no avail, the "Device drive or USB stick, but it can be installed on the hard disk if you wish. EXT4-fs ( [01 31m [Ksda2 [m [K): write access will be SystemRescueCd is a Linux system rescue disk available as a bootable CD-ROM or. EXT4-fs ( [01 31m [Ksda2 [m [K): INFO: recovery sda: sda1 [01 31m [Ksda2 [m [K sda3 sda4 Shows that it is not mounted and it can't be unmounted. After a crash of Ubuntu netbook, the machine hang with initramfs (Iīooting with the same system (ubuntu 10.10) from thumb drive, I cannot fsck it:įsck.ext4: Device or resource busy while trying to open /dev/sda2įilesystem mounted or opened exclusively by another program?
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |