Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
[root@kids ~]# fdisk /dev/sdb
Command (m for help): m
a toggle a bootable flag
b edit bsd disklabel
c toggle the dos compatibility flag
d delete a partition
l list known partition types
m print this menu
n add a new partition
o create a new empty DOS partition table
p print the partition table
q quit without saving changes
s create a new empty Sun disklabel
t change a partition's system id
u change display/entry units
v verify the partition table
w write table to disk and exit
x extra functionality (experts only)
Command (m for help):p
Disk /dev/sdb: 8119 MB, 8119648256 bytes
255 heads, 63 sectors/track, 987 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sdb1 * 1 383 3076416 b W95 FAT32
/dev/sdb2 384 987 4851630 83 Linux
Command (m for help):
At this stage you can choose to delete a partition or both partitions, then create new ones of the desired type.
Distribution: Cinnamon Mint 17.3 and 18 at present.
As per Smoker...
What do you get when you print out the partition table? Smoker's example shows W95 FAT32 and Linux, what do you get? It looks like yours is corrupt (as below) You can re-write the partition ID to change/reset the partition type - option 't'.
Aug 23 17:29:37 benylap kernel: [ 3155.198823] sd 5:0:0:0: [sdb] 15794176 512-byte logical blocks: (8.08 GB/7.53 GiB)
Aug 23 17:29:37 benylap kernel: [ 3155.208791] sd 5:0:0:0: [sdb] Write Protect is off
Aug 23 17:29:37 benylap kernel: [ 3155.213789] sd 5:0:0:1: [sdc] Attached SCSI removable disk
Aug 23 17:29:37 benylap kernel: [ 3155.230767] sdb: unknown partition table
Aug 23 17:29:38 benylap kernel: [ 3156.105759] sd 5:0:0:0: [sdb] Attached SCSI removable disk
If you repartition the disk you've probably lost any data so try the ID first.
If you delete the partitions, yes. But you can still have a look first. You have no access to the data anyway do you ? It would be informative to know whether there are any partitions on the drive anyway. Trying to mount /dev/sdb won't work if it's partitioned into sdb1 and sdb2, so print the partition table and let's see what we're working with.
Actually, no. Deleting a partition only changes the partition table, not the actual data. So, if you delete a partition, then create a partition at the same starting point and with the same size, the new partition will have all the data the old one did. This is actually part of the recommended technique for resizing partitions.
Having said that, I agree with 10110111 that you should make a raw image of the drive before you start messing with it. If you accidentally create a partition that overlaps your data, then write anything to it, you will lose data.
See directory table section. And I gave the drive a volume label of "keytone" I found its starting address . And I see the directory file names also the bit for Volume label is set for "keytone" as it should. But before the volume label and stuff its all a bunch of zero's.
It starts at address 0x00F13E00. ... And I'm still trying to recover the data.
I'm going to try to format my USB FAT32 and at address 0x00F13E00 copy over a few megs into the USB from the backup image and maybe it'll work.