Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can mount ext4 partition on Mojave (10.14.1), but shows up empty #52

Open
dprotter opened this issue Nov 18, 2018 · 2 comments
Open

Can mount ext4 partition on Mojave (10.14.1), but shows up empty #52

dprotter opened this issue Nov 18, 2018 · 2 comments

Comments

@dprotter
Copy link

dprotter commented Nov 18, 2018

Hi all, I've been trying to mount an ext4 formatted SSD on my mac. I can confirm that it contains the data I need by plugging it into another computer, but when I mount with ext4fuse it looks completely empty. I've already checked for OSXFuse updates, and I'm all up-to-date.

I've also successfully mounted another linux disk by mistake (I forgot a USB flashed with an update file was plugged into my USB hub, haha), but I can't seem to get access to my big ole SSD with actual data on it.

I've tried a variety of mount commands, but the most recent was:
ext4fuse /dev/disk2s1 /Users/me/Desktop/tmp -o logfile=/Users/me/Desktop/ext_log.txt -o allow_other

if cd into the mount and run ls -la in I get:
dr-xr-xr-x@ 3 root wheel 4096 Aug 13 14:26 . drwx------+ 26 me staff 832 Nov 18 08:19 .. MrMe:tmp me$

Thanks for any advice! the log file head and tail is below.

[debug][__disk_read:105] Disk Read: 0x438 +0x2 [main:135]
[info] [op_init:20] Using FUSE protocol 7.19
[debug][__disk_read:105] Disk Read: 0x400 +0x400 [super_fill:57]
[info] [super_fill:59] BLOCK SIZE: 4096
[info] [super_fill:60] BLOCK GROUP SIZE: 134217728
[info] [super_fill:61] N BLOCK GROUPS: 3726
[info] [super_fill:62] INODE SIZE: 256
[info] [super_fill:63] INODES PER GROUP: 8192
[debug][__disk_read:105] Disk Read: 0x1000 +0x40 [super_group_fill:90]
[debug][__disk_read:105] Disk Read: 0x1040 +0x40 [super_group_fill:90]

[debug][__disk_read:105] Disk Read: 0x421100 +0x9c [inode_get_by_number:155]
[debug][op_getattr:32] getattr done
[debug][op_getattr:23] getattr(/)
[debug][inode_get_idx_by_path:202] Looking up: /
[debug][inode_get_idx_by_path:207] Looking up after dcache:
[debug][super_group_inode_table_offset:73] Inode table offset: 0x421
[debug][__disk_read:105] Disk Read: 0x421100 +0x9c [inode_get_by_number:155]
[debug][op_getattr:32] getattr done
[debug][op_getattr:23] getattr(/)
[MrMer:Desktop me$

@dprotter
Copy link
Author

Just a bump for this, I'm getting the same behavior intermittently. Could it be because I'm formatting the drive with DiskGuru? Linux systems read it fine, but all I get when I mount it is the "lost+found" directory and nothing else...

@dsoprea
Copy link

dsoprea commented Jan 18, 2019 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants