[opensuse] can't access Windows partition from SuSE 10.2
I have a PC with XP and SuSE 10.2 in a dual boot setup. I want to be able to access a FAT32 partition from SuSE. In the past that was fairly easy and I remember previous versions automatically detecting and mounting the windows partitions during the SuSE installation. Now I don't see the FAT32 partition from SuSE. I tried manually mounting but that just gives an error message about the resource being busy (or something like that). I found http://en.opensuse.org/Access_Your_Windows_Files and tried adding a line to fstab but I get a similar error message on boot and still I can't access the FAT32 partition. I tried Google and the openSUSE site but didn't find anything useful there. I even tried searching this list. Can anyone please help? Damon Register -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Hi, On 5/28/07, Damon Register <damon.register@comcast.net> wrote:
I have a PC with XP and SuSE 10.2 in a dual boot setup. I want to be able to access a FAT32 partition from SuSE. In the past that was fairly easy and I remember previous versions automatically detecting and mounting the windows partitions during the SuSE installation.
Now I don't see the FAT32 partition from SuSE. I tried manually mounting but that just gives an error message about the resource being busy (or something like that).
Strange, I have no problem with FAT32 partitions. They were autodetected during installation and I just renamed mounting points. This is what I have in the fstab (I have relatevly old IDE disk) /dev/hda1 /winc vfat users,gid=users,umask=0002,utf8=true 0 0 /dev/hda5 /wind vfat users,gid=users,umask=0002,utf8=true 0 0 -- Mark Goldstein -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Monday 28 May 2007 09:37, Damon Register wrote:
I have a PC with XP and SuSE 10.2 in a dual boot setup. I want to be able to access a FAT32 partition from SuSE. In the past that was fairly easy and I remember previous versions automatically detecting and mounting the windows partitions during the SuSE installation.
Now I don't see the FAT32 partition from SuSE. I tried manually mounting but that just gives an error message about the resource being busy (or something like that).
If the error message is that the resource (in this case a disk partition) is busy, then just about the only thing that could indicate is that the partition is already mounted. (At least I can't think of another condition within the system that could lead to that response.) So probably the file system is mounted and you can see where (on which directory) by using the "mount" or "df" commands. The other possibility is that you've mistaken one of your Linux disk volumes (partitions) for the FAT32 partition, and are trying to (re-) mount that. You can verify what's on a disk with the "file" command, provided you give the "-s" option (otherwise it tells you that the target is a disk): % file /dev/sda1 /dev/sda1: block special (8/1) For this, however, you'll probably need root permissions. # file -s /dev/sda1 /dev/sda1: ReiserFS V3.6 block size 4096 (mounted or unclean) num blocks 73254384 r5 hash Note, too, that the fact that file system is mounted (or was not successfully unmounted the last time it was used) is noted (not all file systems types get this extra indication, however; XFS does not, e.g.). When in doubt, you can brute-force this to find the right partition: First, the SCSI or SATA drives: # file -s /dev/sd* /dev/sda: x86 boot sector /dev/sda1: ReiserFS V3.6 block size 4096 (mounted or unclean) num blocks 73254384 r5 hash /dev/sdb: x86 boot sector, code offset 0x48 /dev/sdb1: SGI XFS filesystem data (blksz 4096, inosz 256, v2 dirs) /dev/sdb2: x86 boot sector, Microsoft Windows XP MBR /dev/sdb3: Linux/i386 swap file (new style) 1 (4K pages) size 1048240 pages /dev/sdb4: x86 boot sector, extended partition table /dev/sdc: x86 boot sector, code offset 0x48 /dev/sdc1: SGI XFS filesystem data (blksz 4096, inosz 256, v2 dirs) /dev/sdd: x86 boot sector, code offset 0x48 /dev/sdd1: SGI XFS filesystem data (blksz 4096, inosz 256, v2 dirs) /dev/sdd2: SGI XFS filesystem data (blksz 4096, inosz 256, v2 dirs) /dev/sdd3: SGI XFS filesystem data (blksz 4096, inosz 256, v2 dirs) Next, the IDE drives (for me, that's just optical drives and only one currently has a disc inserted): # file -s /dev/hd* /dev/hda: writable, no read permission /dev/hdc: ISO 9660 CD-ROM filesystem data 'SU1000.001 ' (bootable)
...
Damon Register
Randall Schulz -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Monday 28 May 2007 23:56, Randall R Schulz wrote:
# file -s /dev/sd* /dev/sda: x86 boot sector /dev/sda1: ReiserFS V3.6 block size 4096 (mounted or unclean) num blocks 73254384 r5 hash /dev/sdb: x86 boot sector, code offset 0x48 /dev/sdb1: SGI XFS filesystem data (blksz 4096, inosz 256, v2 dirs) /dev/sdb2: x86 boot sector, Microsoft Windows XP MBR /dev/sdb3: Linux/i386 swap file (new style) 1 (4K pages) size 1048240 pages /dev/sdb4: x86 boot sector, extended partition table /dev/sdc: x86 boot sector, code offset 0x48 /dev/sdc1: SGI XFS filesystem data (blksz 4096, inosz 256, v2 dirs) /dev/sdd: x86 boot sector, code offset 0x48 /dev/sdd1: SGI XFS filesystem data (blksz 4096, inosz 256, v2 dirs) /dev/sdd2: SGI XFS filesystem data (blksz 4096, inosz 256, v2 dirs) /dev/sdd3: SGI XFS filesystem data (blksz 4096, inosz 256, v2 dirs)
That is a nifty tips, Randall! I thought we usually use fdisk -l. I didn't know that. Thanks for sharing :) -- Fajar Priyanto | Reg'd Linux User #327841 | Linux tutorial http://linux2.arinet.org 7:15am up 0:53, 2.6.18.2-34-default GNU/Linux Let's use OpenOffice. http://www.openoffice.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Tuesday 2007-05-29 at 07:15 +0700, Fajar Priyanto wrote:
On Monday 28 May 2007 23:56, Randall R Schulz wrote:
# file -s /dev/sd* /dev/sda: x86 boot sector ... /dev/sdd3: SGI XFS filesystem data (blksz 4096, inosz 256, v2 dirs)
That is a nifty tips, Randall! I thought we usually use fdisk -l. I didn't know that. Thanks for sharing :)
"fdisk -l" gives the partition type, yes, but all linux filesystems use the same partition type (83h). Windows has the luxury of having reserved several numbers, but Linux doesn't. We have to distinguish them some other way instead. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFGW3RAtTMYHG2NR9URAiDJAKCGk40wMw3FINUMyiVtBylYX7Ov0QCeJfPW nrX4B+Ayp99QbbF9LjkY1wo= =GRQv -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Sorry Randall, I forgot to change the address to reply to list. Randall R Schulz wrote:
If the error message is that the resource (in this case a disk partition) is busy, then just about the only thing that could indicate here is the error message
directory) by using the "mount" or "df" commands. the mount and df don't show the FAT32 partition
linux-gmsj:~ # mount /dev/mapper/pdc_ifagghhd_part6 on / type ext3 (rw,acl,user_xattr) proc on /proc type proc (rw) sysfs on /sys type sysfs (rw) debugfs on /sys/kernel/debug type debugfs (rw) udev on /dev type tmpfs (rw) devpts on /dev/pts type devpts (rw,mode=0620,gid=5) /dev/mapper/pdc_ifagghhd_part2 on /boot type ext2 (rw,acl,user_xattr) securityfs on /sys/kernel/security type securityfs (rw) /dev/hdd on /media/SU1020.001 type iso9660 (ro,nosuid,nodev,noatime,uid=0,utf8) linux-gmsj:~ # df -k Filesystem 1K-blocks Used Available Use% Mounted on /dev/mapper/pdc_ifagghhd_part6 5044156 4675972 111952 98% / udev 128184 132 128052 1% /dev /dev/mapper/pdc_ifagghhd_part2 23332 10891 11237 50% /boot /dev/hdd 3789858 3789858 0 100% /media/SU1020.001
You can verify what's on a disk with the "file" command, provided you give the "-s" option (otherwise it tells you that the target is a disk): Thanks for the info. I agree with Fajar Priyanto's post; it really is a useful tip. The mount and df commands I already knew about but not the file -s trick
# file -s /dev/hd* I tried that and got linux-gmsj:~ # file -s /dev/hda* /dev/hda: x86 boot sector; partition 1: ID=0x7, active, starthead 1, startsector 63, 16386237 sectors; partition 2: ID=0x83, starthead 0, startsector 16386300, 48195 sectors; partition 3: ID=0xf, starthead 0, startsector 16434495, 23438835 sectors, code offset 0x48 /dev/hda1: x86 boot sector, code offset 0x52, OEM-ID "NTFS ", sectors/cluster 8, reserved sectors 0, Media descriptor 0xf8, heads 255, hidden sectors 63, dos < 4.0 BootSector (0x80) /dev/hda2: Linux rev 1.0 ext2 filesystem data (mounted or unclean) /dev/hda3: x86 boot sector; partition 1: ID=0x82, starthead 1, startsector 63, 1060227 sectors; partition 2: ID=0x5, starthead 0, startsector 1060290, 10249470 sectors, extended partition table /dev/hda5: Linux/i386 swap file (new style) 1 (4K pages) size 132527 pages /dev/hda6: Linux rev 1.0 ext3 filesystem data (needs journal recovery) (large files) /dev/hda7: x86 boot sector, code offset 0x58, OEM-ID "MSWIN4.1", sectors/cluster 8, reserved sectors 34, Media descriptor 0xf8, heads 255, hidden sectors 27744318, sectors 12129012 (volumes > 32 MB) , FAT (32 bit), sectors/FAT 11823, reserved3 0x800000, serial number 0xc67e28b9, label: "ASUS_D " linux-gmsj:~ #
/dev/hda7 is the one I am trying to mount. Attempting to mount gives linux-gmsj:~ # mount -t vfat /dev/hda7 /windows/data mount: /dev/hda7 already mounted or /windows/data busy linux-gmsj:~ # I don't know what else to try. Damon Register -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Tuesday 29 May 2007 14:42, Damon Register wrote:
...
# file -s /dev/hd*
I tried that and got linux-gmsj:~ # file -s /dev/hda* /dev/hda: x86 boot sector; partition 1: ID=0x7, active, starthead 1, startsector 63, 16386237 sectors; partition 2: ID=0x83, starthead 0, startsector 16386300, 48195 sectors; partition 3: ID=0xf, starthead 0, startsector 16434495, 23438835 sectors, code offset 0x48 /dev/hda1: x86 boot sector, code offset 0x52, OEM-ID "NTFS ", sectors/cluster 8, reserved sectors 0, Media descriptor 0xf8, heads 255, hidden sectors 63, dos < 4.0 BootSector (0x80) /dev/hda2: Linux rev 1.0 ext2 filesystem data (mounted or unclean) /dev/hda3: x86 boot sector; partition 1: ID=0x82, starthead 1, startsector 63, 1060227 sectors; partition 2: ID=0x5, starthead 0, startsector 1060290, 10249470 sectors, extended partition table /dev/hda5: Linux/i386 swap file (new style) 1 (4K pages) size 132527 pages /dev/hda6: Linux rev 1.0 ext3 filesystem data (needs journal recovery) (large files) /dev/hda7: x86 boot sector, code offset 0x58, OEM-ID "MSWIN4.1", sectors/cluster 8, reserved sectors 34, Media descriptor 0xf8, heads 255, hidden sectors 27744318, sectors 12129012 (volumes > 32 MB) , FAT (32 bit), sectors/FAT 11823, reserved3 0x800000, serial number 0xc67e28b9, label: "ASUS_D " linux-gmsj:~ #
/dev/hda7 is the one I am trying to mount. Attempting to mount gives
linux-gmsj:~ # mount -t vfat /dev/hda7 /windows/data mount: /dev/hda7 already mounted or /windows/data busy linux-gmsj:~ #
Well, based the mount and df output you supplied, it does not appear that /dev/hda7 is mounted, though sometimes /etc/mtab can become out-of-sync with the actual list of mounted devices. You can be certain by looking at /proc/mounts (I should have mentioned this the first time--sorry). The only other possibility I can think of (*) is that the mount point (/windows/data, in this case) is in use, meaning, most likely, it is the current working directory for some process. If it's not immediately obvious which that might be (say, the shell you're using to run these commands), then use the "lsof" command to see if there is a process that is holding a reference of some sort to the mount-point directory. As root: # lsof |egrep /windows/data (Naturally, this produces no output on my system, since I have no such directory.) If it turns out one or more processes is using that directory, shut them down or change their current working directory to some other place. (*) On my 10.0 system, you can mount over a directory that is the current working directory of a process, but perhaps the kernel in 10.2 is more fussy?
I don't know what else to try.
You can always give up and reboot...
Damon Register
Randall Schulz -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Tuesday 2007-05-29 at 17:42 -0400, Damon Register wrote: ...
/dev/hda7: x86 boot sector, code offset 0x58, OEM-ID "MSWIN4.1", sectors/cluster 8, reserved sectors 34, Media descriptor 0xf8, heads 255, hidden sectors 27744318, sectors 12129012 (volumes > 32 MB) , FAT (32 bit), sectors/FAT 11823, reserved3 0x800000, serial number 0xc67e28b9, label: "ASUS_D " linux-gmsj:~ #
/dev/hda7 is the one I am trying to mount. Attempting to mount gives
linux-gmsj:~ # mount -t vfat /dev/hda7 /windows/data mount: /dev/hda7 already mounted or /windows/data busy linux-gmsj:~ #
Try to mount on another directory, and try to run fsck on hda7. Ah! Look at "dmesg" output. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFGXKnqtTMYHG2NR9URAjJzAJ9aTmrrVNDw0vZX79iCi7lKdkMMYgCeKil+ C8hAAZGqxA/TqHZYtKgCf+k= =0OKJ -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wednesday 30 May 2007 04:42, Damon Register wrote:
/dev/hda7: x86 boot sector, code offset 0x58, OEM-ID "MSWIN4.1", sectors/cluster 8, reserved sectors 34, Media descriptor 0xf8, heads 255, hidden sectors 27744318, sectors 12129012 (volumes > 32 MB) , FAT (32 bit), sectors/FAT 11823, reserved3 0x800000, serial number 0xc67e28b9, label: "ASUS_D " linux-gmsj:~ #
/dev/hda7 is the one I am trying to mount. Attempting to mount gives
linux-gmsj:~ # mount -t vfat /dev/hda7 /windows/data mount: /dev/hda7 already mounted or /windows/data busy linux-gmsj:~ #
Ok: 1. run this: partprobe This will force the kernel to renew it's info on your partitions. 2. try to mount it into another directory: mkdir /test mount -t vfat /dev/hda7 /test -- Fajar Priyanto | Reg'd Linux User #327841 | Linux tutorial http://linux2.arinet.org 7:53am up 1:34, 2.6.18.2-34-default GNU/Linux Let's use OpenOffice. http://www.openoffice.org
participants (5)
-
Carlos E. R. -
Damon Register -
Fajar Priyanto -
Mark Goldstein -
Randall R Schulz