Database Develop

Getting Linux to boot?!

Hi all,
I popped back after some time away to find that you'd now been working on linux for the BA.
Course, eager as ever I dived in and tried to understand what I thought said instructions.
So I downloaded all the required files, and placed them into the folders specified, ran Heret.exe and I get our iccle penguine with a thermometer rising but when it reaches the top thats all it does?
Am I missing something ere?
Gav

I've got it to get to the Portmap, but i'm unable to login via USB.
Has ANYONE managed to deal with this yet?
Gav

it works exactly as advertised on WIKI.
after temp. goes thru the roof and penguin eyes crack, you should see kernel messages scrolling by.
since u don't see that, i'm guessing the kernel cannot be found because u didn't set up the SD card correctly.
post ur SD card partitions (fdisk -l) and also output of ls -lR
before u can login remotely, usb net modules must be loaded (see wiki)

I had realised I had downloaded the initrd-3.6.12-hh2.gz and mapped the startup.txt to that file,
so I downloaded the 2.6 version and changed the startup and I got the kernal message.
It goes through the kernel and I get a usb disconnection notification on xp and activesync disconnects.
As for partitions, how the f**k do I do this, because theres nothing in wm2003se that allows you to partition sd cards, and I don't get any command prompt on the linux kernel.
Also I do get an error that etc/modules directory could not be found but the kernal continues to load.
Regards
Gav

I'm just waiting till their is a complete Linux ROM with a portalable WINE port built in so you can run TomTom. Then I'll be happy. :wink:

man, you need to follow the wiki EXACTLY. u will not get anywhere by skipping steps.
windoze cannot create required fat and ext3 partitions. the fastest way 2 do this is download a linux live cd
judging by ur level of experience, i say leave this alone, until linux for blueangel matures enough for foolproof installation.

and how do I mount this ext3 partition?
(I can only connect to the initrd-filesystem with ssh)

[HOW-TO] Run Debian Armel on your N1

Hi all!
I want to share the way i have to run Debian on Nexus One
I'm editing my own install of deb-armel and ill upload to everyone but first i need to finish it
By now, we will use a qemu image ready and edit it to your needs
You'll need a SD parted with Amon_RA recovery, few files i'll upload later and some skills with Debian, of course hehe
Partition could be user-alike but i recommend:
Im using a microsdhc 8gb class-2 from my magic
- EXT3: 2gb (nice for install a lot of stuff)
- SWAP: 150MB
- The rest as fat32
You need also a rom with app2sd or mount ETX3 partition under /system/sd, im using Modaco's 1.3
First of all, im working on archlinux but this can be done on windows too using the qemu version for windows
Install qemu on your machine.
NOTE: Also you can start a new installation from 0 using images (iso) and info found on google
Now we will use the following QEMU images:
http://people.debian.org/~aurel32/qemu/armel/
We will download the followings Of course you can choose the small or normal version with X preinstalled (the X version preinstalled is not tested by me and i dont know if works)
debian_lenny_armel_small.qcow2 150M
initrd.img-2.6.26-1-versatile 2.1M
vmlinuz-2.6.26-1-versatile 1.2M
Put they in your home folder or where u want.
Now, lets run it.
Use the following command (run it from the folder you have the downloaded files) :
qemu-system-arm -M versatilepb -kernel vmlinuz-2.6.26-1-versatile -initrd initrd.img-2.6.26-1-versatile -hda debian_lenny_armel_small.qcow2 -append "root=/dev/sda1"
Wait a moment... Debian-armel running under qemu
Here are the configuration by default:
- Keyboard: British English
- Language: English
- Mirror: ftp.uk.debian.org
- Hostname: debian-armel
- Root password: root
- User account: user
- User password: user
Edit the system to fit your needs, im not going to explain how to do this, im asumming you know how to. If u don't, use the debian reference guide:
http://www.debian.org/doc/manuals/debian-reference/
Of course, you'll need to edit basic things as locales, network, ssh preferences, etc...
Edit your system, update, configure packages, etc...
Once edited and configured, quit you virtual machine.
Now, we are going to convert the qemu image to a raw image, mount the fs and copy to your SD
Assuming you still in the same folder as the qcow2 image of debian (for windows, google a little, im sure there are something to do the same):
qemu-img convert -O raw debian_lenny_armel_small.qcow2 debian.raw
With this will obtain the qcow2 converted to a raw file (without touching the original qcow2 file)
Now mount it where u want or follow this steps:
sudo mkdir /media/debian
Before mount, lets see where start the partition on the raw file:
sfdisk -l -uS debian.raw
U will see a list of partions under the raw file, use the first, like this one:
debian.raw1 * 63 20225834 20225772 83 Linux
Now, we know the / starts at 63, mount this partition
sudo mount -o loop,offset=$((63*512)) debian.raw /media/debian
Ok, we have our partition mounted now, lets make a copy in our EXT3 partition on SD.
Use the USB Storage function from android, sd card reader... and mount the EXT3 partition
Once mounted, copy everything from /media/debian to /media/yourSDext3mounted
cd /media/debian
sudo cp -a * /media/yourSDext3mounted/
If everithing works as expected, umount the systems /media/debian/ and /media/yourSDext3mounted or use the Android notif to disconnect the USB storage function
Check if everything is now in the SD EXT3. Open a terminal and adb shell
adb shell
cd /system/sd
ls
U'll see the Debian / extructure and the app & app-private
Of course dont worry about this, u can still using apps2sd and debian at the same time
Now, it's time to boot debian
We need some modded files from the G1 version to boot it:
Download from Megaupload: http://www.megaupload.com/?d=Q67SNOBC
Download from MediaFire: http://www.mediafire.com/?mxgcyk3whdt
Also, files attached to post (rename the extension to tar.gz)
Put the files into your FAT32 SD partition, no in a folder just in "/"
Now, it's time to give it a try
U have two ways:
Open a terminal window in your PC
adb shell
cd /sdcard/
sh installer.sh
sh bootdeb
Or:
Open up a terminal in your N1, like Terminal Emulator on Market
cd /sdcard/
sh installer.sh
sh bootdeb
PROFIT!!!
Enjoy your debian-armel on your N1
For the next chapter, how to run X with VNC Viewer
Bye and thanks for reading!

