Solved-Cannot Access Data Storage Drives

[jdm79]

Hi All, I am new to PCLinuxOS & don't know much about the system in general. i am a long time Debian user, but the methods that i use to fix or make changes to correct this particular problem in Debian, does not apply here. so i would like to ask for some help :-).

i have a PC that has two Solid State SATA drives on the first two SATA ports on the MB in a non-RAID configuration. the first Solid state drive (sda) has Mepis 11 on it's root partition (sda1) & partitions for swap (sda2) & Home (sda3).

PCLinuxOS resides on the second Solid State Drive (sdb) along with it's own swap & home partitions on that drive.

however, there are two other SATA disk drives (sdd) & (sdi) each with a single partition & their sole purpose is for storage of all my music & video files. these drives are formatted with ext4 filesystem as well.

the problem is that while logged in as user, i cannot see (throgh Kdiskfree) those two drives. in fact, i cannot find them listed anywhere, or find a way to mount them.

in most debian distributions, i could at least mount them logged in as user & i could change access permissions just by opening dolphin as su, going into the /mnt directory & change the user permissions if i wanted write access. however, i am at a loss on how to get this drive situation fixed in PCLinuxPS.
if someone could give me some advise, i would really appreciate it.

this is a correction: the /dev/sdd1/ & /dev/sdi1 are designations that my Debian install gave those drives.

 

[jdm79]

i have also looked in /etc/fstab & there is no listings for any of the two storage drives.

b.t.w, the OS is the latest FM version.

[muungwana]

Where you using KDE on your previous distro?

They should be shown in device notifier or so somewhere in dolphin file manager.

device notifier plasmoid is the default and the preferred way to mount/unmount partitions.

kdiskfree only shows mounted partitions.

[jdm79]

Where you using KDE on your previous distro?

Yes, that is the best DE & it is my favorite.

They should be shown in device notifier or so somewhere in dolphin file manager.

i clicked on the "show more icons">"Device Notifier" & the device notifier window shows "No Available Devices"
additionally, Dolphin does not show them on the side ether.

device notifier plasmoid is the default and the preferred way to mount/unmount partitions.
kdiskfree only shows mounted partitions.

thats quite opposite from the disks are mounted & accessed in Debian.
KDiskfree in Debian shows all partitions & disks mounted or unmounted & i can unmount or mount partitions directly with KDiskfree.
i plan on posting the output from fdisk -i, fstab, & more specific items later today.
the one thing that i find peculiar is that there is nothing in the /mnt & /media directories.


 

[muungwana]

device notifier plasmoid is the default and the preferred way to mount/unmount partitions.
kdiskfree only shows mounted partitions.

thats quite opposite from the disks are mounted & accessed in Debian.
KDiskfree in Debian shows all partitions & disks mounted or unmounted & i can unmount or mount partitions directly with KDiskfree.
  

I stand corrected <insert appropriate title>  

It shows all mounted partitions but it shows unmounted ones if they have an entry in "/etc/fstab".

Time to update my info on kdiskfree  

also post contents of the following commands:

blkid

cat /proc/partitions

[jdm79]

I stand corrected <insert appropriate title>  
It shows all mounted partitions but it shows unmounted ones if they have an entry in "/etc/fstab".
Time to update my info on kdiskfree  

 

also post contents of the following commands:

here you go
blkid
[root@localhost jon]# blkid
/dev/sdb1: LABEL="./" UUID="3b1c9e63-2256-4c5f-8410-1f474d2fcf8d" TYPE="ext4"
/dev/sda2: UUID="c1e3d272-bc6c-4b74-bc11-1affb4d4fd15" TYPE="swap"
/dev/sda3: UUID="2e33fe27-da75-4b60-ab7e-a338f599f95e" SEC_TYPE="ext2" TYPE="ext3"
/dev/sdb2: UUID="78047ac3-2ff0-4017-b65a-0b14ce758abe" TYPE="swap"
/dev/sdb3: LABEL="_/" UUID="2c43037a-11f6-46bd-9c6e-3360fcfe7bbc" TYPE="ext4"
/dev/sda1: UUID="798bdb20-c9c5-4738-8071-677395e0abb3" SEC_TYPE="ext2" TYPE="ext3"
/dev/sdc1: UUID="82048577-7899-4be9-81ae-89fd0fd1e89d" TYPE="ext4"

