| View previous topic :: View next topic |
| Author |
Message |
gr0x0rd
Guru
Joined: 12 Aug 2006
Posts: 311
|
 Posted: Thu Jun 30, 2011 11:38 pm Post subject: udev/consolekit/vfs WTF!!!! |
 |
|
I just plugged my Nexus S into my Gentoo system via USB to copy over some precious photos I just took. I did a world update 2 days ago. Tried mounting my device and got "Not authroized". How nice. Another world update, and once again i have to search the forums to get things working again.
Thankfully I had another Gentoo system that I did not update. I plugged my device into it and mounted the drive. Funny, I don't see my photos. They're gone! Unmount. Check the device. Gone. F*CKING GONE. Along with other various files and data from my sdcard.
dmesg | Code: | [26841.795226] usb 2-1.2: new high speed USB device using ehci_hcd and address 4
[26841.882245] scsi4 : usb-storage 2-1.2:1.0
[26842.882909] scsi 4:0:0:0: Direct-Access Android UMS Composite 0001 PQ: 0 ANSI: 2
[26842.883643] sd 4:0:0:0: Attached scsi generic sg2 type 0
[26842.886059] sd 4:0:0:0: [sdb] Attached SCSI removable disk
[26853.212608] sd 4:0:0:0: [sdb] 27957215 512-byte logical blocks: (14.3 GB/13.3 GiB)
[26853.213122] sd 4:0:0:0: [sdb] Assuming drive cache: write through
[26853.214573] sd 4:0:0:0: [sdb] Assuming drive cache: write through
[26853.214582] sdb:
[26911.133164] VFS: busy inodes on changed media or resized disk sdb
[26911.135344] VFS: busy inodes on changed media or resized disk sdb
[26911.137002] VFS: busy inodes on changed media or resized disk sdb
[26911.139144] VFS: busy inodes on changed media or resized disk sdb
[26911.141965] VFS: busy inodes on changed media or resized disk sdb
[27010.079488] usb 2-1.2: USB disconnect, address 4
|
If anyone can offer me a technical explanation for what the f*ck just happened here so I can prevent this in the future, I'd be very interested to hear it.
And for the rest of you, here's your warning...
I tried running fsck on the drive to no effect. Can anyone recommend some disk tools i could use to try to recover my data?
_________________
~g
emerge -FML... |
|
| Back to top |
|
 |
gr0x0rd
Guru
Joined: 12 Aug 2006
Posts: 311
|
| Posted: Wed Jul 06, 2011 3:35 am Post subject: |
|
|
I was able to solve my mount issue by removingthat had been appended to the | Code: | | session optional pam_ck_connector.so |
directive in
/etc/pam.d/system-login. That's an etc-update issue for another thread.
All I was able to find regarding the inodes message while googling had to do with ejecting physical media without unmounting first. This usually had to do with cdroms. I really wish I could find some more info on this, and specifically how any why it happened to my android device, effectively destroying the data I was mounting in order to back up.
I'm all ears if anyone has any hare-brained theories, or otherwise. Also, I apologize for the original tone of this post, as I was very, very pissed off. Sorry if I ruffled anyone's feathers.
_________________
~g
emerge -FML... |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Kernel & Hardware