Looks like Klingon to me.

I have Debian running too now

Nice! Cant wait to try it out!

nice, i've been looking for a n1 debian how-to

Installing debian is pretty much the same as running it on your g1. I had it working the day after I got mine using the g1 instructions.

So, what's the reason or running debian on your phone?
Jst wondering
u

The reason by now is just fun hehe
But, if we can run it natively via fastboot, would be awesome hehe
Sorry for the delay guys, ill do it now, the last night was too late for me 4am here hehe
EDIT: Just give some time more, i going to try it with the Cm 5.0 beta 1

jairuncaloth said:
Installing debian is pretty much the same as running it on your g1. I had it working the day after I got mine using the g1 instructions.
Click to expand...
Click to collapse
I couldnt get chmod or installer.sh from the g1 instructions to work. I tried it both with bacon and modaco 1.3. I skipped the jesusfreak part though so maybe thats why. Anyway seeing confirming instructions would be nice.

Because the g1 files need to be modded first
I have it running it under modaco 1.3 and now im going to try it with the new b1 from cyanogen

Guide ready
Enjoy it!

Hi,
i have one question about debian. Is the network traffic routed trough android, or does debian has direct access to the wlan adapter for monitor mode and aircrack ?
meld0

it's using the same ip and mac, so is shared for both
If there are the apropiate drivers maybe, don't really know

Calling Linux Experts!!! hehe
Is there any way to create a boot.img bootable via fastboot to run the ext3 partition of sdcard with debian?

Driskol said:
Calling Linux Experts!!! hehe
Is there any way to create a boot.img bootable via fastboot to run the ext3 partition of sdcard with debian?
Click to expand...
Click to collapse
sorry for being noob in this matter but, why do i need debian on my phone? what does it give me?
amir

The answer is a choice, Android or a Full Desktop OS with Firefox, Thunderbird, OpenOffice, etc...

When its booting I'm getting an error:
/system/bin/bootdeb: line 61: chroot: command not found
Doing "find / -name chroot" only returns binaries within the debian image.
Any ideas?

Driskol said:
The answer is a choice, Android or a Full Desktop OS with Firefox, Thunderbird, OpenOffice, etc...
Click to expand...
Click to collapse
How well does Firefox run?
Can anyone take some pics or video?

Any instructions for creating and mounting linux as an img file instead of using separate partitions?

tetlee said:
When its booting I'm getting an error:
/system/bin/bootdeb: line 61: chroot: command not found
Doing "find / -name chroot" only returns binaries within the debian image.
Any ideas?
Click to expand...
Click to collapse
Maybe your rom doesn't have Busybox
EDIT: Im going to make a img version tutorial
Of course, this version was without the highmem kernel, now with more ram, more flawlessly

[REQUEST] Can someone post a guide to how to get Froyo on eMMC?

I don't want to dual-boot, even, just have a nice "normal" Nookie Froyo install on eMMC. I've seen several allude to the fact that it worked for them but no reviews of how they did it. I've backed up my 2.1 install with Clockwork so I'm not really worried about that.
TIA.

It's quite simple actually. All you need is basic knowledge of adb.
All disclaimers apply, I'm not responsible for any damage. Just know that mine is running on internal partitions. And the SD does mount too!
Before doing anything, I would recommend applying a dd from your partitions to your pc.
With, for example on mmcblk0p1 (boot) adb: dd if=/dev/block/mmcblk0p1 of=boot.img
You should do that for each partition to be safe (0p1 to 0p8).
All the following commands can be execute one after one, the separations are only there to makes things a bit more clear.
Then,
Boot to a working Nookie (NF) with your uSD fresh from burning, without any google apps, and without any uSD damaged errors.
Empty your internal system and copy uSD system over, by doing:
- adb shell mount -o remount,rw /dev/block/mmcblk1 / (---there is a space after the 1---)
- adb shell
- mkdir tmpfolder
- mount /dev/block/mmcblk0p5 tmpfolder
- cd tmpfolder
- rm -r * (---note that there is space after the r---)
- cd ..
- cp -r system/* tmpfolder (---this will take a few minutes---)
- umount tmpfolder
Click to expand...
Click to collapse
Then, you need to boot push the attached files (bottom of post) except for the 2 vold files to your boot partition: mmcblk0p1. Unzip, copy content, not zip.
You could very well replace uImage with the new Quickie overclocked uImage for froyo (see dev thread).
To push attached files to boot, do:
- mount /dev/block/mmcblk0p1 tmpfolder
- exit
- adb push [folder-containing-4-attached-files-except-vold.fstab] tmpfolder
- adb shell
- umount tmpfolder
Click to expand...
Click to collapse
I would also recommend erasing all your data. But that's up to you, if you want to keep your data on it. In any case, you can revert back with the data.img you created above . So next part you could skip, haven't tried skipping personally:
Non mandatory, but you could do:
- mount /dev/block/mmcblk0p6 tmpfolder
- cd tmpfolder
- rm -r *
- cd ..
- umount tmpfolder
Click to expand...
Click to collapse
Then you need to push vold.fstab and vold.conf (unzip volds, copy content) to system/etc
Copy vold's to system/etc:
- mount /dev/block/mmcblk0p5 tmpfolder
- exit
- adb push [folder-with-vold's] tmpfolder/etc/
- adb shell
- umount tmpfolder
- rm -r tmpfolder
- exit
Click to expand...
Click to collapse
Then shut down, remove uSD, and boot.
Again, you can choose to push the Quickie uImage, I you prefer, but the accelerometer doesn't work with it at the moment. The 950 kernel does sometimes crash on boot, but once booted is quite stable.
I think that's all folks. I could have been a bit vague at some times, but this should work. And if you made your imgs as recommended, you're bullet proof.
To revert back to initial state with img files, you need to copy files to sdcard and then dd:
- adb shell mount -o remount,rw /dev/block/mmcblk1p1 sdcard
- adb push XXX.img sdcard (--could take a few minutes--)
- dd if=XXXX.img of=/dev/block/mmcblk0pX
Click to expand...
Click to collapse
Do that for each partition.
For those who don't feel up to the task, I could make a CWR flashable zip file of all this. The only thing is, CWR dosen't boot on Nookie just yet. So you couldn't restore with a zip after the change.

[Before doing anything, I would recommend applying a dd from your partitions to your pc.
With, for example on mmcblk0p1 (boot) adb: dd if=/dev/block/mmcblk0p1 of=boot.img
You should do that for each partition to be safe (0p1 to 0p8).
[/QUOTE]
I am a little confused here. What are the names of the 7 other partitions? Thanks, Great guide btw!

See here.

Do you see improved speed and touch response running nookie from emmc?

im getting a "No such file or directory" error after "adb push [folder-with-vold's] tmpfolder/etc"
I created the directory but now it looks like i am stuck at the landscape android splash screen on boot...
any ideas? I am attempting to redo the whole process again just incase i missed something.

Sorry, there's a slash after etc.
Make sure you've copied the systen files, with "ls" inside tmpfolder where you copied system. Should be a etc folder there.
Sam

to the op: I'm not knocking you here, but do you have a basic idea of generic linux file hierarchy or operations in general? Getting a basic grasp on working with files in a linux terminal will make all of these operations make a lot more sense, since most "adb shell" commands are basic linux commands.

FastCR said:
to the op: I'm not knocking you here, but do you have a basic idea of generic linux file hierarchy or operations in general? Getting a basic grasp on working with files in a linux terminal will make all of these operations make a lot more sense, since most "adb shell" commands are basic linux commands.
Click to expand...
Click to collapse
Thanks but I don't see how that comment adds anything here.
Looks like the issue is above commands copy the actual system folder (not the contents of the folder) To the root of the partition. ls shows the folder "system" not the contents including etc. They are inside the folder but if the partition is mounted as system then the folder is redundant. Will check copying the contents and see if that helps.
Once I get it working in will post back to let others know
**** in the first block of code replace
Code:
- cp -r system tmpfolder (---this will take a few minutes---)
with
Code:
- cp -r system[B]/*[/B] tmpfolder (---this will take a few minutes---)
many thanks!

FastCR said:
to the op: I'm not knocking you here, but do you have a basic idea of generic linux file hierarchy or operations in general? Getting a basic grasp on working with files in a linux terminal will make all of these operations make a lot more sense, since most "adb shell" commands are basic linux commands.
Click to expand...
Click to collapse
Why would you go out of your way to say that? It's not constructive. As a junior member with three posts and 0 thanks after a year and a half, sharpen your teeth here at XDA before you act like a big shot.

Right thanks. Changed it.
Has it worked for you?
Sent from my HTC Desire using XDA App

samuelhalff said:
You could very well replace uImage with the new Quickie overclocked uImage for froyo (see dev thread).
Click to expand...
Click to collapse
Are you certain on this part? Last I read in that thread, Froyo needs a different minimum kernel.
UPDATE: Nevermind, I missed this updated effort.
Homer

Well, last time I checked, my NC was running at 950 on froyo with setcpu.
Check the forum. There's a nookie version of quickie. Except accelerometer doesn't work..

First, huge thanks to the second poster - great guide! Can we sticky this?
Second, yes I know what dd does, etc, I've been working with Linux for about ten years . I just don't know the ins and outs of embedded devices yet.

samuelhalff said:
Right thanks. Changed it.
Has it worked for you?
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
yeah i was up till 4am last night but got it working. first i tried to use my existing nf sd card... bad idea. would boot from emmc to the touch android screen to begin, but could not get past. i assume it was the issue on nookdevs because wifi was not enabled. so i removed the setupwizard.apk but somehow bricked and was unable to boot from emmc. so i took the following steps to get things working properly:
1. reimage boot and system from the stock 1.0.1 images and reset the nook to stock, didnt even touch. at the intro screen i just powered it off.
2. next i took a fresh nf sdcard and run steps from your post(with the correction to copy system contents)
3. from there i had a working nf from sdcard! i did my tweaks (google apps, market fix and button remapping from nookdevs froyo tips)
i might to put together a post with a more verbose set of instructions for a one stop froyo shop but if i do i will be sure to give you credit for your contribution.
thanks again!

Hi,
Second, yes I know what dd does, etc, I've been working with Linux for about ten years . I just don't know the ins and outs of embedded devices yet.
Click to expand...
Click to collapse
Well, that's a nice contrast. I've been working on Linux/Android for about 2 months now
I should have mentioned that the NF uSD Card must be a newly burnt image, without all the nookie tips added to it. Of course, your Google framework will crash if you port it without your data.
By the way, there's a nice trick to get past the numb android interface, simply touch every corner of the screen, starting with top left and going clockwise. You'll then be sent the your home screen, and from there you'll log on to google account again.
I think the best way of doing it would to create a flashable .zip, which I'll make tonight if I find the time and if people are really interested. But don't forget CWR dosen't work on nookie for the time being. The only way back would be through adb.
So, does anyone wish to have a flashable zip of this? Or will it be a waist of time?
Sam

samuelhalff said:
Hi,
Well, that's a nice contrast. I've been working on Linux/Android for about 2 months now
I should have mentioned that the NF uSD Card must be a newly burnt image, without all the nookie tips added to it. Of course, your Google framework will crash if you port it without your data.
By the way, there's a nice trick to get past the numb android interface, simply touch every corner of the screen, starting with top left and going clockwise. You'll then be sent the your home screen, and from there you'll log on to google account again.
I think the best way of doing it would to create a flashable .zip, which I'll make tonight if I find the time and if people are really interested. But don't forget CWR dosen't work on nookie for the time being. The only way back would be through adb.
So, does anyone wish to have a flashable zip of this? Or will it be a waist of time?
Sam
Click to expand...
Click to collapse
I would love a flashable .zip. I think many others would as well.

starkruzr said:
I would love a flashable .zip. I think many others would as well.
Click to expand...
Click to collapse
Can't wait for a flashable zip. Maybe even some cm7 release candidates would make me real happy.
Sent from Nooted NookColor using XDA App

How to switch from Ubuntu to Fedora 18

First of all, I need to acknowledge that I'm standing on the shoulders of giants, in composing this post. Mad props have to go to Rob Clark, for writing Freedreno and the Fedora installer I used. I also have to give credit to the people who made Ubuntu possible on the Touchpad (jshafer817, BodemM, castrwilliam, jcsullins, Calc1Programmer, Mystikal57, and lots of other people...I couldn't possibly post them all here, but that in no way diminishes my gratitude to them for all their hard work!)
Second of all, this is rough. Like "only shows kernel messages, good for nothing as it is" rough. I'm posting this to help spur on more work, so we can get things up and running faster.
Thirdly, you must have Ubuntu already installed to use this process, and it WILL destroy your Ubuntu install. I repeat, this WILL destroy your Ubuntu install. Only do this if you want to play with something that doesn't work right yet, and are willing to sacrifice something that does work to get it. You also need moboot 0.3.8 (which you already probably have if you have a working Ubuntu install).
Finally, no warranties. This will probably not work very well for you. I can't guarantee that bad things won't happen, and I will not be responsible if they do. I'm also LAUGHABLY FAR from being an expert, so look critically at these instructions before you go ahead, I can't guarantee I didn't miss anything. This is also probably not the most optimal method...the best method is probably what Rob posted in the readme, but that assumes you don't already have a Linux installed, which won't work so well for those of us with 16GB Touchpads.
Ok, having said all that, here's the good stuff.
Go to https://github.com/freedreno/touchpad-fedora and download the zip file.
Unzip it somewhere. There will be a bunch of scripts, a boot folder and a rootfs folder.
On your Touchpad, either in Android via a root terminal, or in WebOS with a root terminal, mount your /boot as read-write "sudo mount -o rw,remount /boot"
Go into the newly writable /boot, and delete uImage.Ubuntu (you'll need the free space...you can copy it to your computer or the SD Card if you want to reinstall it later). Copy uImage.Fedora to /boot. When you're done this, you should probably remount /boot as read-only "sudo mount -o ro,remount /boot"
Create a folder on your SD Card. Doesn't matter what you call it, but copy all the files from the rootfs folder there. There should be 11 of them, numbered 00 to 10.
Boot into WebOS, if you're not there already, and make sure you have WTerm installed and set up for root access.
Erase your Ubuntu partition, but don't destroy it. "mke2fs -F -T ext3 /dev/store/ubuntu-root" in WTerm. ***THIS IS DESTRUCTIVE***DANGER WILL ROBINSON***BE SURE BEFORE YOU DO THIS***
Make a temporary directory to mount your ubuntu partition on. "mkdir -p /tmp/linux"
Mount your newly formatted ubuntu partition. "mount /dev/store/ubuntu-root /tmp/linux"
CD into the folder you created that has the 00 through 10 files in it, and untar each one of them into /tmp/linux. The way I did this was to simply type "tar -C /tmp/linux -xvzf 00" and hit Tab. When it finished, I hit the up arrow, backspaced over the filename, then typed 01 and hit Tab, and so on for all eleven files.
When the files are all untarred, I typed "sync" (not sure why, it's in the script), and unmounted the temporary directory "umount /tmp/linux"
Last but not least, we have to rename the volume from ubuntu-root to fedora-root. "lvrename store ubuntu-root fedora-root"
That's it. You can close WTerm and reboot. When the moboot menu comes up, you'll see that Ubuntu is gone and Fedora is there, select it to boot. According to Rob's blog post, adb and rndis are working, so you can get access to a shell using adb, when it finishes booting.
Let me know how it works out for you, and please reply if you can improve my method (or if I screwed something up!).

I got rndis working...all I had to do was do it on my linux laptop, it didn't seem to work in Windows (surprise, surprise). With that running, I was able to get to yum via the adb shell. I yummed up gnome-shell, and it seemed to install OK, but I got an error when I tried to startx. It said there were no screens available, and it failed. I googled around a bit on that error, and it suggested I check into systemctl, where I noticed that "systemd-modules-load.service" had failed, and I saw module loading failure messages in dmesg, makes me think freedreno isn't loading right. I'll work on it some more after breakfast.

Turns out Rob forgot to add libdrm to the rootfs downloads. He added it last night to the git, and I've updated this guide to reflect that. Still doesn't boot to a GUI, but I'm closer than I was. startx throws an error about "no screens found", must need to be configured. I'll work on it later this evening and see what I can come up with.

Got it (sorta)! The libdrm version Rob supplied didn't quite match the Xorg version. A simple 'sudo yum update' and a reboot, and I have a GUI. Now to figure out how to add a user without a keyboard...

If this gets working I'm deff going to install. I'm dying for gnome 3 on a tablet.
Sent from my Nexus 7 using xda app-developers app

Head to your local Walmart (I think every town has one lol ) and buy the Bluetooth crapple keyboard....assuming it will work..but you might want to look it up...I just seen one there the other day.
Sent from my Galaxy Nexus using xda app-developers app
---------- Post added at 01:45 AM ---------- Previous post was at 01:41 AM ----------
OK quick search says yes it will pair...also if on the cheap..... http://dx.com/p/mini-bluetooth-keyboard-for-android-wince-nokia-symbian-s60-cellphones-black-37863 was successful under webos....so probably under android or Linux assuming your Bluetooth works.
Sent from my Galaxy Nexus using xda app-developers app

Great guide, can't wait to try this on my TP! It's been a while since I last messed around with it and this seems quite useful, as Gnome 3 is kinda optimized for touchscreens.
I was wondering though, does it matter which version of Ubuntu is installed or does it overwrite everything anyway?

https://github.com/freedreno/touchpad-fedora
Appears to have been a small update 4 days ago.
Sent from my Nexus 7 using xda app-developers app

[Q] How to check file system on internal storage?

I think there is something wrong with it. Some programs does not work well.
fsck always tell me it can not find /etc/fstab
e2fsck does not work on FAT disk

lzy0702 said:
I think there is something wrong with it. Some programs does not work well.
fsck always tell me it can not find /etc/fstab
e2fsck does not work on FAT disk
Click to expand...
Click to collapse
Can you please read before you post. especially the pinned threads, (most of all the fourth one down) they are pinned for a reason, and also stop us having to say this.
It will use the Linux extended file system that you will only be able to mount from a mac or linux machine, on windows you will need software to show mount and show this partition without using the Sony driver.

danw_oz said:
Can you please read before you post. especially the pinned threads, (most of all the fourth one down) they are pinned for a reason, and also stop us having to say this.
It will use the Linux extended file system that you will only be able to mount from a mac or linux machine, on windows you will need software to show mount and show this partition without using the Sony driver.
Click to expand...
Click to collapse
I have read those issue before. I am searching for a tool can run in my phone, because I can't find a computer now.

lzy0702 said:
I have read those issue before. I am searching for a tool can run in my phone, because I can't find a computer now.
Click to expand...
Click to collapse
No, read. Do not post questions in the General Section.
It is linux file system, so from a terminal window you can run unix commands to do checks on the file system.
at terminal window type man fsck
or google fsck (file system check)

danw_oz said:
No, read. Do not post questions in the General Section.
It is linux file system, so from a terminal window you can run unix commands to do checks on the file system.
at terminal window type man fsck
or google fsck (file system check)
Click to expand...
Click to collapse
Did you try this, did it help you?