Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
hi there
i have flash 32gb it is damage when i write fdisk -l
** Disk /dev/sda: 250.1 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0xc4e779f7
Device Boot Start End Blocks Id System
/dev/sda1 1 3825 30724281 7 HPFS/NTFS
/dev/sda2 3826 26772 184321777+ f W95 Ext'd (LBA)
/dev/sda3 * 26773 26798 204800 83 Linux
/dev/sda4 26798 30401 28945142+ 8e Linux LVM
/dev/sda5 3826 26772 184321746 7 HPFS/NTFS
Disk /dev/dm-0: 24.4 GB, 24352129024 bytes
255 heads, 63 sectors/track, 2960 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00000000
Disk /dev/dm-0 doesn't contain a valid partition table
Disk /dev/dm-1: 5284 MB, 5284823040 bytes
255 heads, 63 sectors/track, 642 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00000000
Disk /dev/dm-1 doesn't contain a valid partition table
when i do less /dev
** brw-rw----. 1 root disk 253, 0 2010-02-20 22:05 dm-0
brw-rw----. 1 root disk 253, 1 2010-02-20 22:05 dm-1
my flash convert from directory to block device
how can i solve it ?
hi there
i have flash 32gb it is damage when i write fdisk -l
** Disk /dev/sda: 250.1 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0xc4e779f7
Device Boot Start End Blocks Id System
/dev/sda1 1 3825 30724281 7 HPFS/NTFS
/dev/sda2 3826 26772 184321777+ f W95 Ext'd (LBA)
/dev/sda3 * 26773 26798 204800 83 Linux
/dev/sda4 26798 30401 28945142+ 8e Linux LVM
/dev/sda5 3826 26772 184321746 7 HPFS/NTFS
Disk /dev/dm-0: 24.4 GB, 24352129024 bytes
255 heads, 63 sectors/track, 2960 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00000000
Disk /dev/dm-0 doesn't contain a valid partition table
Disk /dev/dm-1: 5284 MB, 5284823040 bytes
255 heads, 63 sectors/track, 642 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00000000
Disk /dev/dm-1 doesn't contain a valid partition table
when i do less /dev
** brw-rw----. 1 root disk 253, 0 2010-02-20 22:05 dm-0
brw-rw----. 1 root disk 253, 1 2010-02-20 22:05 dm-1
my flash convert from directory to block device
how can i solve it ?
Could you print the contents of /dev/mapper/? I don't see why a flash drive would be showing up as dm-0 or dm-1. Even if it is encrypted, there should be a /dev/sdb or /dev/sdc for the drive and /dev/sdb1 or /dev/sdc1 for the partition. Are any of your partitions encryped, part of a RAID array or are you using LVM?
Also, to examine a device you can use `file -s':
sudo file -s /dev/dm-0
Another thing to do is to run `sudo tail -f /var/log/messages' before inserting the pendrive. This will clear up what device is detected, the node it uses and whether the kernel has found partitions on the device.
Could you print the contents of /dev/mapper/? I don't see why a flash drive would be showing up as dm-0 or dm-1. Even if it is encrypted, there should be a /dev/sdb or /dev/sdc for the drive and /dev/sdb1 or /dev/sdc1 for the partition. Are any of your partitions encryped, part of a RAID array or are you using LVM?
Also, to examine a device you can use `file -s':
sudo file -s /dev/dm-0
Another thing to do is to run `sudo tail -f /var/log/messages' before inserting the pendrive. This will clear up what device is detected, the node it uses and whether the kernel has found partitions on the device.
when i do file -s /dev/dm-0 show this message
[root@Fedora12 ~]# file -s /dev/dm-0
/dev/dm-0: Linux rev 1.0 ext4 filesystem data (needs journal recovery) (extents) (large files) (huge files)
/dev/dm-0 and /dev/dm-1 are probably logical volumes from the LVM volume.
It is normal that they wouldn't have a valid partiton table if they are partitions themselves.
Please post your /etc/fstab file. I am thinking that these two devices are from /dev/sda and not your flash drive, unless your system runs of a flash drive.
Look at your kernel messages from boot up. (enter dmesg or look in /var/log/ for logs starting with "boot.". If the flash drive is a second drive, then you need to find out what it is first. There may have been a problem with the flash drive, and the kernel didn't detect any partitions on it, but it has nothing to do with dm-0 or dm-1.
You line "less /dev" doesn't make sense. Using a directory as an argument to less, it presents you with files in the directory to choose from. Maybe you meant to use "ls /dev/".
Gather informations about your devices so you know which device is what. Then you know where to look further.
Knowing the name of the problem device, collect evidence such as boot error messages, which may indicate what the problem is with your device.
address the problem directly after you are armed with the information you need. If the filesystem is faulty, you may be able to repair it. If the device itself is faulty, look into whether you can produce an image file(s) and recover your files.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.