Root Phone will no longer mount

[Karl_Tx]

Phone is using Ryan's one click lag fix.....ext 2 file system. Even after rooting initially I was able to mount as long as I used usb debugging......but now....I use it.....I plug into the usb port and nothing.....I can click on mount but nothing happens anymore.....any idieas? Thanks in advance

 

[sremick]

The lagfix in OCLF does dirty tricks/things to pull it off. And ext2 is unsafe as all hell... tosses away all filesystem integrity safeguards for the sake of speed. There's a very good reason the Captivate didn't ship with ext2.

Lagfixes are high-risk and not recommended. Now you see why.

 

[dayv]

Phone is using Ryan's one click lag fix.....ext 2 file system. Even after rooting initially I was able to mount as long as I used usb debugging......but now....I use it.....I plug into the usb port and nothing.....I can click on mount but nothing happens anymore.....any idieas? Thanks in advance

does the phone start charging when you plug it into the usb port? are there any other issues problems with the phones operation?

by the way ext2 is not as unsafe as hell. yea there are feature improvements such a journaling available in ext4 and as such are welcome improvements and make ext4 better at avoiding data corruption. but i ran drives with ext2 for years and never had any major issues. which by the way ext4 is just ext2 with more features -- at the core they are the same file system and both blow samsungs rfs out of the water.

but, lagfix's for the cappi are risky. very few if any of the applications and software written for the cappi were written with the idea lagfix's being used, they are all usually written with the expectation that the cappi will be operating under manufactured spec which creates allot of potential for bugs. also most all of these lagfix's require partial/or entire reformatting of the data partition which also has a certain amount of risk, especially when done wrong or haphazardly.

that all said, I think it may be a little presumptuous to assume it is the lagfix that is causing the issue. In fact if there are not any other prevalent bugs or issues with the phone i would be more apt to think the problem lies with the computer the phone is being connected to -- though this is still a little presumptuous on my part until we have some more information.

 

[ronaldramsayii]

does the phone start charging when you plug it into the usb port? are there any other issues problems with the phones operation?

by the way ext2 is not as unsafe as hell. yea there are feature improvements such a journaling available in ext4 and as such are welcome improvements and make ext4 better at avoiding data corruption. but i ran drives with ext2 for years and never had any major issues. which by the way ext4 is just ext2 with more features -- at the core they are the same file system and both blow samsungs rfs out of the water.

but, lagfix's for the cappi are risky. very few if any of the applications and software written for the cappi were written with the idea lagfix's being used, they are all usually written with the expectation that the cappi will be operating under manufactured spec which creates allot of potential for bugs. also most all of these lagfix's require partial/or entire reformatting of the data partition which also has a certain amount of risk, especially when done wrong or haphazardly.

that all said, I think it may be a little presumptuous to assume it is the lagfix that is causing the issue. In fact if there are not any other prevalent bugs or issues with the phone i would be more apt to think the problem lies with the computer the phone is being connected to -- though this is still a little presumptuous on my part until we have some more information.

In a ways it could be a lagfix.....but it also can be as simple as the correct driver on his computer. Ext2 even Ext4 is risky and can cause problems like bootloops and so on.

Everyone has to understand that anything you flash to your phone can do significant damage to your phone. That's why people warn you, if you flash anything, even ROOT your phone, you void the warranty.

 

[Jirv311]

Stupid question but do you have any other drives mapped in My Computer? My work laptop has a persistent G: drive mapping. Typically after a fresh ROM flash, the first time I plug in my phone, it will assign itself as G:. I have to go into Disk Management and change it manually for it to show up. This could also happen with an SD Card reader installed. Take a peek in Disk Management and see if it shows up there. This could again also be related to a bad USB Mass Storage driver. Google "Remove old USB devices from Windows".

I too disagree this has anything to do with the lag fix installed. Mounting of the SD Card should not be affected at all. Of course, to prove it to yourself, you could always uninstall the lag fix.

 

[dayv]

In a ways it could be a lagfix.....but it also can be as simple as the correct driver on his computer. Ext2 even Ext4 is risky and can cause problems like bootloops and so on.

I do agree that lagfixs built on any file system are risky -- at this point anyway, but ext* as a file system is not risky. ext* (ext2, ext3, and ext4) are actually among the best and safest file systems we have available.

I just don't want to see people keep hammering and harping on lagfixs and at the same time accidentally or unknowingly associate problems that can arise from the lagfixs to the file systems that are being used in the lagfixs.

So to be clear Ext2 and Ext4 the file systems themselves are not risky -- just it is the lagfixs that are risky that just happen to be using Ext2 and Ext4.

 

[sremick]

i ran drives with ext2 for years and never had any major issues.

