LinuxQuestions.org - fstab problems with second ext3 HDD

- Fedora (https://www.linuxquestions.org/questions/fedora-35/)

- - fstab problems with second ext3 HDD (https://www.linuxquestions.org/questions/fedora-35/fstab-problems-with-second-ext3-hdd-245418/)

fstab problems with second ext3 HDD

I added a 2nd HDD to my FC2 box. Created four partitions on new drive using

Code:

fdisk /dev/hdb

and

Code:

mke2fs -cv /dev/hdb3

for each. Here is my setup:

Code:

[root@athenasrv /]# fdisk -l  /dev/hdb

Disk /dev/hdb: 30.0 GB, 30003240960 bytes

255 heads, 63 sectors/track, 3647 cylinders

Units = cylinders of 16065 * 512 = 8225280 bytes

  Device Boot      Start        End      Blocks  Id  System

/dev/hdb1  *          1        123      987966  83  Linux

/dev/hdb2            124        367    1959930  83  Linux

/dev/hdb3            368        1097    5863725  83  Linux

/dev/hdb4            1098        3647    20482875  83  Linux

So I can mount them with commands like

Code:

mount /dev/hdb3 /SCR

and everything fine:

Code:

[root@athenasrv /]# df -h

Filesystem            Size  Used Avail Use% Mounted on

/dev/hda2            7.3G  3.7G  3.3G  54% /

/dev/hda1              97M  7.6M  85M  9% /boot

none                  110M    0  110M  0% /dev/shm

/dev/hdb4              20G  4.0K  19G  1% /MZK

/dev/hdb3            5.6G  69M  5.2G  2% /SCR

However, I tried adding the four partitions to /etc/fstab and I get errors on reboot... fsck complains that these are not ext2 filesystems...

Code:

[root@athenasrv /]# cat /etc/fstab

LABEL=/                /                      ext3    defaults        1 1

LABEL=/boot            /boot                  ext3    defaults        1 2

none                    /dev/pts                devpts  gid=5,mode=620  0 0

none                    /dev/shm                tmpfs  defaults        0 0

none                    /proc                  proc    defaults        0 0

none                    /sys                    sysfs  defaults        0 0

/dev/hda3              swap                    swap    defaults        0 0

/dev/cdrom              /mnt/cdrom              udf,iso9660 noauto,owner,kudzu,ro 0 0

/dev/fd0                /mnt/floppy            auto    noauto,owner,kudzu 0 0

/tmp                    /dev/hdb1              ext3    defaults        1 3

/home                  /dev/hdb2              ext3    defaults        1 4

/SCR                    /dev/hdb3              ext3    defaults        1 5

/MZK                    /dev/hdb4              ext3    defaults        1 6

I usually have to go into maintenance mode, comment out all /dev/hdb* entries and reboot. Then everything ok. Also for /dev/hdb1 and /dev/hdb2 I wanted them to replace the current /tmp and /home according to instructions from item #1 in this link
www dot linux-mag dot com /cgi-bin/printer.pl?issue=2000-03&article=tech_support
but it didn't work out... Any ideas?

With your mke2fs command above, you created ext2 filesystems. Then in your fstab you put them as ext3. Try putting them in as ext2 in fstab.

Thanks Darthtux. You made me read the mke2fs manpage. So I tried re-entering the partitions to /etc/fstab as ext2... no luck. Then I tried to make them ext3 with

Code:

mke2fs -j /dev/hdb3

and then editing /etc/fstab to show ext3 for /dev/hdb3 etc...
That did not work either.

Here is the error message I keep getting on reboot:

Code:

fsck.ext2/MZK

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 the superblock is corrupt, and you might try running e2fsck with an alternate superblock:

e2fsck -b 8193  <: Is a directory while trying to open /MZK device>

Interestingly enough, after booting with all /dev/hdb* commented out in fstab I can

Code:

mount -t ext2 /dev/hdb3 /MZK

Code:

mount -t ext3 /dev/hdb3 /MZK

with no problem. In fact I can read/write to /MZK after that without complaints from linux...

In the line in /etc/fstab make the numbers at the end of the line 0 0
That way they won't be checked at boot. Not a solution as to why but it should stop the error message.