similar to: UFS file system problem in either stable or current

Does anyone know if support for the Intel 875P/ICH5 motherboard chipset has yet made it into the stable branch? (Is release 4.9 likely to have it?) I am mainly interested in the IDE and "native" serial ATA devices. There is also a new Intel ethernet controller chip, 82547EI, that is designed to interface directly with the 875P chip. The currently supported chip list only goes up to

A few hours ago I downloaded .../i386/ISO-IMAGES/4.9-RC1-i386-disc1.iso and made kern/mfsroot floppies from it. If I enable my ICH5R SATA controller in "native" mode, the 4.9-RC1 GENERIC kernel hangs solidly (only the system reset button can unwedge it) during device configuration. The last line of bootstrap monologue written by the kernel is: plip0" <PLIP network

I just noticed the 4.9-20030914-PRERELEASE and made a set of installation boot floppies from it to see which of the devices in my new PC the PRERELEASE would support. It wedged hard during the boot autoconfiguration monologue, just after typing these lines on the console: atapci0: <Intel ICH5 ATA100 controller> port 0xf000-0xf00f,0-0x3,0-0x7,0-0x3,0-0x7 irq 0 at device 31.1 on pci0 ata0:

Is r/w to a UFS partition using 'guestmount' still an impossibility? From everything I've found, it seems to be something that is not possible at the moment. I was just wondering if that has changed or if there are plans to change that? Here is the issue I'm experiencing: ~# guestmount --rw -a ${disk_path}/${disk_name} -m /dev/sda4 /tmp/freebsd-master libguestfs: error:

Hi Dears, I am having trouble mounting a partition with UFS file system (FreeBSD), I am trying to build with the following commands: mount-r-t-o ufs ufstype = ufs2 / dev/hdb1 / part mount-r-t-o ufs ufstype = 44bsd / dev/hdb1 / part But appears the following error message: mount: wrong fs type, bad option, bad superblock on / dev/hdb1, missing codepage or other error In some

During the last two weeks there has been some discussion in freebsd-questions and freebsd-stable about the prospects of FreeBSD support for some motherboard devices associated with the Intel 865PE/875P and ICH5/ICH5R support chips now showing up in recent motherboard designs. The 865PE/875P chips are called MCH (memory controller hub) or "northbridge" chips. The ICH5/ICH5R chips are

Hello list. I have a perfectly working PV host, with this configuration: kernel = "/boot/vmlinuz-2.6.18.8-xen-3.3.0-7mdv" ramdisk = "/boot/initrd-2.6.18.8-xen-3.3.0-7mdv.img" root = "/dev/sda1 ro" extra = "(hd0)/boot/grub/menu.lst" memory = 256 maxmem = 512 name = "sexonthebeach" uuid = "f36962f5-0dec-4708-84a0-f5b4dea48d34" disk = [

Hello, I had a scientific linux 3.0.4 system (rhel compatible), with 3 ide disks, one for / and two others in linear raid (250 gb and 300 gb each). This system was obsoleted so i move the raid disks to a new scientific linux 3.0.7 installation. However, the raid array was not detected ( I put the disks on the same channels and same master/lsave setup as in the previous setup). In fact

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

Is for these UFS bugs in FreeBSD since 6.1 a fix uderway? See: http://projects.info-pull.com/mokb/ MOKB-08-11-2006,CVE-2006-5824, MOKB-03-11-2006,CVE-2006-5679 Regards, Oliver

Is for these UFS bugs in FreeBSD since 6.1 a fix uderway? See: http://projects.info-pull.com/mokb/ MOKB-08-11-2006,CVE-2006-5824, MOKB-03-11-2006,CVE-2006-5679 Regards, Oliver

When trying to do a yum update, I am told I need more space in /boot. When I check the contents of /boot (ls -l /boot), there are no files. If I do a df -h, there is no available space yet it shows that it has a lot of used space. The fstab shows the following: # This file is edited by fstab-sync - see 'man fstab-sync' for details /dev/VolGroup00/LogVol00 /

This is CentOS-6x. I have cloned the HDD of a CentOS-6 system. I booted a host with that drive and received the following error: checking filesystems /dev/mapper/vg_voinet01-lv_root: clean, 128491/4096000 files, 1554114/16304000 blocks /dev/sda1: clean, 47/120016 files, 80115/512000 blocks /dev/mapper/vg_voinet01-lv_home: clean, 7429/204800 files, 90039/819200 blocks

Hello Gurus, Greetings. I have been assigned some work on the development of a migration tool. The requirement is that it has to migrate the data on a UFS/VxFs filesystem to an ext2 filesystem. What are the technical apects I will have to look into to achieve the same? Is it possible to change the on-disk structure of the UFS/VxFs filesystem to an ext2 filesystem? The question may

Hi All, One of my servers upon a restart today comes up with an error checking filesystems: fsck.ext3: no such file or directory while trying to open /dev/VolGroup-1/Logvol00. /dev/VolGroup-1/LogVol00. The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 filesystem (and not swap or ufs or something else), then

From: Raphael S. Carvalho <raphael.scarv at gmail.com> Wrote the documentation below. I think it would be good to push the doc to the wiki as soon as the UFS support gets merged. Unix Fast File System (UFS/FFS) 1/2 on Syslinux - (usage/install) ----- There is a confusion about the name of this file system, then I decided to contact the author who replied: "The name has always been

From: Raphael S. Carvalho <raphael.scarv at gmail.com> Change since v1: * Fix bug on dentry structure (thank you specification; btw, sarcasm), and consequently a bug on ufs_readdir. * Add readlink support (applied tests for symlinks whose destionation path were stored in blk pointers and the file itself). * Several improvements. Wrote the documentation below. I think it would be good to

Hello all. I am currently using ext3 0.0.5d with great success. I am a bit conflicted about what to tell the system regarding my root filesystem however. I have my root filesystem configured and working as an ext3 filesystem, but it is/was not without some fraught. Using RedHat 7.0, if you simply create your journal on the root file- system, figure out it's inode number, issue a lilo -R

Hello, I have been having an annoying problem with a multi-partition domain. This domain has a separate partition for : /, /home, /usr, /var, /tmp and /data. I created it using xen-tools and the custom partitionning scheme option. The partitions are inside a LVM. When I boot the domain, it mounts the / and swap partition but none of the others. Therefore it doesn''t work... I get the

On Fri, Oct 06, 2017 at 09:53:27AM +0200, Pino Toscano wrote: > On Thursday, 5 October 2017 23:49:26 CEST Richard W.M. Jones wrote: > > On Thu, Oct 05, 2017 at 06:55:53PM +0200, Pino Toscano wrote: > > > On Thursday, 5 October 2017 17:36:09 CEST Richard W.M. Jones wrote: > > > > /* We need to mount everything up in order to read out the list of > > > >