Sponsored Content
Operating Systems Linux Ubuntu Memory card partition table corrupted after unsafe removal Post 302898743 by Perderabo on Wednesday 23rd of April 2014 01:46:22 PM
Old 04-23-2014
I find it hard to believe that an unsafe removal trashed the partition table. Unsafe removals are supposed to trash the file system metadata. I never believe anything that fdisk has to say. Switch to a better utility like parted. I just plugged a factory fresh thumb drive into my workstation....
Code:
#
# ls -ltr | tail -5
crw------- 1 root  root   442, 10242 Apr 23 13:28 usbdev6.3_ep02
crw------- 1 root  root    21,     2 Apr 23 13:28 sg2
brw-r----- 1 root  disk     8,    16 Apr 23 13:28 sdb
brw-r----- 1 root  disk     8,    17 Apr 23 13:28 sdb1
crw-rw-rw- 1 root  tty      5,     2 Apr 23 13:34 ptmx
# parted /dev/sdb print

Model: Lexar USB Flash Drive (scsi)
Disk /dev/sdb: 8017MB
Sector size (logical/physical): 512B/512B
Partition Table: msdos

Number  Start   End     Size    Type     File system  Flags
 1      12.3kB  8017MB  8017MB  primary  fat32        lba

Information: Don't forget to update /etc/fstab, if necessary.

# fsck -n /dev/sdb1
fsck 1.39 (29-May-2006)
dosfsck 2.11, 12 Mar 2005, FAT32, LFN
Free cluster summary wrong (4294967295 vs. really 1953276)
  Auto-correcting.
Leaving file system unchanged.
/dev/sdb1: 1 files, 1/1953277 clusters
#

So /dev/sdb and /dev/sdb1 popped into existence when I plugged in my thumb drive. /dev/sdb is the physical device. It has a partition table that defines partition 1. So, predictably, I also get a device called /dev/sdb1 to correspond to my partition 1.

Note that I ran fsck on /dev/sdb1, not /dev/sdb. If I want to mount my thumb drive I do this....
Code:
# mount /dev/sdb1 /mnt
# df -k /mnt
Filesystem           1K-blocks      Used Available Use% Mounted on
/dev/sdb1              7813108         4   7813104   1% /mnt
#


You ran fsck on /dev/sdc. That was probably a mistake and it may have trashed your partition table. It should have been /dev/sdc1.
 

10 More Discussions You Might Find Interesting

1. Solaris

recovery partition table from fdisk?

I have two disks on a sun blade 100. I just installed a solaris8 on the first disk. The installation was successful. But the problem is now I lost all data / partition on my second hard disk. The possible reason could be: 1. I used default web start install. During the installation I didn't... (2 Replies)
Discussion started by: motor98
2 Replies

2. UNIX for Advanced & Expert Users

resizing the partition table

Host 1 ------- Part Tag Flag Cylinders Size Blocks 0 root wm 0 - 1911 18.56GB (1912/0/0) 38913024 1 swap wu 1912 - 5434 34.19GB (3523/0/0) 71700096 2 backup wm 0 - 14086 136.71GB ... (5 Replies)
Discussion started by: sriny
5 Replies

3. UNIX for Advanced & Expert Users

modify a predefined partition table on Solaris

I want to modify a predefined partition on Solaris. This predefined partion has 51 GB. I want to partition it as two partition. One is 5G, another one is about 46 GB. I want to use these commands: #format specify disk #partition # modify The system told me that ' Cannot modify disk... (1 Reply)
Discussion started by: duke0001
1 Replies

4. Solaris

Can I put my own tags in a partition table

I have X4500 running Solaris 10. I have formatted a disk and created partition table as given below. Specify disk (enter its number): 0 selecting c0t0d0 /dev/dsk/c0t0d0s0 is part of active ZFS pool zpool1. Please see zpool(1M). FORMAT MENU: disk - select a disk ... (3 Replies)
Discussion started by: bharu_sri
3 Replies

5. Solaris

usb memory card

I just got a removable memory card. I tried the following bu still my OS solaris x86 cannot detect it and also i got an error touch /reconfigure init 0 I inserted the removable memory card and the powered the system on I got the following on at boot up when i fully logged in I did ... (2 Replies)
Discussion started by: seyiisq
2 Replies

6. Slackware

Help me!!!! - Slackware 12 Issue - Invalid Partition table

Hi All, I am a linux newbie. After working with my loveable FEDORA 10 for months, i found it a bit slower. I wanted to try with slackware this time. I already had Windows XP and fedora in my 80 GB SATA disk. Now i allotted 15 GB ( SWAP + / + /home/usr ). During my installation i encountered no... (5 Replies)
Discussion started by: beinthemiddle
5 Replies

7. Solaris

Manually editing partition table

