Bug 115551 - unable to access non reisersfs drives
Summary: unable to access non reisersfs drives
Status: RESOLVED WORKSFORME
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: Installation (show other bugs)
Version: Beta 4
Hardware: i686 SUSE Other
: P5 - None : Minor
Target Milestone: ---
Assignee: E-mail List
QA Contact: Klaus Kämpf
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-09-07 05:43 UTC by rob welch
Modified: 2006-08-17 07:33 UTC (History)
0 users

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


Attachments
amended fstab (1.22 KB, application/octet-stream)
2005-09-08 06:49 UTC, rob welch
Details
result of clicking on the "my computer" icon (122.98 KB, image/png)
2005-09-08 07:05 UTC, rob welch
Details
error that is reported when accessing drives (16.34 KB, image/png)
2005-09-08 07:08 UTC, rob welch
Details
YaST2logs (142.03 KB, application/x-gunzip)
2005-09-08 07:45 UTC, rob welch
Details
hwinfo (212.02 KB, text/plain)
2005-09-08 07:45 UTC, rob welch
Details

Note You need to log in before you can comment on or make changes to this bug.
Description rob welch 2005-09-07 05:43:39 UTC
After installation I can open the desktop icon labeled "my computer" and see all
of the partitions on my machine.  I have NTFS, FAT32, and reisers partitions. 
Only the reisers partitions are accessible.  If i try to open the FAT32 disk I
get the following:

Could not mount device.
The reported error was:
mount: can't find /dev/sdb1 in /etc/fstab or /etc/mtab

Shouldn't the drives be accessible?  Why list them if not?  I tried to edit the
/etc/fstab file to be able to access this partition but was unsuccessful.
Comment 1 Jiří Suchomel 2005-09-07 07:02:03 UTC
Please attach yast log files:

http://www.opensuse.org/index.php/Bug_Reporting_FAQ#YaST


Thomas, please request another necesary informations.
Comment 2 Thomas Fehr 2005-09-07 08:28:39 UTC
This has nothing to do with yast2-storage or yast2 at all, the data for these
icons comes from HAL.
Comment 3 Danny Al-Gaaf 2005-09-07 08:39:46 UTC
Which desktop you use? KDE? GNOME? This works for me with KDE. Sounds like gnome 
problem.
Comment 4 Thomas Fehr 2005-09-07 08:44:49 UTC
This may also depend on the fstab content, maybe it only works if the filesystems
have an entry in /etc/fstab
Comment 5 Danny Al-Gaaf 2005-09-07 08:48:43 UTC
Not sure, but there was a bug in GNOME with partitions which are mounted but not 
in the fstab. If this is a problem under GNOME reassign this to the gnome guys.
Comment 6 rob welch 2005-09-08 06:49:17 UTC
Created attachment 49151 [details]
amended fstab

I fixed the problem by using the line from a knoppix generated fstab and and
pasting into the SuSE fstab.  The drive that I added is at the bottom of the
file and is for /dev/sdb1.  Screen shots to follow.
Comment 7 rob welch 2005-09-08 06:57:36 UTC
file:///home/rob/snapshot1.png
Comment 8 rob welch 2005-09-08 07:05:22 UTC
Created attachment 49152 [details]
result of clicking on the "my computer" icon

All my drives and partitions are shown.  Only the reisers drives are accessible
hdb1 (6.2G media) with kanotix installed, hdb3 (11G media) with SuSE 10.0 beta
4 installed, and sda1 (common linux) my linux files and stuff.
Comment 9 rob welch 2005-09-08 07:08:16 UTC
Created attachment 49153 [details]
error that is reported when accessing drives 

This is the same error that I was getting when trying to access the drive sdb1.
 This shot was taken of the same error reported when trying to access an NTFS
partition.
Comment 10 rob welch 2005-09-08 07:30:34 UTC
What's interestig is if you look at my fstab file, it contained an entry for
/dev/sda1 (common linux partition) so it does not appear to be a scsi issue.  It
seems to me that if they are listed as drives on my computer then I should be
able to mount them.  But they were like curtains hanging on the wall but when
you open them there is only a brick wall wall where a window should be.

Not sure that it is a YaST2 problem but figured that it may be an issue with the
install setup and configuration done by YaST2.

What additional info or log files do you need?

Computer info:
AMD Athlon 1800
Iwill XP333 MB
512 Mb ram
SiS 315 AGP video card (not supported but VESA works when booted no frame buffer)
2x 60 GB IDE hard drives
1 IDE DVD-rom
1 IDE DVD writer
2x 32 GB SCSI hard drives
1 SCSI CD-r
Network card and SCSI card


Comment 11 rob welch 2005-09-08 07:45:27 UTC
Created attachment 49156 [details]
YaST2logs
Comment 12 rob welch 2005-09-08 07:45:57 UTC
Created attachment 49157 [details]
hwinfo
Comment 13 Danny Al-Gaaf 2005-09-08 08:33:00 UTC
looks like a problem  of KDE, also if I can't reproduce this.
Comment 14 Dirk Mueller 2005-09-08 08:46:58 UTC
can't actually follow the whole bug, but perhaps you can have a look at bug 
86991 and bug 102918 and see if you can find some correlation there? 
 
 
Comment 15 Stephan Kulow 2006-08-17 07:33:47 UTC
not able to reproduce