Other trying to figure out this cli mount ext4 thing...

userxbw

userxbw

gpart list
Code: 
Geom name: da0
modified: false
state: OK
fwheads: 255
fwsectors: 63
last: 732558330
first: 6
entries: 128
scheme: GPT
Providers:
1. Name: da0p1
   Mediasize: 3000556847104 (2.7T)
   Sectorsize: 4096
   Stripesize: 0
   Stripeoffset: 1048576
   Mode: r0w0e0
   efimedia: HD(1,GPT,d8d1da3e-bc49-43a6-a103-597f9c1f30ee,0x100,0x2ba9f200)
   rawuuid: d8d1da3e-bc49-43a6-a103-597f9c1f30ee
   rawtype: ebd0a0a2-b9e5-4433-87c0-68b6b72699c7
   label: (null)
   length: 3000556847104
   offset: 1048576
   type: ms-basic-data
   index: 1
   end: 732558079
   start: 256
Consumers:
1. Name: da0
   Mediasize: 3000558944256 (2.7T)
   Sectorsize: 4096
   Mode: r0w0e0
I installed fusefs-ext2 because automount informed me that gives read/write for ext*
Code: 
[userx@FreeBSD64ssd ~]$ ls /dev
acpi            bpsm0           kbd1            psm0            ttyva
ada0            console         kbdmux0         pts             ttyvb
ada0s1          consolectl      klog            random          ufssuspend
ada0s1a         ctty            kmem            reroot          ugen0.1
ada0s2          da0             log             sequencer0      ugen0.2
ada1            da0p1           mdctl           ses0            ugen0.3
ada1s1          devctl          mem             sndstat         ugen0.4
ada1s2          devctl2         midistat        stderr          ugen0.5
ada1s3          devstat         mixer0          stdin           ugen0.6
ada1s5          diskid          mixer1          stdout          ugen0.7
ada1s6          dri             mixer2          sysmouse        ugen0.8
ada1s7          drm             music0          tcp_log         ugen0.9
ada1s8          dsp1.0          netdump         ttyv0           ugen1.1
apm             fb0             netmap          ttyv1           ugen1.2
apmctl          fd              nfslock         ttyv2           uhid0
atkbd0          fido            ntfs            ttyv3           uhid1
audit           full            null            ttyv4           ums0
auditpipe       geom.ctl        pass0           ttyv5           urandom
autofs          gptid           pass1           ttyv6           usb
aux             hpet0           pass2           ttyv7           usbctl
bpf             io              pass3           ttyv8           xpt0
bpf0            kbd0            pci             ttyv9           zero
[userx@FreeBSD64ssd ~]$ ls /mnt  
usb1
[userx@FreeBSD64ssd ~]$ sudo mount auto /dev/da0p1 /mnt/usb1
usage: mount [-adflpruvw] [-F fstab] [-o options] [-t ufs | external_type]
       mount [-dfpruvw] special | node
       mount [-dfpruvw] [-o options] [-t ufs | external_type] special node
[userx@FreeBSD64ssd ~]$ sudo mount -t ext2fs /dev/da0p1 /mnt/usb1
mount: /dev/da0p1: Invalid argument
[userx@FreeBSD64ssd ~]$ sudo mount -t ext4 /dev/da0p1 /mnt/usb1
mount: /dev/da0p1: Operation not supported by device
[userx@FreeBSD64ssd ~]$ sudo mount -t ext4 /dev/da0 /mnt/usb1
mount: /dev/da0: Operation not supported by device
[userx@FreeBSD64ssd ~]$ sudo mount -t ext2fs /dev/da0 /mnt/usb1
mount: /dev/da0: Invalid argument
what I've seen thus far in the commands to be used .. as it shows does not work.

I know it got a be the partition not device, file format (sometimes) source -> destination.
Code: 
mount (type) source -> destination
that simple .. but.. what am I doing wrong?
 
Nothing you've shown from ad0 is actually ext2 (or any other ext version).
 
SirDice said:
Nothing you've shown from ad0 is actually ext2 (or any other ext version).
Click to expand...
so ad = ext2 ?

all of them ad* ones are two hdd's in my laptop.

from what I've been seeing I though them are just where the drive is at destinations. da= usb port not type. it maybe ntfs on that drive now that you bring this up. let me swap it with what I know for sure is ext4 , I do not use that drive very often, its actually been a log time sense I plug that one in, let me get a different one and try this again.. hold on ...
 
olli@ said:
What does the command fstyp /dev/da0p1 say?
Click to expand...
Code: 
fstyp /dev/da0p1
fstyp: /dev/da0p1: No such file or directory
but I am looking at it.. mhuhahaha
wait I swapped it out :eek:
Code: 
[userx@FreeBSD64ssd ~]$ fstyp /dev/da0s1
ext2fs
,...
[userx@FreeBSD64ssd ~]$ sudo mount -t ext2fs /dev/da0s1 /mnt/usb1
mount: /dev/da0s1: Invalid argument

is there something more to do after installing this fusefs-ext2 -- config files, reboot?

rebooted. now it's

Code: 
root@FreeBSD64ssd.net:/home/userx
# mount /dev/da0s1 /mnt/usb1
mount: /dev/da0s1: No such file or directory

root@FreeBSD64ssd.net:/home/userx
# fstyp /dev/da0s1
ext2fs
root@FreeBSD64ssd.net:/home/userx
# mount -t ext2fs /dev/da0s1 /mnt/usb1
mount: /dev/da0s1: Invalid argument
and
Code: 
# /etc/autofs/special_media
1TB
ada1s8
ada1s7
ada1s6
ada1s5
ada1s3
ada1s2
ada1s1
the write up on that is it shows already mounted
Code: 
[userx@FreeBSD64ssd media]$ ls
1TB     ada1s1  ada1s2  ada1s5  ada1s6  ada1s7  ada1s8  data1
/dev/da0s1 is actually the 1TB but it does not show any files in the file manager if I click into it.. go figure..
 
ok let me try running that this says.
Code: 
# file -s /dev/da0s1
/dev/da0s1: Linux rev 1.0 ext4 filesystem data, UUID=93a1fc88-fef1-4bf1-8f24-af94a725e786, volume name "1TB" (needs journal recovery) (extents) (large files) (huge files)
well maybe not
(this part is all new to me)
Code: 
# fsck  /media/1TB
/media/1TB is not a char device
Can't resolve /media/1TB to character special device.
/media/1TB is not a disk device
CONTINUE? [yn]
selected n

I'm going to jump into Linux and run gparted -> check on it.
 
So, for some reason the fusefs-ext2 driver does not recognize it as a valid ext2 file system. Maybe try to mount it read-only. I think the write support of fusefs-ext2 is rather unreliable. Also, support for certain advanced features of ext3 / ext4 might be missing, so if your file system uses those features, it might refuse to mount it.

By the way, for data exchange between different operating systems I recommend FAT32. It has certain limits (4GB file size, no permissions, no ownership, no symlinks), but you can circumvent those limitations by putting a split tar archive on the FAT32 file system, for example.

Another alternative without the 4GB file size limit would be exFAT (there's a FUSE driver for that one, too) because it is supported by all major operating systems including BSD, Linux, Windows and MacOS. Also, it's the default file system for SDXC flash memory cards used by digital cameras.
 
userxbw said:
ok let me try running that this says.
Code: 
# file -s /dev/da0s1
/dev/da0s1: Linux rev 1.0 ext4 filesystem data, UUID=93a1fc88-fef1-4bf1-8f24-af94a725e786, volume name "1TB" (needs journal recovery) (extents) (large files) (huge files)
Click to expand...
The “needs journal recovery” part might be the reason why fusefs-ext2 refuses to mount it.
Maybe you removed the stick from the linux machine without unmounting it first.
 
olli@ said:
So, for some reason the fusefs-ext2 driver does not recognize it as a valid ext2 file system. Maybe try to mount it read-only. I think the write support of fusefs-ext2 is rather unreliable. Also, support for certain advanced features of ext3 / ext4 might be missing, so if your file system uses those features, it might refuse to mount it.

By the way, for data exchange between different operating systems I recommend FAT32. It has certain limits (4GB file size, no permissions, no ownership, no symlinks), but you can circumvent those limitations by putting a split tar archive on the FAT32 file system, for example.

Another alternative without the 4GB file size limit would be exFAT (there's a FUSE driver for that one, too) because it is supported by all major operating systems including BSD, Linux, Windows and MacOS. Also, it's the default file system for SDXC flash memory cards used by digital cameras.
Click to expand...
the bother with that one is I already got a butt load of ext4 and some ntfs (internal laptop hdds used for externals and two external hdds formatted to and filled with files already, and not spare to play move everyting on to that change format then move everything back onto it.
 
You must log in or register to reply here.
Back
Top