FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > 64 Studio > 64 Studio User

 
 
LinkBack Thread Tools
 
Old 06-21-2010, 09:59 AM
Ralf Mardorf
 
Default 3.3 alpha USB stick issue

Hi



sorry, it's OT for this list.



I'm open to suggestions wich list might be qualified.



Anyway, information for the 8GB Intenso stick:



$ lsusb

Bus 002 Device 003: ID 1307:0165 Transcend Information, Inc. 2GB/4GB Flash Drive



$ su root -c "parted /dev/sdb print"

Model: Intenso Rainbow (scsi)

Disk /dev/sdb: 8087MB

Sector size (logical/physical): 512B/512B

Partition Table: loop



Number* Start* End**** Size*** File system* Flags

1***** 0.00B* 8087MB* 8087MB* fat32



The result of 'spinymouse@64studio:/media/INTENSO$ su root -c "rm -fr a64"':

Among others there were 76 files for /media/INTENSO/a64/spinymouse/Documents/[cryptic file names] causing 'Read-only file system' or an 'Input/output error'.



This two files are the sources, that were copied to the USB stick by using 64 Studio 3.3 alpha:

ls ~/Documents -a

.* ..* HowtoVST4Linux.abw* translation.txt



I installed lde, ncurses-hexedit and tweak. At the moment I'm only fine with hexeditor from the package ncurses-hexedit, while I had issues using lde and tweak.



Until now I only run



root@64studio:/home/spinymouse# cd /media/INTENSO/a64

root@64studio:/media/INTENSO/a64# hexeditor -r



Later today I'll search the web for the flags that 'delete' the directory entries for the file names or the complete /a64 directory. If anybody has information about this or a better idea how to remove the directory /media/INTENSO/a64, any hints are welcome.



I don't know when this happened and what's the cause for this is.



An issue for 64 Studio 3.3 alpha, when I copied the files? A broken USB stick? Or an issue for Suse 10.2, when I tried to delete the files the first time. Or anything else.



FWIW I tried to remove the files with 3.0 beta and 3.3 alpha too.

I wonder if I should set up Windows and try to run the system's error check, that also comes with a repair function.



# dosfsck -nv /dev/sdb

[snip]

/a64/spinymouse/.mozilla/056000000.00�17

* Start cluster beyond limit (547581816 > 1970420). Truncating file.

/a64/spinymouse/.mozilla/056000000.00�17

* File size is 412154930 bytes, cluster chain length is 0 bytes.

* Truncating file to 0 bytes.

/a64/spinymouse/.mozilla/057000000.00215s

* Start cluster beyond limit (18446744071648172919 > 1970420). Truncating file.

/a64/spinymouse/.mozilla/057000000.00215s

* File size is 2595958557 bytes, cluster chain length is 0 bytes.

* Truncating file to 0 bytes.

/a64/spinymouse/.mozilla/�230;�142223235.17720422

* Directory has non-zero size. Fixing it.

/a64/spinymouse/.mozilla/�230;�142223235.17720422

* Start cluster beyond limit (18446744071908836044 > 1970420). Truncating file.

Checking for unused clusters.

Reclaimed 9724 unused clusters (39829504 bytes).

Checking free cluster summary.

Free cluster summary wrong (542661 vs. really 562104)

* Auto-correcting.

Leaving file system unchanged.

/dev/sdb: 3278 files, 1408315/1970419 clusters



At the moment I'm running

# dosfsck -av /dev/sdb

[snip]

/a64/spinymouse/.mozilla/054000000.00�221

* Directory has non-zero size. Fixing it.

/a64/spinymouse/.mozilla/054000000.00�221

* Start cluster beyond limit (18446744073244898098 > 1970420). Truncating file.

/a64/spinymouse/.mozilla/055000000.00T07

* Start cluster beyond limit (1221107160 > 1970420). Truncating file.

/a64/spinymouse/.mozilla/055000000.00T07

* File size is 793081378 bytes, cluster chain length is 0 bytes.

* Truncating file to 0 bytes.

/a64/spinymouse/.mozilla/056000000.00�17

* Start cluster beyond limit (547581816 > 1970420). Truncating file.

/a64/spinymouse/.mozilla/056000000.00�17

* File size is 412154930 bytes, cluster chain length is 0 bytes.

* Truncating file to 0 bytes.

/a64/spinymouse/.mozilla/057000000.00215s

* Start cluster beyond limit (18446744071648172919 > 1970420). Truncating file.

/a64/spinymouse/.mozilla/057000000.00215s

* File size is 2595958557 bytes, cluster chain length is 0 bytes.

* Truncating file to 0 bytes.

/a64/spinymouse/.mozilla/�230;�142223235.17720422

* Directory has non-zero size. Fixing it.

/a64/spinymouse/.mozilla/�230;�142223235.17720422

* Start cluster beyond limit (18446744071908836044 > 1970420). Truncating file.

Reclaiming unconnected clusters.



I'm not sure if it's working or if it hung up. I guess it's the latter.



Cheers!



Ralf


_______________________________________________
64studio-users mailing list
64studio-users@lists.64studio.com
http://lists.64studio.com/mailman/listinfo/64studio-users
 

Thread Tools




All times are GMT. The time now is 04:51 PM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org