Bug 116360 - Couldn't continue installation after reboot (Minimal installation over SMB)
Summary: Couldn't continue installation after reboot (Minimal installation over SMB)
Status: RESOLVED FIXED
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: Installation (show other bugs)
Version: RC 1
Hardware: x86-64 All
: P5 - None : Normal
Target Milestone: ---
Assignee: Ruediger Oertel
QA Contact: Klaus Kämpf
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-09-10 20:10 UTC by Jörg Rüppel
Modified: 2005-09-13 13:23 UTC (History)
3 users (show)

See Also:
Found By: Other
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Yast2 Logfiles (173.17 KB, application/x-gzip)
2005-09-10 20:11 UTC, Jörg Rüppel 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Jörg Rüppel 2005-09-10 20:10:25 UTC 
Yast2 failed to mount CIFS installation media after reboot.

Bootet from a SuSE 10 Beta 1 CD, in Bootscreen selected Advanced Options,
XMB/CIFS install.

Pointed it to remote SMB share of RC1 CD1 and chose minimal installation.
Install went through until reboot, Yast2 came up in textmode and complained
about invalid filesystem on installation media.

/var/log/messages was full of CIFS error code -22. no username specified
although I tried it with anonymous login or explicit logins.
Comment 1 Jörg Rüppel 2005-09-10 20:11:00 UTC 
Created attachment 49528 [details]
Yast2 Logfiles
Comment 2 Michael Andres 2005-09-12 14:10:07 UTC 
The Yast2 log is full of:

Executing '/bin/mount' '-t' 'cifs' '-o' 
  'credentials=/var/tmp/TmpFile.SzjI7G,guest,ro,workgroup=workgroup' 
  '//192.168.5.3/H' '/var/adm/YaST/InstSrcManager/IS_CACHE_0x00000001/MEDIA'
stdout: mount: wrong fs type, bad option, bad superblock on //192.168.5.3/H,
stdout:        missing codepage or other error
stdout:        In some cases useful info is found in syslog - try
stdout:        dmesg | tail  or so
stdout: 
pid 6504 exited with status 32
Comment 3 Michael Andres 2005-09-12 14:52:23 UTC 
Jörg, could you please check
/var/adm/YaST/InstSrcManager/IS_CACHE_0x0000000*/DESCRIPTION/description.

Does the '=URL:' entry (usg. the 2nd line) contain correct user and password info?

--
Some SMB-wizard: What does 'missing codepage or other error' mean? Is it a
problem of the credentials or something completely different?
Comment 4 Guenther Deschner 2005-09-12 15:58:17 UTC 
Hm, very weird. The only possible scenario of this error message is - at least
for me - that the cifs-mount rpm is not installed at all. Could this be true ?
Comment 5 Jörg Rüppel 2005-09-12 23:23:31 UTC 
(In reply to comment #4)
> Hm, very weird. The only possible scenario of this error message is - at least
> for me - that the cifs-mount rpm is not installed at all. Could this be true ?

Confirmed.
Comment 6 Klaus Kämpf 2005-09-13 06:24:32 UTC 
How big is this package ? Which dependencies does it have ? 
 
It might be easiest to add cifs-mount to the minimal selection.
Comment 7 Olaf Hering 2005-09-13 07:20:22 UTC 
a vnc installation adds fvwm2, x11 to the package list.
the same has to be done for other install methods, like install via smb.
update Packages.ycp
Comment 10 Guenther Deschner 2005-09-13 07:57:11 UTC 
The cifs-mount package is very small and has no dependencies (especially not to
samba).
Comment 11 Klaus Kämpf 2005-09-13 07:58:55 UTC 
AJ, your call ;-)
Comment 12 Andreas Jaeger 2005-09-13 08:19:36 UTC 
Let's add it to the selections.  Stefan, please do so and then assign to Rudi.

Rudi, cifs-mount needs to be on CD1 as far as I can see.
Comment 13 Stefan Dirsch 2005-09-13 08:39:44 UTC 
done.
Comment 14 Ruediger Oertel 2005-09-13 13:23:28 UTC 
cifs-mount is already on CD1. 
so we can close this.