it appears that one of the storage drives is MIA.

cat /proc/partitions
[root@localhost jon]# cat /proc/partitions
major minor  #blocks  name

   8        0   62522712 sda
   8        1   11044656 sda1
   8        2    2939895 sda2
   8        3   48532365 sda3
   8       16   62522712 sdb
   8       17   21004956 sdb1
   8       18    1245037 sdb2
   8       19   40266922 sdb3
   8       32   72613056 sdc
   8       33   72605736 sdc1
   8       48    4193279 sdd
  11        0    1048575 sr0
[/quote]

[muungwana]

You did not include contents of "/etc/fstab"

The drive you are having problem with seem to be "/dev/sdd"

"/dev/sdd" does not appear to be partitioned.
Reason why blkid did not show "/dev/sdd" could be because it expects a partitioned drive and "/dev/sdd" is not partitioned.

Its is not advised to use unpartitioned drives they are not expected and some tools may fail to work with them.

Where you able to use it in debian?

"/dev/sdi" is not being seen by the kernel, this suggests a hardware related problem.

The output of the following command could hold some clues.

dmesg | grep -i sd

[jdm79]

You did not include contents of "/etc/fstab"

here it is.
 # Entry for /dev/sdb1 :
UUID=3b1c9e63-2256-4c5f-8410-1f474d2fcf8d / ext4 defaults 1 1
# Entry for /dev/sdb3 :
UUID=2c43037a-11f6-46bd-9c6e-3360fcfe7bbc /home ext4 defaults 1 2
none /proc proc defaults 0 0
# Entry for /dev/sda2 :
UUID=e9f66a09-e107-46ed-b5a1-9298cb4bd6dd swap swap defaults 0 0
# Entry for /dev/sdb2 :
UUID=78047ac3-2ff0-4017-b65a-0b14ce758abe swap swap defaults 0 0
none /dev/pts devpts defaults 0 0

The drive you are having problem with seem to be "/dev/sdd"
"/dev/sdd" does not appear to be partitioned.
Reason why blkid did not show "/dev/sdd" could be because it expects a partitioned drive and "/dev/sdd" is not partitioned.
Its is not advised to use unpartitioned drives they are not expected and some tools may fail to work with them.

yes, /dev/sdd IS partioned with one single ext4 partition as stated in my original post. if you notice, it has a size of 74.3 GB

Where you able to use it in debian?

yes, in fact, i created folders & placed files in them.

"/dev/sdi" is not being seen by the kernel, this suggests a hardware related problem.

The output of the following command could hold some clues.

dmesg | grep -i sd

here you go. this is after the removal of the ramdisk
dmesg | grep -i sd

