mounting problems

English Install/Boot/Login
#1

I installed opensuse 11 64 bit (multi boot with ubuntu hardy) earlier today, but i ran into a problem getting all of my partitions mounted.
I have quite a few partitions i want to mount, and all but one mount with no problems. I cant seem to get the last (ntfs) partition to mount properly. Also, fdisk -l gives me some strange output for this disk (strange to me anyway). Everything mounts just fine under ubuntu, so the partition should be ok.

fdisk -l

Disk /dev/sda: 122.9 GB, 122942324736 bytes
255 heads, 63 sectors/track, 14946 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0xaf579307

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *           1        2611    20972826   83  Linux
/dev/sda2            2612        2873     2104515   82  Linux swap / Solaris

Disk /dev/sdb: 120.0 GB, 120034123776 bytes
255 heads, 63 sectors/track, 14593 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x625ed5e9

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1   *           1       14593   117218241    7  HPFS/NTFS

Disk /dev/sdc: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x75f48e6f

   Device Boot      Start         End      Blocks   Id  System
/dev/sdc1   *           1         852     6835720+  83  Linux
Partition 1 does not end on cylinder boundary.
/dev/sdc2             852        1216     2929752   82  Linux swap / Solaris
Partition 2 does not end on cylinder boundary.
/dev/sdc3            1217       58916   463475250   83  Linux
/dev/sdc4           58917       60801    15141262+  83  Linux

Disk /dev/sdd: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00018ef7

   Device Boot      Start         End      Blocks   Id  System
/dev/sdd1               1      121601   976760001   83  Linux

Disk /dev/sde: 1000.2 GB, 1000204886016 bytes
16 heads, 63 sectors/track, 1938021 cylinders
Units = cylinders of 1008 * 512 = 516096 bytes
Disk identifier: 0x5893c07c

   Device Boot      Start         End      Blocks   Id  System
/dev/sde1               1     1938018   976761040+   7  HPFS/NTFS

Disk /dev/sdf: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0xa0bcf878

   Device Boot      Start         End      Blocks   Id  System
/dev/sdf1   *           1      121601   976760001    7  HPFS/NTFS

Disk /dev/sdg: 251.0 GB, 251000193024 bytes
255 heads, 63 sectors/track, 30515 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0xe31ed6c6

   Device Boot      Start         End      Blocks   Id  System
/dev/sdg1               1       30515   245111706    7  HPFS/NTFS

Disk /dev/dm-0: 1000.2 GB, 1000204098560 bytes
255 heads, 63 sectors/track, 121601 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0xa0bcf878

     Device Boot      Start         End      Blocks   Id  System
/dev/dm-0p1   *           1      121601   976760001    7  HPFS/NTFS

Disk /dev/dm-1: 1000.2 GB, 1000202241024 bytes
255 heads, 63 sectors/track, 121600 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x69205244

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

     Device Boot      Start         End      Blocks   Id  System
/dev/dm-1p1   ?       13578      119522   850995205   72  Unknown
Partition 1 does not end on cylinder boundary.
/dev/dm-1p2   ?       45382       79243   271987362   74  Unknown
Partition 2 does not end on cylinder boundary.
/dev/dm-1p3   ?       10499       10499           0   65  Novell Netware 386
Partition 3 does not end on cylinder boundary.
/dev/dm-1p4          167628      167631       25817+   0  Empty
Partition 4 does not end on cylinder boundary.

Partition table entries are not in disk order

I dont understand why the last disk is named /dev/dm-1p when all the others are named /dev/sda/b/c etc.

the fdisk output makes it look like theres a bunch of partitions on /dev/dm-0p while its a single ntfs partition.

Heres my fstab:


linux:~ # cat /etc/fstab

/dev/sdb1 /windows/d ntfs-3g defaults 0 0
/dev/sdc2 swap swap defaults 0 0
/dev/sdc3 /windows/e ext3 defaults 0 0
/dev/sdc4 / ext3 defaults 1 1
/dev/sdd1 /windows/f ext3 defaults 0 0
/dev/sde1 /windows/g ntfs-3g defaults 0 0
/dev/sdg1 /windows/h ntfs-3g defaults 0 0
/dev/dm-0p1 /windows/i ntfs-3g defaults 0 0

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

