[Desire Android Development] Borat38:
Help needed reading log

I ran Script Manager and was surprised to find the log below:

Command:

'/mnt/sdcard/GetlogsInteractive.sh'

-------------

Out:

sh-3.2$ exec sh '/mnt/sdcard/GetlogsInteractive.sh'

opendir failed, Permission denied

/mnt/sdcard/GetlogsInteractive.sh: line 9: /dev/dal.txt: Permission denied

/mnt/sdcard/GetlogsInteractive.sh: line 10: /dev/dal.txt: No such file or directory

/mnt/sdcard/GetlogsInteractive.sh: line 12: /dev/misc.txt: Permission denied

/mnt/sdcard/GetlogsInteractive.sh: line 13: /dev/misc.txt: No such file or directory

/mnt/sdcard/GetlogsInteractive.sh: line 15: /dev/property.txt: Permission denied

/mnt/sdcard/GetlogsInteractive.sh: line 16: /dev/property.txt: No such file or directory

/mnt/sdcard/GetlogsInteractive.sh: line 18: /dev/system.txt: Permission denied

/mnt/sdcard/GetlogsInteractive.sh: line 19: /dev/system.txt: No such file or directory

The Data2SD signature is

/mnt/sdcard/GetlogsInteractive.sh: line 24: [: ==: unary operator expected

/mnt/sdcard/GetlogsInteractive.sh: line 30: [: ==: unary operator expected

/mnt/sdcard/GetlogsInteractive.sh: line 38: [: ==: unary operator expected

The Data2SD vesion is unrecognized!

opendir failed, Permission denied

opendir failed, Permission denied

opendir failed, Permission denied

/cache/data2sd.ver: Permission denied

opendir failed, Permission denied

opendir failed, Permission denied

/mnt/sdcard/GetlogsInteractive.sh: line 99: /cache/dalvik.ver: Permission denied

/mnt/sdcard/GetlogsInteractive.sh: line 100: /cache/dalvik.ver: Permission denied

/mnt/sdcard/GetlogsInteractive.sh: line 101: /cache/dalvik.ver: Permission denied

/mnt/sdcard/GetlogsInteractive.sh: line 102: /cache/dalvik.ver: Permission denied

/mnt/sdcard/GetlogsInteractive.sh: line 103: /cache/dalvik.ver: Permission denied

/mnt/sdcard/GetlogsInteractive.sh: line 104: /cache/dalvik.ver: Permission denied

opendir failed, Permission denied

/cache/dalvik.ver: Permission denied

fdisk: can't open '/dev/block/mmcblk0p1': Permission denied

tar: removing leading '/' from member names

The Log capture utility has completed successfully.

Additional logs are available in the file /sdcard/Data2SDlog.tar.gz

---------------------------------

Log creation Utility by Droidzone

---------------------------------

Starting Logs on Sun Jul 24 09:09:53 PHT 2011

---------------------------------

Data2SD Version Information:

File System Information:

---------------------------------

File structure of /data

File structure of /system/data

---------------------------------

File structure of /data [Actual mount for ext]

---------------------------------

Dalvik-cache information:

---------------------------------

Device Characteristics Information:

-----------------------------------

Partition Information:

----------------------

Available Diskspace and Usage on Nand (/system):

/system: 256000K total, 192148K used, 63852K available (block size 4096)

Available Diskspace and Usage on ext4 (/data):

/data: 1965392K total, 564824K used, 1400568K available (block size 4096)

Additional Logs:

----------------------

Ext2 FileSystem Checker Information for ext4 [e2fsck log]

No e2fsck logs found!

----------------------

Adjustable Tunable Filesystem Information for ext4 [tune2fs log]

No tune2fs logs found!

See the Cache folder in the zip for System logs created during Bootup

Log Utility has finished its work at Sun Jul 24 09:09:53 PHT 2011

--------------------------------

--------------------------------

**I'm quite taken aback. What could be wrong with my phone? It's functioning perfectly, no bugs or speed problems. Never seen this kind of log before. Does anyone know how to read this, and help me out pls? Thanks.

EDIT: Never mind. I think I've found out the culprit for this log result. Before this log, a restart ended up in a bootloop. I remember reading somewhere that rebooting through snq's powermenu or ROM Manager is not advisable because the chance for data corruption is high. I think what happened was the final successful reboot was able to fix the missing files. I'll reboot the old-fashioned way from now on.