Quote:
Originally Posted by Keez
[root@[192_168_15_244] root]# mount
rootfs on / type rootfs (rw)
* * * *
/dev/mmcblk0p3 on /var/local type ext3 (rw,relatime,errors=continue,data=writeback)
fsp on /mnt/us type fuse.fsp (rw,nosuid,nodev,noatime,user_id=0,group_id=0)
/dev/loop/0 on /mnt/base-us type vfat (rw,noexec,noatime,nodiratime,fmask=0022,dmask=002 2,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
/dev/mmcblk0p1 on /mnt/mmc-base type ext3 (rw,relatime,data=writeback)
|
OK, that looks like "diags" mode;
The mounting of the "main" mode file system has worked;
Using the "ls -l /mnt/mmc-base/" command;
Look for the presence of the next directory in the expected path;
If found, "step down" one more directory level by appending the found directory to the above command, and repeat the command.
What you will be doing is "walking" down the entire pathname, looking for the first missing directory in the path:
/mnt/base-mmc/amazon/screen_saver/600x800
Translation:
We know that /mnt/base-mmc is present, that it has storage mounted on it (mmcblk0p1), that the file system is read/write.
Now check:
/mnt/base-mmc/amazon
/mnt/base-mmc/amazon/screen_saver
/mnt/base-mmc/amazon/screen_saver/600x800
The "ls -l ..." command will also be reporting the ownership and permissions.
Both the first missing directory in the path **and** the permissions of the ones which are present in the path are important to trouble shooting this problem.
I have been working nearly 20 hours straight today - I may have to crash for awhile, RSN.
But someone else can pick up this thread, the above should tell them the types of problems I am looking for.