similar to: partition magic messed up my magic number

Hi folks, For unknown cause I encounter following mounting problem; # /mnt/hda8 mount: wrong fs type, bad option, bad superblock on /dev/hda8, missing codepage or other error In some cases useful info is found in syslog - try dmesg | tail or so # dmesg | tail via82cxxx: timeout while reading AC97 codec (0x9A0000) via82cxxx: timeout while reading AC97 codec (0x9A0000)

> [6] ctivating swap partitions: swapon: /dev/hda7: No such device or address > [6] [FAILED] > [6] ioctl 80041272 not supported by xl_block > [6] Finding module dependencies: depmod: Can''t open /lib/modules/2.4.24-xeno/modules.dep for writing > [6] [FAILED] > [6] Checking filesystems > [6] Couldn''t find matching filesystem: LABEL=/policy Edit your

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi all, I don't know if this is the right list, but here goes what happened recently to me. I have an IDE disk (hda: QUANTUM FIREBALLP AS20, ATA DISK drive / hda: 39851760 sectors (20404 MB) w/1902KiB Cache, CHS=2480/255/63, UDMA(100)) connected to 00:1f.1 IDE interface: Intel Corp. 82801BA IDE U100 (rev 12) I've decided to make a

Hi, i am seeing something interesting since the upgrade to 2.2.19/0.0.7a - I am experimenting with the am930 wireless driver and i am crashing on module exit. Everytime i reboot afterwards the var fs on /dev/hda8 is inconsistent [...] Checking all file systems... Parallelizing fsck version 1.21-WIP (01-Jun-2001) /dev/hda7: recovering journal /dev/hda7: clean, 39160/320640 files, 354596/640702

Hi, "Mircea Popescu" <nufarul.alb at go.ro> schrieb am 29.01.02: > I have this problem: > I've partitioned my hard drive with PQMagic 7 in the following way: > hda1 - fat32 > hda2 - ext2 > hda3 - fat16 > hda4 - extended > hda5 - Linux Swap > hda6 - fat32 > hda7 - ext2 > hda8 - fat32 > > I've put syslinux on

Hi, after my X froze i had a fs inconsistency after the journal replay [...] EXT3-fs: 03:06: 1 orphan inode deleted EXT3-fs: recovery complete. EXT3-fs: mounted filesystem with ordered data mode. VFS: Mounted root (ext3 filesystem) readonly. Freeing unused kernel memory: 64k freed INIT: version 2.78 booting Loading /etc/console-tools/default.kmap.gz Activating swap... Adding Swap: 264560k

Hi, Just got Fedora FC1 vanilla 2.4.25kernel+libata8patch booting problems, FC1 complains that it can not automatically find&found partitions specified with "LABEL=" in /etc/fstab, and then falls me into repair mode. In the repair mode I can mount it manually without any problems. More interesting are: 1) I have several partitions specified with "LABEL=*" in

On Wed, Dec 9, 2015 at 1:07 PM, Emilio Lazo Zaia via Syslinux <syslinux at zytor.com> wrote: > I thought I've found three bugs on syslinux 6.03: Just to be clear, is this only affecting vesamenu.c32? > (1) With sample config file as is, i.e. leaving commented MENU VSHIFT and > MENU COLOR UNSEL but uncommented MENU COLOR SEL: > > A black "border" is displayed

Please help me understand why I am unable to connect to and browse the newly configured DFS tree that I installed on my Samba server according to the instructions found in Chapter 18. "Hosting a Microsoft Distributed File System Tree" of the official how-to. Irrespective of whether I try to access the dfs file tree from either the local file browser (and choosing the SMB tree) or from

I wanted to boot gentoo on xen, but it doesn''t work. What can I do? Booting ''Xen 3.0.0 / Linux 2.6.12.5'' root (hd0,0) Filesystem type is ext2fs, partition type 0x83 kernel /xen.gz dom0_mem=131072 com1=115200,8n1 [Multiboot-elf, <0x100000:0x641cc:0x27e34>, shtab=0x18c078, entry=0x100000] module /vmlinuz-2.6.12.5-xen-0 root=/dev/md0

I thought I've found three bugs on syslinux 6.03: (1) With sample config file as is, i.e. leaving commented MENU VSHIFT and MENU COLOR UNSEL but uncommented MENU COLOR SEL: A black "border" is displayed below the selected line and on its right edge. (2) Uncommenting MENU COLOR UNSEL: This effect appears also on separators and on right edge on every unselected lines. (3)

Help! I am running FC1, with a maxtor 160GB HD installed. Drive is only about a month old. I had just finished moving data from an older HD that was making some funny sounds and throwing some random errors. All was well. Last night we lost power for several hours and 1 machine's UPS/shutdown system didn't power down the workstation. The other 7 in our office did fine. The power

I am using SuSE 7.3 compiled ext3 support into the kernel and installed it. All my partitions load up as ext3 except / . I ran tune2fs several times, still doesn't take on the / drive. Most recent dumpe2fs -h show no features on that drive=, I keep going around in circles, removing .journal from / and running tune2fs but it never works for / What am I doing wrong? ( thanks in advance)

Hello, I just went back to 2.4.9-ac18 from 2.4.10 (i386), and then for the first time migrated all my ext2 partitions to ext3. I did this over a series of reboots, as I confirmed that indeed things continued to work. The last step I took was to convert /. I have set up /etc/fstab to mount my 'ext3' partitions with 'auto', I suppose thinking this will make it easier to roll

Hello all, I have a few strange errors in my messages log I can't fix. My system works great, it just bugs me that I have error (or apparent errors) that I don't know about. I get automount errors regurlarly (daily) that are reflected in the last four lines of the log file excerpt below. My misc and net directories are there, but I can't write to them either. The properties say that

Hi everybody, I have been using rsync for quite some time, and I've realized it is a fantastic tool. As it is able to syncronize two CD images, I was wondering, if I could do that with a harddisk partition. Would it be possible to syncronize two partitions at device level somehow? I mean using: # rsync /dev/hda8 /dev/hda9 skipping non-regular file "hda8" where /dev/hda8

Hi, Each time i try tou use vhost_net, i'm facing a kernel bug. I do a "modprobe vhost_net", and start guest whith vhost=on. Following is a trace with a kernel 2.6.37, but i had the same problem with 2.6.36 (cf https://lkml.org/lkml/2010/11/30/29). The bug only occurs whith vhost_net charged, so i don't know if this is a bug in kvm module code or in the vhost_net code. Feb

Hi, Each time i try tou use vhost_net, i'm facing a kernel bug. I do a "modprobe vhost_net", and start guest whith vhost=on. Following is a trace with a kernel 2.6.37, but i had the same problem with 2.6.36 (cf https://lkml.org/lkml/2010/11/30/29). The bug only occurs whith vhost_net charged, so i don't know if this is a bug in kvm module code or in the vhost_net code. Feb

Hi everyone! I came across a problem when I used xm create to create a domainU on my machine. I installed xen-3.0.4 on my computer, running Fedora 6, kernel version is 2.6.18-1.2798.fc. I want to install a Fedora 6 on xen, so I write the following config file, named fc6.cfg kernel = "/boot/vmlinuz-2.6.16.33-xenU" memory = 128 name = "fedora.fc6" dhcp = "dhcp" disk =

Hello, I am trying to boot an RHAS 4 release 3 guest kernel (the binary release available through Redhat Network) from a SLES 10 dom0 host (the binary release available through Suse''s software distribution channel). Both systems are installed as physical partitions in a standard multiboot configuration on a single hard drive on a recent vintage HP Pavilion (zd7380) notebook PC with a