Opened 12 years ago

Closed 11 years ago

#1796 closed bug (invalid)

Cannot mount partitions either from Desktop, Drive Setup or Terminal

Reported by: cebif Owned by: axeld
Priority: normal Milestone: R1
Component: File Systems Version: R1/pre-alpha1
Keywords: Cc:
Blocked By: Blocking:
Has a Patch: no Platform: All

Description

I can mount bfs partitions from Desktop but cannot mount any other partitions from Desktop, Drive Setup or Terminal, including bfs. If I try to mount a FAT32 partition from Drive Setup I get "Error invalid argument" window. I was testing in hrev23925

Attachments (4)

Trying to Mount From Drive Setup (465.1 KB ) - added by cebif 12 years ago.
Trying to Mount From Terminal Beos and FAT32 Partitions (458.8 KB ) - added by cebif 12 years ago.
Errors using Terminal to Mount Other Drives 2.jpg (192.0 KB ) - added by cebif 12 years ago.
Results for mounting FAT32 partition from Terminal and DriveSetup.jpg (183.6 KB ) - added by cebif 12 years ago.
Revised command works for Beos partition but not Windows. Using Terminal or DriveSetup

Download all attachments as: .zip

Change History (20)

comment:1 by korli, 12 years ago

Could you please upload PNG or JPEG images ?

comment:2 by cebif, 12 years ago

I don't know how it happened but the images I uploaded were jpeg and they somehow were converted to html. I will try and get some screenshots again but I am having other operating system problems (linux) as well as ISP slowed my connection speed to dialup. It might take a day or two to sort things out.

comment:3 by mmlr, 12 years ago

The images work fine if you download them. You just didn't save them with the ".jpeg" so now it doesn't know how to display them. Anyway, you're using the mount command the wrong way. The syntax is "mount [-ro] [-t fstype] device directory" where "-ro" means read only, with "-t" you can specify a filesystem type if it is not autodetected (i.e. "-t iso9660" for cds), then "device" which is "/dev/disk/ata/x/master/y" and "directory" which is where to mount. You first have to create the directory to mount to by using "mkdir /TheMount" where "TheMount" is a useful name to recognize again. In your case you'd have to do for example:

mkdir /OtherBeOS mount -t bfs /dev/disk/ata/0/master/1 /OtherBeOS

Where "/OtherBeOS" can be anything you like.

comment:4 by cebif, 12 years ago

I re applied the command in Terminal as mmir has advised but it did not work either. The first time I made a definite error by leaving out /disk in device but inserted it next. It still did not work. I wondered if there needed to be a space between device and directory but no. Could not mount the Windows FAT32 partition either. This partition is not showing on the Desktop right click sub menu.

comment:5 by cebif, 12 years ago

The new screen shot I uploaded is shown as a raw on the end of the URL. I had saved it as jpeg before uploading. This seems to happen if I upload from Beos not Linux or Windows.

comment:6 by cebif, 12 years ago

I have re uploaded the screenshot using Eye of Gnome image veiwer. The first with 2 on the end of name did not work properly until I used save-as and put jpg on the names end. The file images I have uploaded before have done this automatically. Disregard the first with 2 on the names end.

in reply to:  6 ; comment:7 by jackburton, 12 years ago

Replying to cebif:

I have re uploaded the screenshot using Eye of Gnome image veiwer. The first with 2 on the end of name did not work properly until I used save-as and put jpg on the names end. The file images I have uploaded before have done this automatically. Disregard the first with 2 on the names end.

Can't you delete wrong attachments ? Or maybe you don't have permissions to do so.

in reply to:  7 comment:8 by cebif, 12 years ago

Replying to jackburton:

Replying to cebif:

I have re uploaded the screenshot using Eye of Gnome image veiwer. The first with 2 on the end of name did not work properly until I used save-as and put jpg on the names end. The file images I have uploaded before have done this automatically. Disregard the first with 2 on the names end.

Can't you delete wrong attachments ? Or maybe you don't have permissions to do so.

I don't have permission to. I was looking for the delete button but could not see it.

comment:9 by nielx, 12 years ago

I deleted the double posted attachments. Deletion of attachments is reserved for developers.

comment:10 by jackburton, 12 years ago

The commands you are using are wrong. There needs to be a space between the device name and the mount directory: IOW:

"mount /dev/disk/ata/0/master/2 <space> win_f"

comment:11 by mmlr, 12 years ago

The mount point is "/TheMountPoint" not just "TheMountPoint". So really it is: "mount <space> /dev/disk/ata/0/master/x <space> /TheMountPoint"

by cebif, 12 years ago

Revised command works for Beos partition but not Windows. Using Terminal or DriveSetup

comment:12 by mmlr, 12 years ago

Yes, that's what the "-t <type>" is for when using mount. To mount a fat32 filesystem you specify "mount -t fat /dev/disk/ata/x/{master|slave}/y /mountPoint". I have tested that this works with mounting a fat32 filesystem here, but I think ntfs support is yet missing.

comment:13 by cebif, 12 years ago

Your right if I put -t fat before the device it will mount in Terminal. I still cannot use DriveSetup to mount fat32 partitions though. It gives an error window "Invalid argument."

comment:14 by axeld, 12 years ago

That's to be expected, because the FAT (and NTFS for that matter) file system(s) do(es) not yet implement the file system identify hooks. Once they do, you no longer need to specify the file system with "mount", and will be able to mount them using Tracker, and DriveSetup, too.

comment:15 by RandomInsano, 11 years ago

Is this still a problem? I'm certainly able to mount Fat32, but have yet to test NTFS. Since this isn't actually a bug and maybe an enhancement ("Ensure all filesystem drivers implement identify hook") shouldn't this be closed on converted?

comment:16 by axeld, 11 years ago

Resolution: invalid
Status: newclosed

NTFS is currently disabled (it still needs to be ported to the new file system API), so I guess this bug can be closed indeed.

Note: See TracTickets for help on using tickets.