search for: 104388

...gt; I get the following debug info: > > > > > > > > mount -o /dev/sda1 / > > > > [ <time> ] EXT4-fs (sda1): mounting ext2 file system using the ext4 > > > > subsystem > > > > [ <time> ] EXT4-fs (sda1): bad geometry: block count 104388 exceeds > size > > > of > > > > device (103408 blocks) > > > > mount: wrong fs type, bad option, bad superblock on /dev/sda1 > > > > > > It looks as if the image is properly corrupt. My suggestion > > > is to try 'virt-rescue'...

...at 01:37:55PM -0500, Leonard Basuino wrote: > > I get the following debug info: > > > > mount -o /dev/sda1 / > > [ <time> ] EXT4-fs (sda1): mounting ext2 file system using the ext4 > > subsystem > > [ <time> ] EXT4-fs (sda1): bad geometry: block count 104388 exceeds size > of > > device (103408 blocks) > > mount: wrong fs type, bad option, bad superblock on /dev/sda1 > > It looks as if the image is properly corrupt. My suggestion > is to try 'virt-rescue' on it. > > virt-rescue --suggest -a <image> Inspecti...

...nformation about > this error. See: > > http://libguestfs.org/guestfs-faq.1.html#debug > I get the following debug info: mount -o /dev/sda1 / [ <time> ] EXT4-fs (sda1): mounting ext2 file system using the ext4 subsystem [ <time> ] EXT4-fs (sda1): bad geometry: block count 104388 exceeds size of device (103408 blocks) mount: wrong fs type, bad option, bad superblock on /dev/sda1 .... also, trying to mount the image with: mount -t ext2 <image> <mount point> returns: mount: wrong fs type, bad option, bad superblock on /dev/loop0 ... the end of dmesg has: [<tim...

...asuino wrote: > > > I get the following debug info: > > > > > > mount -o /dev/sda1 / > > > [ <time> ] EXT4-fs (sda1): mounting ext2 file system using the ext4 > > > subsystem > > > [ <time> ] EXT4-fs (sda1): bad geometry: block count 104388 exceeds size > > of > > > device (103408 blocks) > > > mount: wrong fs type, bad option, bad superblock on /dev/sda1 > > > > It looks as if the image is properly corrupt. My suggestion > > is to try 'virt-rescue' on it. > > > > virt-res...

On Wed, Feb 18, 2015 at 10:07:20AM -0500, Leonard Basuino wrote: > > ><rescue> e2fsck -n /dev/sda1 > e2fsck 1.42.9 (28-Dec-2013) > The filesystem size (according to the superblock) is 104388 blocks > The physical size of the device is 103408 blocks > Either the superblock or the partition table is likely to be corrupt! > Abort? no > > /boot contains a file system with errors, check forced. > Pass 1: Checking inodes, blocks, and sizes > Pass 2: Checking directory s...

I have worked quite a bit with CentOS 4.x with SAN, multipathing, LVM etc. The way I mount my file systems is using a script that is called during startup that runs fsck, imports the physical volumes, and volume groups, activates the logical volumes, creates the mount point if needed then mounts the volume, I mainly made it for software iSCSI due to the iscsi stack loading after the system mount

On Tue, Feb 17, 2015 at 01:37:55PM -0500, Leonard Basuino wrote: > I get the following debug info: > > mount -o /dev/sda1 / > [ <time> ] EXT4-fs (sda1): mounting ext2 file system using the ext4 > subsystem > [ <time> ] EXT4-fs (sda1): bad geometry: block count 104388 exceeds size of > device (103408 blocks) > mount: wrong fs type, bad option, bad superblock on /dev/sda1 It looks as if the image is properly corrupt. My suggestion is to try 'virt-rescue' on it. > This has me wondering because the debug messages from guestfish -v -x > indica...

...> > http://libguestfs.org/guestfs-faq.1.html#debug > > > > I get the following debug info: > > mount -o /dev/sda1 / > [ <time> ] EXT4-fs (sda1): mounting ext2 file system using the ext4 > subsystem > [ <time> ] EXT4-fs (sda1): bad geometry: block count 104388 exceeds size of > device (103408 blocks) > mount: wrong fs type, bad option, bad superblock on /dev/sda1 > .... This might mean that the partition has been resized to a smaller size, but without updating the partition table. Is that the case? Can you please post the output of the guestfi...

I had located and installed wine via rpm only to discover that I needed to compile from source to get --with-opengl. Fine. The documentation with the source is written in sgml. Turns out sgml, specifically Mozaic, died on the vine thirty years ago, replaced by xml, sort of. Mozilla doesn't open sgml. A search suggested Netscape might. Curious. So I installed 7.2. It doesn't

How do I mount a partition that is in an image file? I have a file called centos.img that has 3 partitions in the file. I need to copy data to the third partition on that image file. I have seen things about a loop back device (which is fine) but then it talked about an offset parameter and I dont know what that is or more importantly what number to use. I hope I'm on the right track. How

Hope someone can point me in the right direction. I don't know if what I am trying to do should work or not. I have 2 disk images. One is a VM with an ext2 boot filesystem and ext4 filesystems with the OS loaded. I am amble to guestmount this with no issue and am able to see the files that are on the ext2 file system. I can also run guestfish on the image, mount the ext2 filesystem, and

Hi , Can any one please let me know how to capture all the boot messages of the Guest OS into a text file? I do xm create -c /etc/xen/hvm.cfg to boot the guest OS. Thanks Kishore _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

https://bugs.freedesktop.org/show_bug.cgi?id=82255 Priority: medium Bug ID: 82255 Assignee: nouveau at lists.freedesktop.org Summary: [VP2] Chroma planes are vertically stretched during VDPAU playback Severity: normal Classification: Unclassified OS: All Reporter: emil.l.velikov at gmail.com

...Auto-renaming it. Renamed to 038\0000000.\000MP /:4wK:7iK:5jc:4vW/WBDZT75/BMP/:5c3.bmp Bad file name. Auto-renaming it. Renamed to 039\0000000.\000MP Performing changes. /dev/hdb9: 6680 files, 980009/1278924 clusters /dev/hdb13: recovering journal /dev/hdb13: clean, 37/26104 files, 36385/104388 blocks : recovering journal : clean, 1691/640640 files, 367103/640584 blocks fsck died with exit status 1 Sun Oct 14 21:00:54 2007 ---------------- -- wonderful !