Results 1 to 8 of 8
Hi all,
I just installed fedora 10 and the main issue until now is that when I'm trying to access my second internal harddisk -(I use KDE4)from dolphin lets say- ...
- 01-28-2009 #1Just Joined!
- Join Date
- Nov 2006
- Posts
- 39
question marks on ls
Hi all,
I just installed fedora 10 and the main issue until now is that when I'm trying to access my second internal harddisk -(I use KDE4)from dolphin lets say- it appears many of the contents of hd but not all.Furthermore, when I open any of the folder inside this hd it appears nothing.
INFO:Hard disk with reiserfs that can access files from ubuntu 8.04
I opened then a terminal and tried to access the hd from command line. The directories and files that doesn't appear in dolphin appears with the ls -l command but without information for them.So it appears the filename and question mark like this:
?????????? ? ? ? ? ? dgh.png
-rw-r--r-- 1 1000 1000 1075817480 2008-07-02 17:28 TITLE02.avi
?????????? ? ? ? ? ? Transporter
I tried to change the owner and permission of these files as root but it says permission denied.
What could I do to see all the files of the harddisk?
- 01-30-2009 #2Just Joined!
- Join Date
- Nov 2006
- Posts
- 39
Could anyone help me?
- 01-30-2009 #3
Something is wrong with partition(s) of second harddisk. Execute fsck command on all partitions of second disk.
Post the output of fdisk -l command here.
Code:su - fdisk -l
It is amazing what you can accomplish if you do not care who gets the credit.
New Users: Read This First
- 02-02-2009 #4Just Joined!
- Join Date
- Nov 2006
- Posts
- 39
fsck /dev/sdb1
fsck 1.41.3 (12-Oct-200
fsck: fsck.reiserfs: not found
fsck: Error 2 while executing fsck.reiserfs for /dev/sdb1
fsck /dev/sdb
fsck 1.41.3 (12-Oct-200
e2fsck 1.41.3 (12-Oct-200
fsck.ext2: Superblock invalid, trying backup blocks...
fsck.ext2: Bad magic number in super-block while trying to open /dev/sdb
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
fdisk -l
Disk /dev/sda: 20.5 GB, 20576747520 bytes
255 heads, 63 sectors/track, 2501 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x8f8004b1
Device Boot Start End Blocks Id System
/dev/sda1 * 1 64 514048+ 82 Linux swap / Solaris
/dev/sda2 65 1313 10032592+ 83 Linux
/dev/sda3 * 1314 2501 9542610 83 Linux
Disk /dev/sdb: 17.1 GB, 17179869696 bytes
255 heads, 63 sectors/track, 2088 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x000bde95
Device Boot Start End Blocks Id System
/dev/sdb1 1 14946 120053713+ 83 Linux
thanks for the help
- 02-02-2009 #5Just Joined!
- Join Date
- Nov 2006
- Posts
- 39
From Ubuntu 8.04 I can see every file in this disk
- 02-05-2009 #6Just Joined!
- Join Date
- Nov 2006
- Posts
- 39
Devil's casper do you know if this is an fstab issue?
Any suggestions?
- 02-06-2009 #7Linux User
- Join Date
- Apr 2007
- Posts
- 289
Is your GRUB loader botched up?
https://answers.launchpad.net/ubuntu/+question/3548
- 02-06-2009 #8Problem is with Harddisk only. Try to mount partition manually and check if it works.fsck /dev/sdb
fsck 1.41.3 (12-Oct-200
e2fsck 1.41.3 (12-Oct-200
fsck.ext2: Superblock invalid, trying backup blocks...
fsck.ext2: Bad magic number in super-block while trying to open /dev/sdb
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
Code:su - mkdir /media/sdb1 umount /dev/sdb1 mount -t ext3 /dev/sdb1 /media/sdb1 ls /media/sdb1
It is amazing what you can accomplish if you do not care who gets the credit.
New Users: Read This First


Reply With Quote