search for: hda5

...ting xattr-s same as --delete for files, because it seems deletion of xattr don't sync, however it is synced when data of file change, see example below. Maybe this is a bug or maybe this is ok? System gentoo attr-2.4.32, rsync form today cvs. -- Regards Stanislaw Gruszka stasiu@sg /mnt/hda5/export $ echo "data" > file stasiu@sg /mnt/hda5/export $ attr -s attr1 -V val1 file Attribute "attr1" set to a 4 byte value for file: val1 stasiu@sg /mnt/hda5/export $ attr -s attr2 -V val2 file Attribute "attr2" set to a 4 byte value for file: val2 stasiu@sg /m...

> [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

Hello, Sorry for the off-topic, but I've just installed CentOS 5 on my home box and I want to put the journal on another drive. I created a software RAID-1 device, /dev/md1, and formatted an ext3 file system on it. Now I want to move the journal to /dev/hda5. I've googled for this and the process appears to be: mkfs.ext3 -b 4096 -O journal_dev /dev/hda5 mkfs.ext3 -b 4096 -J device=/dev/hda5 /dev/md1 Now, here's the fun part. I've already put data on /dev/md1. Will the above commands reformat /dev/md1? If so, is there an easy way to move t...

Hi to all. I''m installed XEN3.1 correctly but I''m some problem to start it. XEN start but I received this message: VFS: Cannot open root device "hda5" or unknown-block(0,0) Please append a correct "root=" boot option Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) This is strange because my grub is configured like this: #XEN3.1-2.6.18 title XEN3.1-2.6.18 #root (hd0,4) kernel (hd0,4)/boot/xen...

...answer to this question but I have not (yet). Any assistance or expert knowledge is greatly appreciated! PROBLEM: mounting an ext3 volume 'read only' results in a different md5sum hash value for the volume than when the same volume is *not* mounted SCENARIO: - when I hash unmounted /dev/hda5 using 'md5sum /dev/hda5' I get value XXX. - when I hash mounted /dev/hda5 using 'md5sum /dev/hda5' I get value 'YYY'. MISC: - no matter how I mount the volume read only I get the same result - differing hash values! <example1> mount /dev/hda5 -o ro /mnt/poop <ex...

...e. I used: http://www.kernel.org/pub/linux/utils/boot/syslinux/Testing/syslinux-3.81-pre13.zip Background: I started with a 'normal' multi-OS boot setup as follows: MBR - syslinux hda1 - 24G - [0c] - FAT32 - WinXP (Encrypted via TrueCrypt) hda2 - 53G - [0f] - Extended hda5 - 0.5G - [06] - [boot] FAT16, boots syslinux menu hda6+ --- Various_Other_Partitions, none with [boot] active --- All was booting & working fine but I wanted to encrypt the WinXP boot partition (hda1) with TC. Doing so would entail: - TC replacing the MBR boot code with its own boot loader -...

Destroy ACL-s on destination when no ACL-s differens between source and destination. Bug is somehow related with function send_file_name() called with negative file descriptor f. There is no such bug in 2.6.9 version, but there options "-X -A --deleted" can't be used (we have "Internal error: wrong write used in receiver."). If I fix this, avoid calling send_acl() &

...(priority -2) Why my root filesystem (ext3) is seen by the kernel as an ext2 filesystem ? - the second trouble... When I restart the linux box (a Toshiba 4060 XCDT), the root filesystem seems to be not clean and a fsck is done... Why ? For information : Weierstrass:[~] > cat /etc/fstab /dev/hda5 / ext3 defaults 1 1 /dev/fd0 /mnt/floppy auto noauto,owner 0 0 /dev/cdrom /mnt/cdrom iso9660 noauto,owner,ro 0 0 none /proc proc defaults 0 0 non...

I'm running RH7.1 and Samba 2.2.2 . I would like to offer a VFAT partition on the server hard drive for universal read-write access. I mount the partition in fstab with /dev.hda5 /sys vfat defaults,rw,uid=1001,gid=1001 0 0 It mounts fine and shows up on the Windows 98 machine and can be opened. I can't write to it however. User and group 1001 are smbuser account, and they show up in /ls -l as the owner and group. security=share I'm logging in from host...

To test CentOS 5, I loaded from DVD adding it to a system at home running Fedora Core 7 T2. Partition Layout is: /dev/hda1 - / for the RH7T2 system /dev/hda2 - /home /dev/hda3 - swap /dev/hda4 - extended /dev/hda5 - / for CentOS 5 The system loaded cleanly and gave me the opportunity to tell grub about the other system. CentOS boots fine. Grub Stage 2 will show me both systems. However, If I choose the FC7T2 system I get the following output: --------------------------------------------------------- Boo...