[root@localhost jon]# dmesg | grep -i sd
ACPI: RSDP 000f7890 00024 (v02 Nvidia)
ACPI: XSDT bfee3100 00044 (v01 Nvidia ASUSACPI 42302E31 AWRD 00000000)
ACPI: DSDT bfee3280 0798A (v01 NVIDIA AWRDACPI 00001000 MSFT 03000000)
ACPI: EC: Look up EC in DSDT
sd 0:0:0:0: [sda] 125045424 512-byte logical blocks: (64.0 GB/59.6 GiB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
 sda: sda1 sda2 sda3
sd 0:0:0:0: [sda] Attached SCSI disk
sd 1:0:0:0: [sdb] 125045424 512-byte logical blocks: (64.0 GB/59.6 GiB)
sd 1:0:0:0: [sdb] Write Protect is off
sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00
sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sd 2:0:0:0: [sdc] 145226112 512-byte logical blocks: (74.3 GB/69.2 GiB)
sd 2:0:0:0: [sdc] Write Protect is off
sd 2:0:0:0: [sdc] Mode Sense: 00 3a 00 00
sd 2:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
 sdb: sdb1 sdb2 sdb3
sd 1:0:0:0: [sdb] Attached SCSI disk
 sdc: sdc1
sd 2:0:0:0: [sdc] Attached SCSI disk
sd 3:0:0:0: [sdd] 145226112 512-byte logical blocks: (74.3 GB/69.2 GiB)
sd 3:0:0:0: [sdd] Write Protect is off
sd 3:0:0:0: [sdd] Mode Sense: 00 3a 00 00
sd 3:0:0:0: [sdd] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
 sdd: sdd1
sd 3:0:0:0: [sdd] Attached SCSI disk
  dhfis 0x1 dmafis 0x1 sdbfis 0x0
ata4: tag : dhfis dmafis sdbfis sactive
  dhfis 0x1 dmafis 0x1 sdbfis 0x0
ata4: tag : dhfis dmafis sdbfis sactive
  dhfis 0x1 dmafis 0x1 sdbfis 0x0
ata4: tag : dhfis dmafis sdbfis sactive
  dhfis 0x1 dmafis 0x1 sdbfis 0x0
ata4: tag : dhfis dmafis sdbfis sactive
  dhfis 0x1 dmafis 0x1 sdbfis 0x0
ata4: tag : dhfis dmafis sdbfis sactive
  dhfis 0x1 dmafis 0x1 sdbfis 0x0
ata4: tag : dhfis dmafis sdbfis sactive
sd 3:0:0:0: [sdd] Unhandled sense code
sd 3:0:0:0: [sdd]  Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
sd 3:0:0:0: [sdd]  Sense Key : Medium Error [current] [descriptor]
sd 3:0:0:0: [sdd]  Add. Sense: Unrecovered read error - auto reallocate failed
sd 3:0:0:0: [sdd] CDB: Read(10): 28 00 00 00 04 2f 00 00 08 00
end_request: I/O error, dev sdd, sector 1071
Buffer I/O error on device sdd1, logical block 126
  dhfis 0x1 dmafis 0x1 sdbfis 0x0
ata4: tag : dhfis dmafis sdbfis sactive
  dhfis 0x1 dmafis 0x1 sdbfis 0x0
ata4: tag : dhfis dmafis sdbfis sactive
  dhfis 0x1 dmafis 0x1 sdbfis 0x0
ata4: tag : dhfis dmafis sdbfis sactive
  dhfis 0x1 dmafis 0x1 sdbfis 0x0
ata4: tag : dhfis dmafis sdbfis sactive
  dhfis 0x1 dmafis 0x1 sdbfis 0x0
ata4: tag : dhfis dmafis sdbfis sactive
  dhfis 0x1 dmafis 0x1 sdbfis 0x0
ata4: tag : dhfis dmafis sdbfis sactive
sd 3:0:0:0: [sdd] Unhandled sense code
sd 3:0:0:0: [sdd]  Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
sd 3:0:0:0: [sdd]  Sense Key : Medium Error [current] [descriptor]
sd 3:0:0:0: [sdd]  Add. Sense: Unrecovered read error - auto reallocate failed
sd 3:0:0:0: [sdd] CDB: Read(10): 28 00 00 00 04 2f 00 00 08 00
end_request: I/O error, dev sdd, sector 1071
Buffer I/O error on device sdd1, logical block 126
EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts:
sd 0:0:0:0: Attached scsi generic sg0 type 0
sd 1:0:0:0: Attached scsi generic sg1 type 0
sd 2:0:0:0: Attached scsi generic sg2 type 0
sd 3:0:0:0: Attached scsi generic sg3 type 0
sd 8:0:0:0: Attached scsi generic sg5 type 0
sd 8:0:0:1: Attached scsi generic sg6 type 0
sd 8:0:0:2: Attached scsi generic sg7 type 0
sd 8:0:0:3: Attached scsi generic sg8 type 0
sd 8:0:0:4: Attached scsi generic sg9 type 0
sd 8:0:0:1: [sdf] Attached SCSI removable disk
sd 8:0:0:0: [sde] Attached SCSI removable disk
sd 8:0:0:2: [sdg] Attached SCSI removable disk
sd 8:0:0:3: [sdh] Attached SCSI removable disk
sd 8:0:0:4: [sdi] Attached SCSI removable disk
  dhfis 0x1 dmafis 0x1 sdbfis 0x0
ata4: tag : dhfis dmafis sdbfis sactive
  dhfis 0x1 dmafis 0x1 sdbfis 0x0
ata4: tag : dhfis dmafis sdbfis sactive
  dhfis 0x1 dmafis 0x1 sdbfis 0x0
ata4: tag : dhfis dmafis sdbfis sactive
  dhfis 0x1 dmafis 0x1 sdbfis 0x0
ata4: tag : dhfis dmafis sdbfis sactive
  dhfis 0x1 dmafis 0x1 sdbfis 0x0
ata4: tag : dhfis dmafis sdbfis sactive
  dhfis 0x1 dmafis 0x1 sdbfis 0x0
ata4: tag : dhfis dmafis sdbfis sactive
sd 3:0:0:0: [sdd] Unhandled sense code
sd 3:0:0:0: [sdd]  Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
sd 3:0:0:0: [sdd]  Sense Key : Medium Error [current] [descriptor]
sd 3:0:0:0: [sdd]  Add. Sense: Unrecovered read error - auto reallocate failed
sd 3:0:0:0: [sdd] CDB: Read(10): 28 00 00 00 04 2f 00 00 08 00
end_request: I/O error, dev sdd, sector 1071
Buffer I/O error on device sdd1, logical block 126
  dhfis 0x1 dmafis 0x1 sdbfis 0x0
ata4: tag : dhfis dmafis sdbfis sactive
  dhfis 0x1 dmafis 0x1 sdbfis 0x0
ata4: tag : dhfis dmafis sdbfis sactive
  dhfis 0x1 dmafis 0x1 sdbfis 0x0
ata4: tag : dhfis dmafis sdbfis sactive
  dhfis 0x1 dmafis 0x1 sdbfis 0x0
ata4: tag : dhfis dmafis sdbfis sactive
  dhfis 0x1 dmafis 0x1 sdbfis 0x0
ata4: tag : dhfis dmafis sdbfis sactive
  dhfis 0x1 dmafis 0x1 sdbfis 0x0
ata4: tag : dhfis dmafis sdbfis sactive
sd 3:0:0:0: [sdd] Unhandled sense code
sd 3:0:0:0: [sdd]  Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
sd 3:0:0:0: [sdd]  Sense Key : Medium Error [current] [descriptor]
sd 3:0:0:0: [sdd]  Add. Sense: Unrecovered read error - auto reallocate failed
sd 3:0:0:0: [sdd] CDB: Read(10): 28 00 00 00 04 2f 00 00 08 00
end_request: I/O error, dev sdd, sector 1071
Buffer I/O error on device sdd1, logical block 126
EXT4-fs (sdb1): re-mounted. Opts: (null)
EXT4-fs (sdb3): mounted filesystem with ordered data mode. Opts: (null)
Adding 1245032k swap on /dev/sdb2.  Priority:-1 extents:1 across:1245032k SS
Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
svc: failed to register nfsdv2 RPC service (errno 111).
nfsd: last server has exited, flushing export cache
svc: failed to register nfsdv2 RPC service (errno 97).
nfsd: last server has exited, flushing export cache
sd 9:0:0:0: Attached scsi generic sg10 type 0
sd 9:0:0:0: [sdj] 1992334 512-byte logical blocks: (1.02 GB/972 MiB)
sd 9:0:0:0: [sdj] Write Protect is off
sd 9:0:0:0: [sdj] Mode Sense: 03 00 00 00
sd 9:0:0:0: [sdj] No Caching mode page present
sd 9:0:0:0: [sdj] Assuming drive cache: write through
sd 9:0:0:0: [sdj] No Caching mode page present
sd 9:0:0:0: [sdj] Assuming drive cache: write through
 sdj: sdj1
sd 9:0:0:0: [sdj] No Caching mode page present
sd 9:0:0:0: [sdj] Assuming drive cache: write through
sd 9:0:0:0: [sdj] Attached SCSI removable disk
[root@localhost jon]# # Entry for /dev/sdb1 :
[root@localhost jon]# UUID=3b1c9e63-2256-4c5f-8410-1f474d2fcf8d / ext4 defaults 1 1bash: /: is a directory
[root@localhost jon]# # Entry for /dev/sdb3 :
[root@localhost jon]# UUID=2c43037a-11f6-46bd-9c6e-3360fcfe7bbc /home ext4 defaults 1 2
bash: /home: is a directory
[root@localhost jon]# none /proc proc defaults 0 0
bash: none: command not found
[root@localhost jon]# # Entry for /dev/sda2 :
[root@localhost jon]# UUID=e9f66a09-e107-46ed-b5a1-9298cb4bd6dd swap swap defaults 0 0
bash: swap: command not found
[root@localhost jon]# # Entry for /dev/sdb2 :
[root@localhost jon]# UUID=78047ac3-2ff0-4017-b65a-0b14ce758abe swap swap defaults 0 0
bash: swap: command not found
[root@localhost jon]# none /dev/pts devpts defaults 0 0# Entry for /dev/sdb1 :
bash: none: command not found
[root@localhost jon]# UUID=3b1c9e63-2256-4c5f-8410-1f474d2fcf8d / ext4 defaults 1 1bash: /: is a directory
[root@localhost jon]# # Entry for /dev/sdb3 :
[root@localhost jon]# UUID=2c43037a-11f6-46bd-9c6e-3360fcfe7bbc /home ext4 defaults 1 2
bash: /home: is a directory
[root@localhost jon]# none /proc proc defaults 0 0
bash: none: command not found
[root@localhost jon]# # Entry for /dev/sda2 :
[root@localhost jon]# UUID=e9f66a09-e107-46ed-b5a1-9298cb4bd6dd swap swap defaults 0 0
bash: swap: command not found
[root@localhost jon]# # Entry for /dev/sdb2 :
[root@localhost jon]# UUID=78047ac3-2ff0-4017-b65a-0b14ce758abe swap swap defaults 0 0
bash: swap: command not found
[root@localhost jon]# none /dev/pts devpts defaults 0 0# Entry for /dev/sdb1 :
bash: none: command not found
[root@localhost jon]# UUID=3b1c9e63-2256-4c5f-8410-1f474d2fcf8d / ext4 defaults 1 1bash: /: is a directory
[root@localhost jon]# # Entry for /dev/sdb3 :
[root@localhost jon]# UUID=2c43037a-11f6-46bd-9c6e-3360fcfe7bbc /home ext4 defaults 1 2
bash: /home: is a directory
[root@localhost jon]# none /proc proc defaults 0 0
bash: none: command not found
[root@localhost jon]# # Entry for /dev/sda2 :
[root@localhost jon]# UUID=e9f66a09-e107-46ed-b5a1-9298cb4bd6dd swap swap defaults 0 0
bash: swap: command not found
[root@localhost jon]# # Entry for /dev/sdb2 :
[root@localhost jon]# UUID=78047ac3-2ff0-4017-b65a-0b14ce758abe swap swap defaults 0 0
bash: swap: command not found
[root@localhost jon]# none /dev/pts devpts defaults 0 0# Entry for /dev/sdb1 :
bash: none: command not found
[root@localhost jon]# UUID=3b1c9e63-2256-4c5f-8410-1f474d2fcf8d / ext4 defaults 1 1bash: /: is a directory
[root@localhost jon]# # Entry for /dev/sdb3 :
[root@localhost jon]# UUID=2c43037a-11f6-46bd-9c6e-3360fcfe7bbc /home ext4 defaults 1 2
bash: /home: is a directory
[root@localhost jon]# none /proc proc defaults 0 0
bash: none: command not found
[root@localhost jon]# # Entry for /dev/sda2 :
[root@localhost jon]# UUID=e9f66a09-e107-46ed-b5a1-9298cb4bd6dd swap swap defaults 0 0
bash: swap: command not found
[root@localhost jon]# # Entry for /dev/sdb2 :
[root@localhost jon]# UUID=78047ac3-2ff0-4017-b65a-0b14ce758abe swap swap defaults 0 0
bash: swap: command not found
[root@localhost jon]# none /dev/pts devpts defaults 0 0

[muungwana]

I am confused,

you first started by saying "/dev/sdd" was one of the drives that were not seen.

Then you said it was actually "Gigabyte PCI ramdisk". You have, so far, refereed "/dev/sdd" as both "SATA disk drive" and as "Gigabyte PCI ramdisk" and one of them was removed btw posts.

There is "/dev/sdj" in your "dmesg" output,but not in your "/proc/partitions" output.

So this one was attached after your initial posts.

sd 3:0:0:0: [sdd] Unhandled sense code
sd 3:0:0:0: [sdd]  Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
sd 3:0:0:0: [sdd]  Sense Key : Medium Error [current] [descriptor]
sd 3:0:0:0: [sdd]  Add. Sense: Unrecovered read error - auto reallocate failed
sd 3:0:0:0: [sdd] CDB: Read(10): 28 00 00 00 04 2f 00 00 08 00
end_request: I/O error, dev sdd, sector 1071

That section of "dmesg" says "/dev/sdd" has a hardware problem. Which of "/dev/sdd" it is,i cant tell.

It is hard to keep straight your problem if you are not consistent with your explanations and your ouputs

[jdm79]

I am confused,

you first started by saying "/dev/sdd" was one of the drives that were not seen.

ok, sorry for the confusion. the reason that i stated that the drives were allocated sdd & sdi because that is what my Debian installation shows both those drives were. i did not find out what they were designated as in the FM installation until i run the  dmesg | grep -i sd command as you suggested. even after removing the ramdisk. i booted into Debian & the Drive assignments did not change. they still are referred to sdd1 & sdi1. however FullMonty apparently refers them to sdc & sdd. i guess that is part of where the confusion come from

 

Then you said it was actually "Gigabyte PCI ramdisk". You have, so far, refereed "/dev/sdd" as both "SATA disk drive" and as "Gigabyte PCI ramdisk" and one of them was removed btw posts.

There is "/dev/sdj" in your "dmesg" output,but not in your "/proc/partitions" output.

So this one was attached after your initial posts.

that is where i have inserted a flash drive so i can copy the outputs of the requested files to a txt file to use to make this post with. i am not posting from the PC in this discussion, i am using my main PC. the /dev/sdj is my flash drive.

sd 3:0:0:0: [sdd] Unhandled sense code
sd 3:0:0:0: [sdd]  Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
sd 3:0:0:0: [sdd]  Sense Key : Medium Error [current] [descriptor]
sd 3:0:0:0: [sdd]  Add. Sense: Unrecovered read error - auto reallocate failed
sd 3:0:0:0: [sdd] CDB: Read(10): 28 00 00 00 04 2f 00 00 08 00
end_request: I/O error, dev sdd, sector 1071

well, apparently, the 2nd storage drive may be going bad & FM must have a utility that is detecting it as where Debian is not.

That section of "dmesg" says "/dev/sdd" has a hardware problem. Which of "/dev/sdd" it is,i cant tell.

apparently, it's /dev/sdd that has a problem according to FM, /dev/sdd is the 2nd storage drive in FM and it is designated in Debian as /dev/sdi1. the first storage drive in FM identifies itself as /dev/sdc according to fdisk. the first drive in Debian identifies itself as /dev/sdc1  
both drives in the debian installation mount & behave normally, but like i said earlier, i cannot find a way to access them in FM.

It is hard to keep straight your problem if you are not consistent with your explanations and your ouputs

look, i was assuming that FM gave them the same drive designations as Debian did. it did not occur to me that they were different drive assignments until i run blkid and dmesg.

it still leaves me to ask, plain and simple, why do both drives work in my debian installation, but i can't seem to find a way for them to work in FM.

[muungwana]

What is "FM"?

You keep saying that and i can not expand it to anything related, does it mean "file manager"? if yes, then its best to specify exactly which one you are using.

back to your problem.

So, "/dev/sdc1" is working correctly. It doesnt show up in kdiskfree because it does not have an entry in "/etc/fstab".

Adding an entry there should fix the problem of it not showing up there.

about "/dev/sdd".

It could be because the drive has some functionality that is correctly detected by recent kernels, what kernel version does your debian system use?

try installing the latest kernel and see if it solved the problem.

If it worked on debian,it should work here too, maybe a kernel setting or two need to be changed.

[jdm79]

What is "FM"?

FM = PCLinuxOS Full Monty
i should have stated that, but i figured that you would have figured that out allready

back to your problem.

So, "/dev/sdc1" is working correctly.

when booted into Debian, they both work correctly, however, in Full Monty, neither of them are seen in fstab, /mnt & /media directories
 

It doesnt show up in kdiskfree because it does not have an entry in "/etc/fstab".
Adding an entry there should fix the problem of it not showing up there.

i will try that tommorow, however why were the entries not made in fstab during installation or startup?

about "/dev/sdd".

It could be because the drive has some functionality that is correctly detected by recent kernels, what kernel version does your debian system use?

2-6-36-4 i am pretty sure that it is older then the one on Full Monty

try installing the latest kernel and see if it solved the problem.
If it worked on debian,it should work here too, maybe a kernel setting or two need to be changed.

i was really hoping not to do that unless there is a updated kernel available through synaptic & in the repositories. i am working on this computer for a friend & already have quite a bit of time invested in it. please don't get me wrong, i really like PCLinuxOS Full Monty & i am really impressed with the KDE setup, however, this is starting to get aggravating to me because the underlying system & my unfamiliarty with it & the problem with setting up these disk drives. i never had this problem in any of the many debian installs that i have done.

[muungwana]

Are these two sata disks internal disks?

If they are and they were present when you installed the system, then they should have been included in "/etc/fstab". They were not so you have to do so manually.

You can simply take their entries from your debian system and add them to your pclinuxos system. You will also have to create mount points at where they are to be mounted too.

I googled a bit about the error you were getting and somebody managed to solve the problem by changing a setting somewhere so it should be possible to make it work in pclinuxos simply by changing a setting. I am a bit pressed for time so will look that info up later.

[menotu]

Just a thought - could maybe have a look in

Config Your Desktop >(aka System Settings) Hardware > Removable Devices -

The "Column Header" options are Automount on Login and Automount on Attach

Configure automatic mounting of removable storage media - with the following options

Enable automatic mounting of removable media
Only automatically mount removable media that has been manually mounted before
Mount all removable media at login
Automatically mount removable media when attached

although it's named Removable Devices it can also shows HDD / Partitions

[Just17]

# Entry for /dev/sdb1 :
UUID=3b1c9e63-2256-4c5f-8410-1f474d2fcf8d / ext4 defaults 1 1
# Entry for /dev/sdb3 :
UUID=2c43037a-11f6-46bd-9c6e-3360fcfe7bbc /home ext4 defaults 1 2
none /proc proc defaults 0 0
# Entry for /dev/sda2 :
UUID=e9f66a09-e107-46ed-b5a1-9298cb4bd6dd swap swap defaults 0 0
# Entry for /dev/sdb2 :
UUID=78047ac3-2ff0-4017-b65a-0b14ce758abe swap swap defaults 0 0
none /dev/pts devpts defaults 0 0

I would initially comment out or delete the /dev/sda2  Swap partition entry in fstab.
If only to keep things separate.

Please provide the output from

fdisk -l    (lower case L)

I notice that you have not used 'discard' in the mount entries, which I thought was necessary for proper management of SSDs .....  not related to the present problem ....

I would suggest powering down and checking the connections to the drives .......  unplug the connectors and replace them, before powering up again.

Then issue the fdisk -l  command and post back the output.



BTW .....  for long lists you wish to post please put them in Code quotes .....  it causes the list to be scrollable and keeps things tidy