Bug 146511

Summary: update error: "Root partition in /etc/fstab has an invalid root device. It is currently mounted as /dev/sdb3 but listed as /dev/sdb2"
Product: [openSUSE] SUSE Linux 10.1 Reporter: Tomislav Stambolija <tstambolija>
Component: Update ProblemsAssignee: E-mail List <bnc-team-screening>
Status: RESOLVED WONTFIX QA Contact: Klaus Kämpf <kkaempf>
Severity: Major    
Priority: P5 - None    
Version: Beta 2   
Target Milestone: ---   
Hardware: i686   
OS: SuSE Linux 10.0   
Whiteboard:
Found By: Customer Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

Description Tomislav Stambolija 2006-01-29 14:29:23 UTC 
error: "Root partition in /etc/fstab has an invalid root device. It is currently mounted as /dev/sdb3 but listed as /dev/sdb2"

system descr:
  sempron, 2xSATA
  Suse 10.0 installed on /dev/sdb3 on reiserfs
  Grub installed by suse 10.0
  sdb2 is an ext3 partition and contains no OS (just archive)
 
Update properly recognize installed OS (probably from grub) but when choose partition to update, message as above apeared.
Comment 1 Martin Lasarsch 2006-01-30 10:10:06 UTC 
please provide:

/etc/fstab of the old system
fdisk -l
/var/log/YaST/* from the installation system
Comment 2 Michael Gross 2006-02-07 13:21:53 UTC 
Please reopen this bug if you can provide the requested information.
Comment 3 Stephan Kulow 2008-06-25 09:35:03 UTC 
mass reopening all SuSE Linux bugs that are set to REMIND+LATER to change the resolution to WONTFIX (adapting to new policy)
Comment 4 Stephan Kulow 2008-06-25 09:37:06 UTC 
mass reopening all SuSE Linux bugs that are set to REMIND+LATER to change the resolution to WONTFIX (adapting to new policy)
Comment 5 Stephan Kulow 2008-06-25 09:41:59 UTC 
mass reopening all SuSE Linux bugs that are set to REMIND+LATER to change the resolution to WONTFIX (adapting to new policy)
Comment 6 Stephan Kulow 2008-06-25 09:53:23 UTC 
Closing old LATER+REMIND bugs as WONTFIX - if you still plan to work on it, feel free to reopen and set to ASSIGNED.

In case the report saw repeated reopen comments, it's due to bugzilla timing out on the huge request ;(