search for: lba32

...otalclust 1 simon > On Tue, 21 Sep 2004 18:42:18 +0200, you wrote: > > > On Tue, 21 Sep 2004 02:21:00 -0700, you wrote: > > > > > Rein, > > > > > > You're gonna love this. I think I figured it out. It turns out > that I > > > had "lba32" enabled in my lilo.conf. I don't know much about > windows, > > > but I'm going to guess that windows98 doesn't play well with lba32. > > > > > > Thanks for your help though. I hope this will help people who have > the > > > same problem...

...No, it's a geometry issue on legacy BIOS/DOS Disk Labels (Partition Table Format) aka "Basic Disc" in NT5+ (2000+) when both NT and Linux share the disk for booting. Microsoft never standardized how geometry should be handled after NT4.0 Service Pack 4 (SP4) other than using legacy LBA32 -- i.e., always assuming Sectors/Heads of 63/255. In NT5+, this is what it does on a "Basic Disc" which cannot store geometry information, at least through NT5.1 (XP/2003) Service Pak 1 (SP1). Unfortunately, assuming LBA32 is not compatible with Extended Int13h Disk Services. And for b...

...inux/Isolinux. Any suggestions would be greatly appreciated. When I tried to convert it I made sure that the kernel and initrd had proper DOS names and such. -Michael =:LILO.CONF:= prompt timeout=10 default=linux boot=/dev/hdc disk=/dev/hdc bios = 0x80 map=/boot/map install=/boot/boot.b vga=0 lba32 image=/boot/vmlinuz-2.4.18-14 label=linux read-only ramdisk=12000 initrd=/boot/rd.img append="hda=ide-scsi root=/dev/ram0 quiet" =:END LILO.CONF:=

hi. i'm hitting a wall each time i try to format a 3 terabyte partition. i'm able to create the partition using parted but whenever i try to create a 3 terabyte xfs or jfs or ext3 filesystem, the mounted filesystem created is only 1 terabyte. i tried centos x86 and x86_64 4.0 but i always hit a 1 terabyte limit. please help.

...ally used on it, and is a 160 GB hard drive, 147 GB formatted. The /boot (hde6) partition starts at approximately the 56 GB boundary, the / (hde9) partition starts at approximately the 76 GB, and the swap drive starts at approximately the 106 GB boundary. Is it possible that I needed to turn on LBA32 as an install option, since there was a screen where I could have checked it but did not ? Is it possible that I needed to tell the install, when choosing my partitions for /boot,/, and swap that this was a Raid controller, event though I am not using Raid with it, since I noticed a Raid button...

...0 0 pts /dev/pts devpts mode=0622 0 0 /dev/fd0 /mnt/auto/floppy auto user,noauto,exec,umask=000 0 0 /dev/cdrom /mnt/auto/cdrom auto user,noauto,exec,ro 0 0 /dev/hda1 / ext2 defaults 0 0 cp /etc/lilo.conf /mnt/hda/etc and modified it like this (basic, to improve) lba32 boot=/dev/hda prompt timeout=30 default=Knoppix image=/vmlinuz append="lang=us quiet screen=800x600 desktop=xfce BOOT_IMAGE=Knoppix" root=/dev/hda1 label=Knoppix read-write (PS: BOOT_IMAGE flag is parsed by init script in /etc/rcS.d/S00...-autoconfig". if you set it to expert you go...

I have a Debian system from a Knoppix distribution. I started out with ext2 but decided to change to ext3. tune2fs -j OK. However the system boots with a warning ....ext3 mounted as ext2. proc/mounts confirms this and no journal is running. So I have to make an initrd. Did so using instructions in the Debian Reference and this did not change anything. Any attempt to use the img produced was a