I'm manually editing the partition table purely for experimenting. I did prtvtoc /dev/dsk/c1t0d0s2 > /tmp/prtvtoc I'm trying to split up partition 5 to make partition 6. I'm running into a cylinder boundary error on partition 6. Any clues? # vi /tmp/prtvtoc "/tmp/prtvtoc" 23 lines, 769... (1 Reply)
Discussion started by: adelsin
1 Replies

8. SCO

Backup MBR an Partition Table

hi How can I backup MBR an Partition Table of SCO 5.0.6? (7 Replies)
Discussion started by: ccc
7 Replies

9. Red Hat

This doesn't look like a partition table Probably you selected the wrong device.

Hi, I need to mount the device from this device # fdisk -l . . . Disk /dev/sdas: 2000.4 GB, 2000365289472 bytes 255 heads, 63 sectors/track, 243197 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size... (0 Replies)
Discussion started by: justbow
0 Replies

10. Programming

How do I partition an Oracle 11g Table?

Hello, I have a database called "audit_database" and I want to create two tables. Table 1 = Table 1 Table 2 = Audit I want to partition the Audit table into partitions grouped by month. I'm not familiar with table partitioning but doing some reading online shows that it can be done but... (4 Replies)
Discussion started by: bbbngowc
4 Replies
fmthard(1M)                                                                                                                            fmthard(1M)

NAME
fmthard - populate label on hard disks SYNOPSIS
SPARC fmthard -d data | -n volume_name | -s datafile [-i] /dev/rdsk/c? [t?] d?s2 fmthard -d data | -n volume_name | -s datafile [-i] /dev/rdsk/c? [t?] d?s2 The fmthard command updates the VTOC (Volume Table of Contents) on hard disks and, on systems, adds boot information to the Solaris fdisk partition. One or more of the options -s datafile, -d data, or -n volume_name must be used to request modifications to the disk label. To print disk label contents, see prtvtoc(1M). The /dev/rdsk/c?[t?]d?s2 file must be the character special file of the device where the new label is to be installed. On systems, fdisk(1M) must be run on the drive before fmthard. If you are using an system, note that the term ``partition'' in this page refers to slices within the fdisk partition on machines. Do not confuse the partitions created by fmthard with the partitions created by fdisk. The following options are supported: -d data The data argument of this option is a string representing the information for a particular partition in the current VTOC. The string must be of the format part:tag:flag:start:size where part is the partition number, tag is the ID TAG of the partition, flag is the set of permission flags, start is the starting sector number of the partition, and size is the number of sectors in the partition. See the description of the datafile below for more information on these fields. -i This option allows the command to create the desired VTOC table, but prints the information to standard output instead of modifying the VTOC on the disk. -n volume_name This option is used to give the disk a volume_name up to 8 characters long. -s datafile This option is used to populate the VTOC according to a datafile created by the user. If the datafile is "-", fmthard reads from standard input. The datafile format is described below. This option causes all of the disk par- tition timestamp fields to be set to zero. Every VTOC generated by fmthard will also have partition 2, by convention, that corresponds to the whole disk. If the input in datafile does not specify an entry for partition 2, a default partition 2 entry will be created auto- matically in VTOC with the tag V_BACKUP and size equal to the full size of the disk. The datafile contains one specification line for each partition, starting with partition 0. Each line is delimited by a new-line character ( ). If the first character of a line is an asterisk (*), the line is treated as a com- ment. Each line is composed of entries that are position-dependent, separated by "white space" and having the fol- lowing format: partition tag flag starting_sector size_in_sectors where the entries have the following values: partition The partition number. Currently, for Solaris SPARC, a disk can have up to 8 partitions, 0-7. Even though the partition field has 4 bits, only 3 bits are currently used. For , all 4 bits are used to allow slices 0-15. Each Solaris fdisk partition can have up to 16 slices. tag The partition tag: a decimal number. The following are reserved codes: 0 (V_UNASSIGNED), 1 (V_BOOT), 2 (V_ROOT), 3 (V_SWAP), 4 (V_USR), 5 (V_BACKUP), 6 (V_STAND), 7 (V_VAR), and 8 (V_HOME). flag The flag allows a partition to be flagged as unmountable or read only, the masks being: V_UNMNT 0x01, and V_RONLY 0x10. For mountable partitions use 0x00. starting_sector The sector number (decimal) on which the partition starts. size_in_sectors The number (decimal) of sectors occupied by the partition. You can save the output of a prtvtoc command to a file, edit the file, and use it as the datafile argument to the -s option. See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWcsu | +-----------------------------+-----------------------------+ uname(1), format(1M), prtvtoc(1M), attributes(5) Only fdisk(1M), installgrub(1M) Special care should be exercised when overwriting an existing VTOC, as incorrect entries could result in current data being inaccessible. As a precaution, save the old VTOC. For disks under one terabyte, fmthard cannot write a VTOC on an unlabeled disk. Use format(1M) for this purpose. 11 Apr 2005 fmthard(1M)
All times are GMT -4. The time now is 03:00 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy