Linux Tutorial?

[blaa]

So assuming I try many different disks, I'm still presented with two possible causes;

1) The Drive is not installed correctly (best one)
2) The formating can not be recognised

So if I were to put in a disk, format it to Unbuntu's prefered filesystem, say ext3. And I can read/write to the disk, it leaves me with the second cause a filesystem i can not access from unbuntu.

Is this a correct assumption?

 

[Jonti]

So assuming I try many different disks, I'm still presented with two possible causes;

1) The Drive is not installed correctly (best one)
2) The formating can not be recognised

So if I were to put in a disk, format it to Unbuntu's prefered filesystem, say ext3. And I can read/write to the disk, it leaves me with the second cause a filesystem i can not access from unbuntu.

Is this a correct assumption?

Sounds good to me, yes. Have you got some blank mo disks to play with?

PS
It's Ubuntu (not Unbuntu)

 

[blaa]

Sounds good to me, yes. Have you got some blank mo disks to play with?

PS
It's Ubuntu (not Unbuntu)

pmsl... ah that pretty much sums up these last few days of learning, pretty much most of my mistakes were putting an 'n' in the wrong place.

*dies from irony*

Yeah, I have a few MO disks to try, - I was wondering though, if I format them in ubuntu in ext3, or in windows as FAT32?
This might seem like a really thick question, but its as I want to eliminate that perhaps ubuntu would be causing a hardware problem...?

 

[Jonti]

How about both?

Using a blank mo disk, just set the partition's system id using fdisk and then use mke2fs to put a file system on it. Follow that up with a mount and then a touch ...

Then umount it and repeat (mutatis mutandis) to make a dos file system.

 

[lobster]

No unfortunately its large files of recorded data, EEG and ECG data, I'm not sure exactly what the files would be, as this is in fact data recorded back in the early 90s, previous to me, and about 3 newer systems installed..

Data recovery is seriously expensive though

And also, this is only on one diskette, I am going to try others with the hexdump command, I don't believe that all the disks can be corrupted...

if i am not mistaken is EEG for electroencephalogram and ECG for electrocardiogram?

 

[blaa]

if i am not mistaken is EEG for electroencephalogram and ECG for electrocardiogram?

Sure is, these disks contain medical data. This is my desperate need to get to them, archiving for 15 years yadda yadda...

 

[blaa]

ok, this is an MO disk formatted in win xp (couldn't figure out the linux way), to a FAT32.

is this the correct information for said setup? (hopes its still wrong and there is just a simple driver issue in linux or sommat)

sleep@standalone:~$ sudo fdisk -l
Password:

Disk /dev/hdc: 20.4 GB, 20411080704 bytes
16 heads, 63 sectors/track, 39549 cylinders
Units = cylinders of 1008 * 512 = 516096 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/hdc1   *           1       12118     6107440+   7  HPFS/NTFS
/dev/hdc2           12119       39541    13821129+   f  W95 Ext'd (LBA)
Partition 2 does not end on cylinder boundary.
/dev/hdc5           12119       18350     3140896+   b  W95 FAT32
/dev/hdc6           18361       19285      465853+  82  Linux swap / Solaris
/dev/hdc7           21612       28401     3421813+  83  Linux
/dev/hdc8           28401       39541     5614686   83  Linux
/dev/hdc9           19285       21612     1172713+  83  Linux

Partition table entries are not in disk order

Disk /dev/sda: 1149 MB, 1149418496 bytes
255 heads, 63 sectors/track, 139 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

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

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   ?       48437      119493   570754815+  72  Unknown
Partition 1 has different physical/logical beginnings (non-Linux?):
     phys=(357, 116, 40) logical=(48436, 183, 40)
Partition 1 has different physical/logical endings:
     phys=(357, 32, 45) logical=(119492, 104, 7)
Partition 1 does not end on cylinder boundary.
/dev/sda2   ?       10501      131013   968014120   65  Novell Netware 386
Partition 2 has different physical/logical beginnings (non-Linux?):
     phys=(288, 115, 43) logical=(10500, 111, 30)
Partition 2 has different physical/logical endings:
     phys=(367, 114, 50) logical=(131012, 158, 28)
Partition 2 does not end on cylinder boundary.
/dev/sda3   ?      116395      236907   968014096   79  Unknown
Partition 3 has different physical/logical beginnings (non-Linux?):
     phys=(366, 32, 33) logical=(116394, 188, 12)
Partition 3 has different physical/logical endings:
     phys=(357, 32, 43) logical=(236906, 234, 25)
Partition 3 does not end on cylinder boundary.
/dev/sda4   ?      179626      179629       27749+   d  Unknown
Partition 4 has different physical/logical beginnings (non-Linux?):
     phys=(372, 97, 50) logical=(179625, 87, 47)
Partition 4 has different physical/logical endings:
     phys=(0, 10, 0) logical=(179628, 203, 42)
Partition 4 does not end on cylinder boundary.

Partition table entries are not in disk order
sleep@standalone:~$ sudo hexdump -C /dev/sda|head
00000000  eb 58 90 4d 53 44 4f 53  35 2e 30 00 02 08 26 00  |.X.MSDOS5.0...&.|
00000010  02 00 00 00 00 f8 00 00  3f 00 ff 00 00 00 00 00  |........?.......|
00000020  5e 41 22 00 8d 08 00 00  00 00 00 00 02 00 00 00  |^A".............|
00000030  01 00 06 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
00000040  00 00 29 eb 7e 05 18 4e  4f 20 4e 41 4d 45 20 20  |..).~..NO NAME  |
00000050  20 20 46 41 54 33 32 20  20 20 33 c9 8e d1 bc f4  |  FAT32   3.....|
00000060  7b 8e c1 8e d9 bd 00 7c  88 4e 02 8a 56 40 b4 08  |{......|.N..V@..|
00000070

 

[blaa]

And then if this proves undoubtedly that I can not use ubuntu to open these disks, how would I go about finding out which new version of Unixware could open these disks?