signmeuptoo
Folding and Crunching Not just Breakfast
Premium
join:2001-11-22
LOSTinSpace
clubs: 
 ·Future Nine Corpor..
 ·AT&T Southeast
| Windows Drives not seen or mounting, fix?
Ok, so it has been a while since I used Linux, due to HD space issues...
SuSE 11 is not seeing all my SATA Windows drives. Furthermore, using YaST's Partitioner, I can't seem to set mount points and successfully have the drives mount.
Devices (drives) are called /dev/sdb1 or what have you, but I can't get them to mount point with that. In fact, I get the message that "It is not allowed to assign a mount point to a device with non existance or unknown file system"
It refuses to see SDA, though during install at first it did.
On top of this, it can't even start up with my SATA drives in failsafe.
Is there something I am missing here, some way to fix this?
--
You know your life has gotten "DICEY" when it turns into an episode of LOST, like my ex wife, who I swear is one of "The Others". Cancer and other diseases kill fellow members here at DSLR! Easy: Join us in Teams Helix and Discovery to save the world! |
|
signmeuptoo
Folding and Crunching Not just Breakfast
Premium
join:2001-11-22
LOSTinSpace
clubs: | 50 views and no one to comment? Gee.
I wonder if it could be that some of my drives are set for SATAII... |
|
nwrickert
sand groper
Premium,MVM
join:2004-09-04
Geneva, IL
 ·AT&T U-Verse
·AT&T Midwest
| 50 views and no one to comment? Maybe we don't understand the problem.
I am not currently having any problems with NTFS or FAT32 drives. That's SuSE 10.1. I'll plan on installing SuSE 11 later this week. I guess I'll have to wait and see if I have problems mounting Windows drives.
--
AT&T dsl; Westell 327w modem/router; SuSE 10.1; firefox 2.0.0.14 |
|
signmeuptoo
Folding and Crunching Not just Breakfast
Premium
join:2001-11-22
LOSTinSpace
clubs:
·Future Nine Corpor..
·AT&T Southeast
| Well, the text while booting shows everything in order, but in the YaST Partitioner one of the drives (Vista 64 boot drive, not encrypted) doesn't show at all. The other drive won't set up to be seen/won't let me set a mount point. But I don't know what I am supposed to call the mount point, so could that be the issue?
My mainboard is a DFI LP nF4 SLI DR.
Thanks.
P.S.: I try hard to communicate well, but it isn't always easy describing an issue...
--
You know your life has gotten "DICEY" when it turns into an episode of LOST, like my ex wife, who I swear is one of "The Others". Cancer and other diseases kill fellow members here at DSLR! Easy: Join us in Teams Helix and Discovery to save the world! |
|
nwrickert
sand groper
Premium,MVM
join:2004-09-04
Geneva, IL
·AT&T U-Verse
·AT&T Midwest
| Can you post the output of
fdisk -l /dev/sda
except change the "sda" to the correct device name if your disk is not called "/dev/sda". I think "sda" should be correct for a single SATA drive.
I am particularly looking for the partition type code (the "Id" column). Normally that is 7 for NTFS. But perhaps Vista 64bit uses a different type code that could be confusing Yast.
--
AT&T dsl; Westell 327w modem/router; SuSE 10.1; firefox 2.0.0.14 |
|
signmeuptoo
Folding and Crunching Not just Breakfast
Premium
join:2001-11-22
LOSTinSpace
clubs: | Ok, I'll do that in the morning, the system is doing an important task in Vista right now. Thanks! |
|
signmeuptoo
Folding and Crunching Not just Breakfast
Premium
join:2001-11-22
LOSTinSpace
clubs:
·Future Nine Corpor..
·AT&T Southeast
| reply to signmeuptoo
For sda, my Windows bootup drive, it doesn't bring any response.
For sdb, it gives:
Disk /dev/sdb: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x483d3d82
Device Boot Start End Blocks Id System
/dev/sdb1 1 50993 409601241 7 HPFS/N
/dev/sdb2 50994 60801 78782760 7 HPFS/N
For sdc:
Disk /dev/sdc: 82.3 GB, 82348277760 bytes
255 heads, 63 sectors/track, 10011 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x70db21bf
Device Boot Start End Blocks Id System
/dev/sdc1 1 10011 80413326 7 HPFS/NTFS
For sdd:
Disk /dev/sdd: 250.0 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x38c6c165
Device Boot Start End Blocks Id System
/dev/sdd1 * 1 6005 48235131 83 Linux
/dev/sdd2 6006 16579 84935655 83 Linux
/dev/sdd3 16580 17102 4200997+ 82 Linuxswap / Solaris
So sda doesn't even give a response.
--
You know your life has gotten "DICEY" when it turns into an episode of LOST, like my ex wife, who I swear is one of "The Others". Cancer and other diseases kill fellow members here at DSLR! Easy: Join us in Teams Helix and Discovery to save the world! |
|
nwrickert
sand groper
Premium,MVM
join:2004-09-04
Geneva, IL
·AT&T U-Verse
·AT&T Midwest
| For sda, my Windows bootup drive, it doesn't bring any response. I guess that's why you cannot mount it.
Is it possible that Windows was installed on an encrypted drive (perhaps with Vista boot drive encryption)?
--
AT&T dsl; Westell 327w modem/router; SuSE 10.1; firefox 2.0.0.14 |
|
signmeuptoo
Folding and Crunching Not just Breakfast
Premium
join:2001-11-22
LOSTinSpace
clubs: | No, as I said, I did not encrypt it. |
|
nwrickert
sand groper
Premium,MVM
join:2004-09-04
Geneva, IL | What's the output from
ls -l /dev/sda
Maybe, for comparison, also provide the corresponding output for sdb. |
|