So you got lucky. But what you need to do is step outside of your anecdotal personal experience and look into how ext2 works, how ext3/4 actually differ from it, the concepts of clean vs unclean shutdown, how Android works (especially with abrupt process termination being the norm as well as Android's power-down methodology) and how mixing it all together makes ext2 an extremely unwise choice for Android phones. Not worth sacrificing reliability and data-integrity for speed. And who wants to have to run fsck every time they boot their Android phone?

ext2 is approaching 20 years old now, and since then much has been learned about good practices and better safety of data and filesystem integrity, and how to manage various problem scenarios. If you're going to use ext2 you might as well use an Apple Newton instead of Android since they're from the same time period. Switching from ext4 to ext2 to get a faster phone is like ditching airbags, seatbelts, anti-lock brakes, bumpers, crumple zones, and all the reinforcement steel in the frame in order to get lighter, cheaper and faster cars.

There's a good reason the guy who made the Voodoo lagfix is anti-ext2 and refused to make a version that supported it. Unfortunately the phone-ricers at XDA loved to flame him more than listen to common sense... if they can get higher quadrant scores by risking bricking their phone, they don't care.

As I've said before: Just because you've pulled the trigger 10 times and not died doesn't make Russian Roulette a safe game. Look at the reality, not your personal experience.

 

[dayv]

So you got lucky. But what you need to do is step outside of your anecdotal personal experience and look into how ext2 works, how ext3/4 actually differ from it, the concepts of clean vs unclean shutdown, how Android works (especially with abrupt process termination being the norm as well as Android's power-down methodology) and how mixing it all together makes ext2 an extremely unwise choice for Android phones. Not worth sacrificing reliability and data-integrity for speed. And who wants to have to run fsck every time they boot their Android phone?

ext2 is approaching 20 years old now, and since then much has been learned about good practices and better safety of data and filesystem integrity, and how to manage various problem scenarios. If you're going to use ext2 you might as well use an Apple Newton instead of Android since they're from the same time period. Switching from ext4 to ext2 to get a faster phone is like ditching airbags, seatbelts, anti-lock brakes, bumpers, crumple zones, and all the reinforcement steel in the frame in order to get lighter, cheaper and faster cars.

There's a good reason the guy who made the Voodoo lagfix is anti-ext2 and refused to make a version that supported it. Unfortunately the phone-ricers at XDA loved to flame him more than listen to common sense... if they can get higher quadrant scores by risking bricking their phone, they don't care.

As I've said before: Just because you've pulled the trigger 10 times and not died doesn't make Russian Roulette a safe game. Look at the reality, not your personal experience.

Granted, my statement was anecdotal, and things such as journalling reduce the anoint of data corruption and I do use ext 4 on my drives now, I'm just saying that ext 2 is not as unsafe as hell - it was the best file system available for years.

Making statements implying that ext 2 completely unsafe are just not true. Yes there are options available now with a little less data corruption potential than ext 2, but that does not make ext 2 all of sudden extremely risky. Making a statement such as using ext 4 is going to result in a smaller amount of data corruption over time than ext2 would be.

all disk drives no matter the file system used suffer from some, even if it is a very small amount, of data corruption. people talk about ext 2 data corruption as if it were a huge problem and as if there are no data write protocols in ext 2 to help prevent data corruption which just isn't true - ext 2 does pretty damn good job of protecting data during writes - its just there have been improvements.

Using ext 2 verse ext 4 is not comparable to a car competely stripped of safety features but would be more akin to comparing the safety of a car with side air bags to a car without. Sure the car with side air bags is safer, but that does not make driving the car without air bags akin to playing russian rullette.

And by the way I don't keep any mission critical data on phone that is not backed up somewhere that is a much safer location. Considering that and that fact that the features such as journalling in ext 4 while decrease the amount of data corruption, those same features increase the wear and tear on a drive and will shorten the life span of the drive. Maybe ext 2 would be a better choice for me as I can always restore my data and apps later so long as my drive is working.

That last paragraph should be taken as tongue in cheek as 99% of all of us will have switched to a new phone long before the drives inside them wear out from use.

 

[Infinite-t]

Well, this thread kind of went off the rails...

Hey OP, have you tried a different USB port on your PC? Myself and others have had wierd issues sometimes when plugging into USB ports other than the ones on the back of the PC. Sounds wierd but it happened to me, If I plug in to one of the port on my front panel or on a hub, it wont work, but plugged directly ino the MOBO on the back it does.. go figure. Worth a try I guess. Also, have you tried rebooting the phone? Ive heared of that working too.

 

[dayv]

Ya, OP, sorry to hijack your thread.

Please post back again if you still need help.

 

[cannedkarma]

I did the same thing, and ran into the same problem. The solution is easier than you'd think.

Go into your USB connection settings under Applications, hit Ask on connection. Plug in your USB, the phone will ask what you want it to do. Select Mass storage. You'll see the notification window light up with the USB message, and then you'll have the option to mount the phone as usual.

Hope that helps

 

[Karl_Tx]

Thanks for all the responses to my lament......I discovered I had rectal cranial inversion and unwittingly deleted my usb drivers for the phone.....no wonder it didn't mount....duh. Thanks again guys

 

[Infinite-t]

Thanks for all the responses to my lament......I discovered I had rectal cranial inversion and unwittingly deleted my usb drivers for the phone.....no wonder it didn't mount....duh. Thanks again guys

Rotflmao.. glad you got it figured out!