Re: [Cooker] diskdrake prob followed by maint session problem with solution
From: John Danielson, II [EMAIL PROTECTED] Any system that has EVER had a file system with Windows or DOS on it has the following part structure. Part #s 1-4 can be primary. Part #5 is always an extended part table to hold logical drives. Parts 6 and up can be logicals. | | And Windows allows for 4 primaries, not 3. So a mixed system or a | migrators system will have a mess. | You have missread the partition tables, or how it works... Windows/dos (or actually te partitioning scheme) does allow for 4 primaries, BUT the extended partition counts as one primary. You dont belive me? If so, it's easy to test ... 1. Create 4 primary partitions. (make sure you leave some emty space on the disk, for example 4 x 1GB partitions on a 10 GB disk leaves you with 6 GB of free space on the disk...) 2. Now try to make a extended partition... IT WON'T WORK 3. Remove one of the primary partitions. Now you can create an extended partition that uses tthe free space on the disk, that also allows you to make logical partitions... Thomas
Re: [Cooker] diskdrake prob followed by maint session problem with solution
John Danielson, II [EMAIL PROTECTED] writes: The commented line is what I had to pull to get the machine to boot past an ext2 fsck that said it could not find a superblock when I tried to boot the machine into Linux. [...] I was trying to use Diskdrake from the GUI when this happened, as any newbie would. so, as far as i understand, the bug is: when creating a partition on a live system with diskdrake, it writes the partition table, it writes the fstab, *but* it doesn't manage to format the partition because it wants to reboot first. is that it? if that's the pb, I thought it was fixed, *unless* you did resize a partition first.
Re: [Cooker] diskdrake prob followed by maint session problem with solution
Pixel wrote: John Danielson, II [EMAIL PROTECTED] writes: Any system that has EVER had a file system with Windows or DOS on it has the following part structure. Part #s 1-4 can be primary. Part #5 is always an extended part table to hold logical drives. Parts 6 and up can be logicals. it really seems like we can't agree on terminology or ??? % fdisk -l /dev/sda [...] Device BootStart EndBlocks Id System /dev/sda1 1 2 16033+ 83 Linux /dev/sda2 * 3 263 2096482+ 83 Linux /dev/sda3 264 276104422+ 83 Linux /dev/sda4 277 1106 9755 Extended /dev/sda5 277 340514048+ 83 Linux /dev/sda6 341 353104391 82 Linux swap ... /dev/sda11 1013 1106755023+ 83 Linux parts #5-#11 are included in #4 And Windows allows for 4 primaries, not 3. So a mixed system or a migrators system will have a mess. You are using SCSI, me IDE also. fdisk -l /dev/hda Disk /dev/hda: 255 heads, 63 sectors, 9729 cylinders Units = cylinders of 16065 * 512 bytes Device BootStart EndBlocks Id System /dev/hda1 * 1 1021 8201151 83 Linux /dev/hda2 1022 9729 69947010f Win95 Ext'd (LBA) /dev/hda5 1022 1071401593+ 82 Linux swap /dev/hda6 2960 3980 8201151 83 Linux /dev/hda7 1072 2959 15165297 83 Linux /dev/hda8 3981 5313 10707291 83 Linux /dev/hda9 5314 8513 25703968+ 83 Linux /dev/hda10 8514 8901 3116578+ 83 Linux /dev/hda11 8902 9729 6650878+ 83 Linux Partition table entries are not in disk order [root@ root]# fdisk -l /dev/hdb omitting empty partition (5) Disk /dev/hdb: 255 heads, 63 sectors, 4865 cylinders Units = cylinders of 16065 * 512 bytes Device BootStart EndBlocks Id System /dev/hdb1 * 1 648 5205028+ 83 Linux /dev/hdb2 649 698401625 82 Linux swap /dev/hdb3 699 4865 33471396f Win95 Ext'd (LBA) /dev/hdb5 700 1606 7285414+ 83 Linux /dev/hdb6 1607 2368 6120702 83 Linux /dev/hdb7 2369 4865 20057121 83 Linux [root@ root]# fdisk -l /dev/hdd Disk /dev/hdd: 255 heads, 63 sectors, 7297 cylinders Units = cylinders of 16065 * 512 bytes Device BootStart EndBlocks Id System /dev/hdd1 1 1021 8201151b Win95 FAT32 [root@ root]# where anything based on DOS or Windows sticks the extended is based on how many Primaries there are: What fdisk saw on theHD after diskdrake was done as I described was: hda1 / hda4 Extended hda5 /cookermirror (type unknown) as in /etc/fstab but hda5 was unformatted and marked as Ext2 when I told Diskdrake to use Ext3 here is the /etc/fstab [root@ root]# cat /etc/fstab /dev/hdb1 / ext3 defaults 1 1 # /dev/hda5 /Cookermirror ext3 noauto 1 2 none /dev/pts devpts mode=0620 0 0 /dev/hdb7 /home ext3 defaults 1 2 none /mnt/cdrom supermount dev=/dev/scd0,fs=auto,ro,--,iocharset=iso8859-1,codepage=850,umask=0 0 0 none /mnt/floppy supermount dev=/dev/fd0,fs=auto,--,iocharset=iso8859-1,sync,codepage=850,umask=0 0 0 /dev/hdd1 /mnt/hd auto user,iocharset=iso8859-1,kudzu,codepage=850,noauto,umask=0,exec 0 0 /dev/hda1 /newslash ext3 defaults 1 2 none /proc proc defaults 0 0 none /tmp tmpfs defaults 0 0 /dev/hdb6 /usr ext3 defaults 1 2 /dev/hdb5 /var ext3 defaults 1 2 /dev/hdb2 swap swap defaults 0 0 [root@ root]# The commented line is what I had to pull to get the machine to boot past an ext2 fsck that said it could not find a superblock when I tried to boot the machine into Linux. BTW, Supermount WORKS on this P4 box, even in stock Mandrake 9.0. I was trying to use Diskdrake from the GUI when this happened, as any newbie would. John.
Re: [Cooker] diskdrake prob followed by maint session problem with solution
John Danielson, II [EMAIL PROTECTED] writes: Soemthing that just happened to me made me think that documenting a particular recovery process would help many people: How to get your /etc/fstab file editted from a floppy boot when your partitioning is set up to have a seperate /usr part: Go into maintenance shell, as the e2fsck fails due to it thinking from the /etc/fstab that a partition is /dev/hda5 when it is /dev/hda6 (or some such radically wrong number, part 5 should always be the extended part table). [...] Just a thought, but could flesh out the procedure if wanted for newbie to know how to edit /etc/fstab from what a floppy boot drops to when an unrecoverable bad superblock error is triggered by diskdrake assigning /dev/hda5 to first extended part and not allowing for the extended part table(and then erroring as it is created, but still offering to write the /etc/fstab, which I did let it do last night at 1 AM). diskdrake defaults optional things like /cookermirror to extended\logical type, but fails to set up an exclusion of part 5 for the extended part table and writes a /dev/hda5 entry in /etc/fstab for the new part if it is the first logical created on a physical disk-- sheesh. Then it decides the extended part table has a bad superblock because is trying to use it as a partition that can be read to and written to directly. i'm missing something. what is this part 5 being special?
