Bug 151344 - minimal install fails on reiserfs partition
Summary: minimal install fails on reiserfs partition
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 4
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Mike McLean
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2005-03-17 03:36 UTC by Zlatin Balevsky
Modified: 2007-11-30 22:11 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2005-03-17 11:16:27 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
install.log (65.54 KB, text/plain)
2005-03-17 03:38 UTC, Zlatin Balevsky
no flags Details
anaconda-ks.cfg (846 bytes, text/plain)
2005-03-17 03:39 UTC, Zlatin Balevsky
no flags Details
install.log.syslog (655 bytes, text/plain)
2005-03-17 03:39 UTC, Zlatin Balevsky
no flags Details
grub.conf (655 bytes, text/plain)
2005-03-17 03:41 UTC, Zlatin Balevsky
no flags Details

Description Zlatin Balevsky 2005-03-17 03:36:56 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.6) Gecko/20050302 Firefox/1.0.1 Fedora/1.0.1-1.3.2

Description of problem:
Attempting a minimal install on a reiserfs parition formatted through anaconda fails to boot.

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. Create a reiserfs partition during installation and format it
2. Select minimal install
3. Boot system
  

Actual Results:  The booting sequence hangs, the last message output is that kernel is unable to mount vfs root on uknown filesystem, superblock(1,3)

Expected Results:  Normal bootup sequence

Additional info:

When booting in rescue mode, the rescue kernel successfully mounts the partition, as well as other reiserfs partitions created either manually or through previous versions of anaconda.  The FC3 kernel also mounts the partition successfully.

Everything works fine if the partition is ext3

Comment 1 Zlatin Balevsky 2005-03-17 03:38:27 UTC
Created attachment 112071 [details]
install.log

Comment 2 Zlatin Balevsky 2005-03-17 03:39:05 UTC
Created attachment 112072 [details]
anaconda-ks.cfg

Comment 3 Zlatin Balevsky 2005-03-17 03:39:44 UTC
Created attachment 112073 [details]
install.log.syslog

Comment 4 Zlatin Balevsky 2005-03-17 03:41:07 UTC
Created attachment 112074 [details]
grub.conf

This is the original grub.conf; I had to modify it by adding my fc3 kernel in
order to boot the system

Comment 5 Zlatin Balevsky 2005-03-17 03:43:41 UTC
This is the same system as in bug #151223, the partition is created on a
secondary master while the bootloader is created on the MBR of the primary master.

Comment 6 Zlatin Balevsky 2005-03-17 04:36:53 UTC
I repeated the process on a reiserfs partition created by mkfs.reiserfs from
fc3.  Startup did not succeed, here is the exact error message:

RAMDISK: Compressed image found at block 0
RAMDISK: Ran out of compressed data
Invalid Compressed format (err=1)
Kernel panic: not syncing VFS: unable to mount root fs on unknown block (22,2)

Comment 7 Paul Nasrat 2005-03-17 11:16:27 UTC
reiserfs is totally, 100% unsupported.  Boot with "linux reiserfs"
at the boot: prompt will let you make new reiserfs filesystems
in the installer.  Bugs filed when you use this will be closed
WONTFIX.


Comment 8 Joost 2005-06-25 09:18:11 UTC
I found a workaround for the problem. I booted in rescue mode using the cd,
removed grub and installed grub from the FC3 distro. You may need the
--noscripts option to get rid of the 'scriptlet failed errors' with rpm. Then I
did a "grub-install /dev/hda" and everything worked like a charm.
Note that reiserfs is not compatible with selinux because it does not support
extended attributes (yet). You can disable it with the boot option selinux=0.

It seems that grub-0.95-13(FC4) broke reiserfs support compared to grub-0.95-3(FC3).

I have been using reiserfs on RH/fedora for years without problems and suddenly
its broken. It is part of the kernel and imho it should at least be functional.
Please reopen.



Note You need to log in before you can comment on or make changes to this bug.