I am unable to mount my 64GB PNY thumb drive It says it is inaccessible and I have looked at the fstab and mounts I even tried a manual mount and nothing. I really need the data on there. Any good freeware that I can use for an EXT4 partition would be great. Any suggestions?
Is it not showing up at all??
If you can see it /dev then try a fschk on it to repair the file system.
My suggestion is to show us that manual mount. We realy can not see from your statement what you did and what happened then. Copy/paste that between CODE tags in a post. You get the CODE tags by clicking on the # button in the toolbar of the post editor.
Same for you saying “I have looked at the fstab”, you should post
cat /etc/fstab
so we can see, else we can not know what you saw.
On Fri, 10 May 2013 16:56:04 +0000, mccalleyt wrote:
> I am unable to mount my 64GB PNY thumb drive It says it is inaccessible
> and I have looked at the fstab and mounts I even tried a manual mount
> and nothing. I really need the data on there. Any good freeware that I
> can use for an EXT4 partition would be great. Any suggestions?
Does it show up in the device list when you plug it in? For example:
lsscsi
should show that it’s there. If it doesn’t, then the problem is likely
hardware related. If it does, then a fsck might help.
BTW, it’s generally not recommended that journalling filesystems be used
on USB flash drives - even with wear leveling, all they tend to do is
wear the drives out faster. Using something like fat32 or ext2 would be
a better option (for future reference).
Jim
–
Jim Henderson
openSUSE Forums Administrator
Forum Use Terms & Conditions at http://tinyurl.com/openSUSE-T-C
On 2013-05-11 05:07, Jim Henderson wrote:
> BTW, it’s generally not recommended that journalling filesystems be used
> on USB flash drives - even with wear leveling, all they tend to do is
> wear the drives out faster. Using something like fat32 or ext2 would be
> a better option (for future reference).
Or ext4 without journal:
mke2fs -t ext4 -L SomeName -O ^has_journal /dev/sdX1
The advantage is that ext4 has extents. Reference:
> http://www.sysresccd.org/Sysresccd-manual-en_How_to_install_SystemRescueCd_on_an_USB-stick#D.29_Installation_from_Linux_using_an_ext3.2Fext4_filesystem
The future would be something like F2fs:
> <http://www.h-online.com/open/features/Kernel-Log-Coming-in-3-8-Part-1-Filesystems-and-storage-1788524.html>
–
Cheers / Saludos,
Carlos E. R.
(from 12.1 x86_64 “Asparagus” at Telcontar)
It does show up on the device list It is just the partition is somehow inaccessable by the system’s auto-mount.
*******:/home/******* # lsscsi
[0:0:0:0] disk ATA TOSHIBA MK5055GS FG00 /dev/sda
[1:0:0:0] cd/dvd hp DVDRAM GT20L DC05 /dev/sr0
*******:/home/***** # cat /etc/fstab
/dev/disk/by-id/ata-TOSHIBA_MK5055GSX_89N3S0I6S-part1 swap swap defaults 0 0
/dev/disk/by-id/ata-TOSHIBA_MK5055GSX_89N3S0I6S-part2 / ext4 acl,user_xattr 1 1
proc /proc proc defaults 0 0
sysfs /sys sysfs noauto 0 0
debugfs /sys/kernel/debug debugfs noauto 0 0
usbfs /proc/bus/usb usbfs noauto 0 0
devpts /dev/pts devpts mode=0620,gid=5 0 0
Ohh sorry the terminal hangs I let it go for about 30 min (while looking at dI’m not sure exactally if the system didn’t finish a delay write to the part. or not. I don’t have a ton of exper. with linux just yet but I’m a software (mostly microsoft), hardware and network guru for the last 12 years. I just need a bit of a nudge on doing either a part recov./file extract to back up that drive then take robin_listas’s and hendersj’s advise (Thank You Sooooo Much) advice on the partition config. It really shows my level of knowledge on linux. I will say this I have got rid of all my windows software on all comps I have just to force myself to learn tux. I finally took the leap to finally not be so scared of it LMFAO.
Thanks,
Tyler McCalley
Sorry here is the FSTAB in a bit more clean setup…
/dev/disk/by-id/ata-TOSHIBA_MK5055GSX_89N3S0I6S-part1 swap swap defaults 0 0
/dev/disk/by-id/ata-TOSHIBA_MK5055GSX_89N3S0I6S-part2 / ext4 acl,user_xattr 1 1
proc /proc proc defaults 0 0
sysfs /sys sysfs noauto 0 0
debugfs /sys/kernel/debug debugfs noauto 0 0
usbfs /proc/bus/usb usbfs noauto 0 0
devpts /dev/pts devpts mode=0620,gid=5 0 0
I’m just hoping everything will be there I really need it… Thanks so far for the help.
Tyler McCalley
“You can never know everything, but you can keep trying till you die, because knowledge IS power and great power can bring great prestige.”
This is from you:
It does show up on the device list It is just the partition is somehow inaccessable by the system’s auto-mount.
Again something not backed by any computer evidence. And then you show
*******:/home/******* # lsscsi
[0:0:0:0] disk ATA TOSHIBA MK5055GS FG00 /dev/sda
[1:0:0:0] cd/dvd hp DVDRAM GT20L DC05 /dev/sr0
which clearly has only your rotating system disk and a CD/DVD device. No others!
Thus IMHO it is not seen at all, this being some hardware problem as Jim says.
And about your fstab **(not **FSTAB), it shows that partition 1 of the revolving disk is to be used for swap and part2 to be mounted at /. That is all. I do not know execatly why you looked at it, but at least we all can look at it now and it contains noything with respect to the not available device.
On Sat, 11 May 2013 03:33:06 +0000, Carlos E. R. wrote:
> Or ext4 without journal:
True, I always forget that’s an option with ext4.
Jim
–
Jim Henderson
openSUSE Forums Administrator
Forum Use Terms & Conditions at http://tinyurl.com/openSUSE-T-C
On Sat, 11 May 2013 06:46:01 +0000, mccalleyt wrote:
> It does show up on the device list It is just the partition is somehow
> inaccessable by the system’s auto-mount.
What’s the output of:
fdisk -l [devicename]
?
Jim
–
Jim Henderson
openSUSE Forums Administrator
Forum Use Terms & Conditions at http://tinyurl.com/openSUSE-T-C
[0:0:0:0] disk ATA TOSHIBA MK5055GS FG00 /dev/sda
[1:0:0:0] cd/dvd hp DVDRAM GT20L DC05 /dev/sr0
[6:0:0:0] disk Multi Flash Reader 1.00 /dev/sdb
[7:0:0:0] disk PNY USB 2.0 FD 1100 /dev/sdc
dev/disk/by-id/ata-TOSHIBA_MK5055GSX_89N3S0I6S-part1 swap swap defaults 0 0
/dev/disk/by-id/ata-TOSHIBA_MK5055GSX_89N3S0I6S-part2 / ext4 acl,user_xattr 1 1
proc /proc proc defaults 0 0
sysfs /sys sysfs noauto 0 0
debugfs /sys/kernel/debug debugfs noauto 0 0
usbfs /proc/bus/usb usbfs noauto 0 0
devpts /dev/pts devpts mode=0620,gid=5 0 0
Sorry I pulled a dumb move I didn’t have the drive plugged in. I was sleep deprived and not paying attention. I’m really sorry for wasting time. Here is the fstab and lsscsi outputs.
***You can never know everything, but you can keep trying till you die, because knowledge IS power and great power can bring great prestige. ***- Tyler McCalley
Disk /dev/sdc: 65.5 GB, 65451982848 bytes
255 heads, 63 sectors/track, 7957 cylinders, total 127835904 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0xc3072e18
Device Boot Start End Blocks Id System
/dev/sdc1 2048 127834111 63916032 83 Linux
Here is the fdisk -l output for ya it does show that it has a valid partition.
You can never know everything, but you can keep trying till you die, because knowledge IS power and great power can bring great prestige. - Tyler McCalley
Now you have put in two new devices! We realy can not help you when you change things every time. And particulary not when you not explain that!
Now this new information shows sdb and sdc. I assume that sdc is the device you are talking about because it sdays there PNY.
Now do what Jim asks for
fdisk -l /dev/sdc
But do not add/remove anything or we will have a new situation again.
Anf forget about that fstab. There is nothing interesting there.
It shows there is a (and only one) partition. I do not know what you mean by “valid”.
Now do a
mount -t ext4 /dev/sdc1 /mnt
Try mounting it manually and see if any errors.
as root
mount -t ext4 /dev/sdc1 /media
not normally we would want a better mount point but /media is normally empty so you would have to create a point but this is only a test to see if it will mount and see and error messages. SO don’t do it this way except as a test.
report results
On 2013-05-11 20:16, Jim Henderson wrote:
> On Sat, 11 May 2013 03:33:06 +0000, Carlos E. R. wrote:
>
>> Or ext4 without journal:
>
> True, I always forget that’s an option with ext4.
I always remember that the option exists, but I never remember how to do
it 
(fortunately, I remember the file where I wrote it)
–
Cheers / Saludos,
Carlos E. R.
(from 12.1 x86_64 “Asparagus” at Telcontar)
On 2013-05-11 20:56, hcvv wrote:
> It shows there is a (and only one) partition. I do not know what you
> mean by “valid”.
> Now do a
>
> Code:
> --------------------
> mount -t ext4 /dev/sdc1 /mnt
> --------------------
I would add a “-v” to it. For “verbose”. 
Alternatively, we have to tail the message file. And in any case, we
might anyway…
–
Cheers / Saludos,
Carlos E. R.
(from 12.1 x86_64 “Asparagus” at Telcontar)
It is the sdc1 that is the partition. I was saying it wasn’t a valid partition because of a write error that may have occured because I do pull the drive without doing a eject through the device notification area on the KDE system tray. Me being a noob to tux I didn’t realize ext4 was a journaled filesystem. Yes sdc is the correct drive.
***You can never know everything, but you can keep trying till you die, because knowledge IS power and great power can bring great prestige. - ***Tyler McCalley