>That should work, *IF*: > >a) hda5 is a FAT12/16 filesystem; >b) hda5 is <= cyl 1024. > > -hpa I got thinking booting off a logical partition might not be allowed, so I changed the LEAF/Bering logical partition to a primary, hda4. Then I ran "syslinux d:" from a Win98SE DOS-box to (try to) initialize the part...

...- Nice boot-device handling overall =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- My working & booting syslinux 3.80 setup, pre altmbr: MBR: from syslinux 3.80 ldlinux.sys: from syslinux 3.80 hda1 - 24G - [0c] - FAT32 - WinXP (Encrypted via TrueCrypt) hda2 - 53G - [0f] - Extended hda5 - 0.5G - [06] - [boot] FAT16, boots syslinux menu hda6+ --- Various_Other_Partitions, none with [boot] active --- AltMBR Purpose: I want to employ the altmbr to have hda5 always be the boot partition that syslinux loads from, in a setup where hda5 will *not* have the boot flag set, but hda1 *wil...

I have been using the LEAF Bering firewall for a year or so. It boots with Syslinux 1.75. But Bering is too large for a 1440KB floppy, so it formats the diskette as 1680KB. Recently I found a small Compaq 2266 box to replace a larger Compaq 7170 to run the firewall. But when I try to boot the Bering diskette on the 2266 I get the following message: Loading Linux ............ Boot failed:

...to hit the reset button. When the system tried to come up, it couldnt mount root. It dropped me straight into single user mode. No problem, I thought to myself. See, I am scheduled to take my RHCE on the 25th and been practicing reviving sick filesystems. The first command I ran was fsck.ext2 /dev/hda5. It complained that it couldn't run. I figured that the superblock must have been corrupt. I ran debugfs /dev/hda5 to see the listing of superblocks. Then I typed fsck.ext2 -b 32768 /dev/hda5 and it found a bunch of errors that it said it fixed. Great, me thinks. I'll reboot and be back in...

Hi, Stephen and Jeff, Thanks. But the problem got debugged&fixed, the answer was post on fedora-list about 2 weeks ago. The problem is: the /etc/blkid.tab file works as an old unappropriate disk partitions cache for fsck|blkid commands when stystem image is installed to a different arch (scsi->ide) machine, the old cache will mislead fsck|blkid at the first run and only the first run,

Hi, I work on a solution for school including Eyeos and thinclient, iwant to convert syplinux ISO into syplinux Pxeboot, is there a way to do that ? Actually i'm using PXELINUX, When I boot the SYPLINUX.GZ (extract from the iso) I get this error : VFS: Cannit open root device "<NULL>" or unknown-block(3,5) Please append a correct "root=" boot option Kernel panic -

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 hda3, but it fails to boot. Did syslinux even start? What did it tell you? Is any of these partitions activated? Which system wrote the MBR? PQMAGIC? Dos? ...? > WHAT CA...

...n irq 15 Probing IDE interface ide2... Probing IDE interface ide3... Probing IDE interface ide4... Probing IDE interface ide5... hda: max request size: 1024KiB hda: 398297088 sectors (203928 MB) w/8192KiB Cache, CHS=24792/255/63, UDMA(133) hda: cache flushes supported hda: hda1 hda2 hda3 hda4 < hda5 hda6 hda7 hda8 hda9 hda10 hda11 hda12 hda13 hda14 hda15 > hdc: max request size: 1024KiB hdc: 398297088 sectors (203928 MB) w/8192KiB Cache, CHS=24792/255/63, UDMA(133) hdc: cache flushes supported hdc: hdc1 hdc2 hdc3 hdc4 < hdc5 hdc6 hdc7 hdc8 hdc9 hdc10 hdc11 hdc12 hdc13 hdc14 hdc15 > A...

...d fine, but '/' no longer shows up in 'df -h'. More importantly, 'mount' shows '/' mounted as type 'auto', not 'ext3'. What have I done wrong? A few lines from /etc/fstab: /dev/hda1 / auto defaults 1 1 /dev/hda5 /home auto defaults 1 2 /dev/hda10 /usr auto defaults 1 2 /dev/hda6 /usr/local auto defaults 1 2 /dev/hda8 /var auto defaults 1 2 /dev/hda9 /var/tmp...

Hello, I'm new in ext3. I installed RH7.2 with ext3. For a short time it worked properly, but when I compiled the linux kernel (2.4.9-13) from RH package, the old kernel didn't boot again (I didn't change anything with the old binary). I downloaded kernel 2.4.14 and ext3 patch for this version. After the compilation and installation I rebooted the system. I got answer something