/dev/sdc is a RAID0 array, the rest dont use any form of raid.

/dev/sda and /dev/sdb are on an IDE controller, and /dev/sdc is connected to a 2 port RAID controller. The rest are conected to the same SATA controller, configured as AHCI.

Another thing, not sure if it has anything to do with this. When i tried to let the suse installation configure GRUB it failed, and wouldnt boot(error 22 if memory serves me right). lilo also wouldnt work. I had to manually install/configure GRUB to get anything to boot. (twice, once when installing ubuntu, and again when installing opensuse)

I’m relatively new to linux so i wouldnt rule out some stupid mistake somewhere :X

I hope you guys are able to help me with this.

#2

Have a gander at swerdna’s help
HowTo Mount NTFS Filesystem Partition Read Write Access in openSUSE 10, 11

#3

I read the article you linked to, pretty much mounting 101. I dont see anything that could explain my problem though.

#4

Am I missing something? You have /dev/sdd1, /dev/sde1 and /dev/sdg1 in your fstab, but they are not listed by fdisk -l.

The /dev/dm-0p1 looks strange to me also. Is there a /dev/dm-0p1?

#5

Hi
Did the disk in question have solaris x86 or ubuntu sparc installed on
it, that is something I have seen on drives created via ubuntu and/or
sun labeling.

–
Cheers Malcolm °¿° (Linux Counter #276890)
openSUSE 11.0 x86 Kernel 2.6.25.16-0.1-default
up 1 day 7:16, 1 user, load average: 0.08, 0.09, 0.20
GPU GeForce 6600 TE/6200 TE - Driver Version: 173.14.12

#6

Actually, they are listed in fdisk -l.
I’m not sure what your asking with “Is there a /dev/dm-0p1?”

The disk was partitioned + formatted under windows XP pro SP3, not ubuntu. Also, it has never been used for any OS, only data storage.

#7

Hi
If you look at the /dev/sdf = dev/dm-0isk as they have both the same
identifier.

Hmmm was it a new, second-hand or openbox purchase?

Can you reformat this drive? If so I would use fdisk to manually mount
and step through to delete them all, then reformat.

–
Cheers Malcolm °¿° (Linux Counter #276890)
openSUSE 11.0 x86 Kernel 2.6.25.16-0.1-default
up 1 day 11:43, 2 users, load average: 0.02, 0.06, 0.03
GPU GeForce 6600 TE/6200 TE - Driver Version: 173.14.12

#8

I’m not sure what the disk identifier is, i’m guessing some kind of ‘unique’ ID for the disk? I see that they are indeed the same. If my assumption on the meaning of disk id is correct, this is very strange.

All of the hardware in this system is new(or was when i bought it).

I’ll see if i can find enough disk space to move all of the files from this disk to another so i can format it, although i doubt i’ll have enough.

#9

Sorry, I missed the scrollbar and thus half of the output. It still seems to me that /dev/dm-1p is a strange beast. fdisk has a lot of comment about it.

With “Is there a /dev/dm-0p1?” I mean just that: is there a block special file named dm-0p1 in directory /dev. But I suppose there is.

I appoligize again and will quit from this thread because I do not seem to be equiped for it :wink:

#10

I solved the problem.

First i deleted the partition on the disk, from ubuntu, after moving all of the data on it. When i tried to create a new partition using the suse partition manager, it didnt work. There was no unallocated space.
When i opened the partition manager, i noticed there was an entry that looked something like “Sil_biosraid” plus a bunch of random letters/numbers, being 1TB.
That led me to assume its got something to do with the 2 port Silicon image RAID controller i use, but the disk in question is not connected to it. I have a 500GB RAID1 array on there.
I deleted the “sil_biosraidrandomlettersnumbers” entry, which freed up the disk. After re-partitioning/formatting it with ext3, the problem was solved.

I’m still stumped as to how this happened, since the disk was partitioned on another computer, which doesnt have a silicon controller.
Thanks for the help guys.