Newbie mounts USB device the first time

[siguri]

Hello,
why do I still get output like WARNING: autofs_trigger_one: request for /media/da0s1/ completed with error 5, pid 3382 (ls)
or mount: /dev/da0s1: No such file or directory ... while mount usb (as root) following thoroughly most of .:ALL:. the instructions in the Handbook, please?

_siguri

 

[Alain De Vos]

#Format UFS
newfs -O 2 -U -j -L da0s1 /dev/da0s1
mkdir /mnt/da0s1
#Mount
mount /dev/da0s1 /mnt/da0s1

 

[siguri]

Thank You for the reply, I actually had to realize that I the format of my disk was ntfs, so I found ntfs-3g / fusefs to do the job.

 

[siguri]

newfs -O 2 -U -j -L da0s1 /dev/da0s1

do you apply this command while an usb-disk is attached to the system? and if so... if it is not empty will the content be still readable thereafter?

file -s /dev/da0s2
/dev/da0s2: Linux rev 1.0 ext3 filesystem data, UUID=f2cdf150-9f79-40d6-acf1-12a47c0a7be5 (large files)

 

[SirDice]

do you apply this command while an usb-disk is attached to the system?

No. You have to create a filesystem (which is what newfs(8) does) before you can mount it. If you're more familiar with MS-DOS/Windows, it's the Unix equivalent of the format command.

and if so... if it is not empty will the content be still readable thereafter?

No, newfs(8) will destroy any existing filesystem that was on there. Just like a 'format' on Windows would basically empty that filesystem.

 

[siguri]

I'm confused. <newfs> creates a filesystem anew. the usb-devices that I have in use already contains a filesystem, namely ext3, as I found out. It is Because after hot/pluggin my usb-disk the default kernel is not able to handle the ext3 that I'll tend to get something like "file not found"?

 

[SirDice]

<newfs> creates a filesystem anew

Correct. More specifically newfs(8) will create a new UFS1 or UFS2 filesystem.

the usb-devices that I have in use already contains a filesystem, namely ext3, as I found out.

Yes, DO NOT run newfs(8) on it as it will destroy everything that was on there. That was what I was trying to explain.

Because after hot/pluggin my usb-disk the default kernel is not able to handle the ext3 that I'll tend to get something like "file not found"?

Try using ext2fs(5) to mount it. For example; mount -t ext2fs /dev/da0s2 /mnt

Run tail -F /var/log/messages in a console or terminal, then plug the stick in. Note the disk name that's detected. These can shift if you have other USB sticks plugged in, so it may be da2 now (if there's already a da0 and da1). The number is dynamic and depends on the order the disks are detected or plugged in.

Run gpart show <diskname> to see the partition table. That will tell you if you need to use s1, s2 (MBR) or p1, p2 (GPT) etc.