LinuxQuestions.org
Support LQ: Use code LQ3 and save $3 on Domain Registration
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Networking
User Name
Password
Linux - Networking This forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.

Notices

Reply
 
Search this Thread
Old 06-05-2005, 12:09 PM   #1
wael_nasreddine
Member
 
Registered: Jun 2004
Location: France
Distribution: debian sarge
Posts: 109

Rep: Reputation: 15
NFS killing me, (can't read superblock)


Hey guys,

Problem

i don't know why, but NFS suddenly stop working yesterday night, i wanted to unmount my shared USB HDD so i stoped manually nfs-kernel-server, and portmap, after i plug it (even after server-client restarting) i keep getting the message
Code:
wael@nasreddine:~$ sudo mount /media/WAEL_FAT/
mount: 192.168.3.2:/media/WAEL_FAT: can't read superblock
wael@nasreddine:~$ sudo mount -t nfs 192.168.3.2:/ /media/SERVER/
mount: 192.168.3.2:/: can't read superblock

Information
client:

Code:
wael@nasreddine:~$ rpcinfo -p 192.168.3.2
   program vers proto   port
    100000    2   tcp    111  portmapper
    100000    2   udp    111  portmapper
    100003    2   udp   2049  nfs
    100003    3   udp   2049  nfs
    100003    4   udp   2049  nfs
    100003    2   tcp   2049  nfs
    100003    3   tcp   2049  nfs
    100003    4   tcp   2049  nfs
    100021    1   udp  32770  nlockmgr
    100021    3   udp  32770  nlockmgr
    100021    4   udp  32770  nlockmgr
    100021    1   tcp  32768  nlockmgr
    100021    3   tcp  32768  nlockmgr
    100021    4   tcp  32768  nlockmgr
    100005    1   udp    865  mountd
    100005    1   tcp    868  mountd
    100005    2   udp    865  mountd
    100005    2   tcp    868  mountd
    100005    3   udp    865  mountd
    100005    3   tcp    868  mountd
    100024    1   udp    603  status
    100024    1   tcp    606  status
wael@nasreddine:~$
wael@nasreddine:~$ ps -edf |grep po
daemon    6543     1  0 13:51 ?        00:00:00 /sbin/portmap
wael@nasreddine:~$ cat /etc/fstab
192.168.3.2:/media/WAEL_FAT     /media/WAEL_FAT nfs     rw,hard,intr,noauto     0       0
192.168.3.2:/   /media/SERVER   nfs     rw,hard,noauto  0       0
192.168.3.2:/media/REDOUANE     /media/REDOUANE nfs     rw,hard,intr,noauto     0       0
wael@nasreddine:~$ showmount -e 192.168.3.2
Export list for 192.168.3.2:
/               192.168.2.0/255.255.255.0,192.168.1.0/255.255.255.0
/media/REDOUANE 192.168.2.0/255.255.255.0,192.168.1.0/255.255.255.0
/media/WAEL_FAT 192.168.1.0/255.255.255.0,server.local,192.168.2.0/255.255.255.0

server:
Code:
server:/etc# cat /etc/exports
/       192.168.1.0/255.255.255.0(rw,sync) 192.168.2.0/255.255.255.0(rw,sync)

/media/WAEL_FAT 192.168.1.0/255.255.255.0(rw,sync) 192.168.2.0/255.255.255.0(rw,sync)

/media/REDOUANE 192.168.1.0/255.255.255.0(rw,sync) 192.168.2.0/255.255.255.0(rw,sync)
server:/etc# cat hosts.allow
portmap: 192.168.2.0/255.255.255.0 192.168.1.0/255.255.255.0
mountd: 192.168.2.0/255.255.255.0 192.168.1.0/255.255.255.0
rquotad: 192.168.2.0/255.255.255.0 192.168.1.0/255.255.255.0
statd: 192.168.2.0/255.255.255.0 192.168.1.0/255.255.255.0
server:/etc# cat hosts.deny
portmap: ALL
mountd: ALL
rquotad: ALL
statd: ALL
server:/etc# cat fstab
### adding external Hard disks
/dev/sda2       /media/WAEL_FAT vfat    defaults,auto,uid=1000,gid=1000,iocharset=utf8  0       0
server:/etc# ls /media/WAEL_FAT/
AuthorizationForm.doc  ClickHere.exe  ClickHere.ini  CRAZY FROG Axel F .wma  gdiplus.dll  mmc  Redouane_merci wael  server.zip  wael  yvon
Question
what's going on, i tried almost everything, i can't get into the HDD using NFS


Thanks in advance

Last edited by wael_nasreddine; 06-05-2005 at 12:15 PM.
 
Old 06-05-2005, 10:51 PM   #2
ARC1450
Member
 
Registered: Jun 2005
Location: Odenton, MD
Distribution: Gentoo
Posts: 290

Rep: Reputation: 30
Did you stop NFS before umounting your USB thumbdrive?

I found out that if, for some reason, my server umounts a drive before stopping NFS, things go to hell real quick. I have to umount the drives on the NFS clients, then stop the NFS service on the server, then umount the drives on the server, then reverse the process. If I don't, my computer gets very angry, very quickly.
 
Old 06-06-2005, 03:30 AM   #3
wael_nasreddine
Member
 
Registered: Jun 2004
Location: France
Distribution: debian sarge
Posts: 109

Original Poster
Rep: Reputation: 15
indeed i forget to unmount it from the client before, but i did stop NFS server, samba Server and unmount the HDD to unplug it safely,
but i didn't unmount it from the client before
so any suggestions please???
 
Old 06-06-2005, 09:11 AM   #4
ARC1450
Member
 
Registered: Jun 2005
Location: Odenton, MD
Distribution: Gentoo
Posts: 290

Rep: Reputation: 30
The only suggestion I can offer is to kill NFS on both machines, then mount the drive on your server, start the nfs server apps, then start the nfs client apps on your client computer, then try to mount the drive.

If that doesn't work, you can always try *shudder* a reboot as a last resort to kill anything that's lurking.
 
Old 06-06-2005, 09:40 AM   #5
wael_nasreddine
Member
 
Registered: Jun 2004
Location: France
Distribution: debian sarge
Posts: 109

Original Poster
Rep: Reputation: 15
oh i reboot serval times both server and client
and also i apt-get remove --purge nfs-kernel-server pormap nfs-common and then apt-get install nfs-kernel-server portmap nfs-common on both server and client (client without the nfs-kernel-server package) serval times
same result :'(
 
Old 06-06-2005, 09:54 AM   #6
ARC1450
Member
 
Registered: Jun 2005
Location: Odenton, MD
Distribution: Gentoo
Posts: 290

Rep: Reputation: 30
Well, I'm out of ideas then. All that stuff always works for me.

So consider this a type of bump.
 
Old 06-06-2005, 10:12 AM   #7
bramhastra
Member
 
Registered: May 2005
Location: India
Distribution: RHEL 4.0
Posts: 136

Rep: Reputation: 15
Well i wuld suggest you to stop all the nfs services then reconfigure your file do all the stuff you did in the past and then again restart the service.

Also this looks weird but I have seen this times that if you get such messages in GUI switch to command mode you wont get them and vice versa
 
Old 06-06-2005, 10:20 AM   #8
wael_nasreddine
Member
 
Registered: Jun 2004
Location: France
Distribution: debian sarge
Posts: 109

Original Poster
Rep: Reputation: 15
it's realy killing me because as i mentioned in the first post, i tried everything, reconfigure, reboot, reinstall, of course not formatting yet,
it happened to me once before but i was preparing the server for a format and distribution change (from ubuntu to debian) so i didn't get deep in it, after a format it worked but i can't format the server each time it stops working, i have sites on ther server can't turn it off whenever i want
so a help is really appreciated, i'll take above advices and i'll proceed now to try to re-reconfigure and re-reinstall to see if any difference

thx for reply guys
 
Old 06-06-2005, 10:27 AM   #9
wael_nasreddine
Member
 
Registered: Jun 2004
Location: France
Distribution: debian sarge
Posts: 109

Original Poster
Rep: Reputation: 15
is it normal that a FAT HDD cannot be scanned via fsck??
Code:
server:~# fsck /dev/sdb
fsck 1.37 (21-Mar-2005)
e2fsck 1.37 (21-Mar-2005)
Couldn't find ext2 superblock, 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:
server:~# e2fsck -b 8193 /dev/sdb
e2fsck 1.37 (21-Mar-2005)
e2fsck: 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>
 
Old 06-06-2005, 10:39 AM   #10
bramhastra
Member
 
Registered: May 2005
Location: India
Distribution: RHEL 4.0
Posts: 136

Rep: Reputation: 15
Have u given an entry for the device to auto mount if yes remove it or see the fstab file whether it has an entry or not
 
Old 06-06-2005, 10:47 AM   #11
wael_nasreddine
Member
 
Registered: Jun 2004
Location: France
Distribution: debian sarge
Posts: 109

Original Poster
Rep: Reputation: 15
yes, it has default so it will be auto mounted
/dev/sdb2 /media/WAEL_FAT vfat defaults,auto,uid=1000,gid=1000,iocharset=utf8 0 0
 
Old 06-06-2005, 11:47 AM   #12
bramhastra
Member
 
Registered: May 2005
Location: India
Distribution: RHEL 4.0
Posts: 136

Rep: Reputation: 15
remove that it will be solved
 
Old 06-06-2005, 03:14 PM   #13
wael_nasreddine
Member
 
Registered: Jun 2004
Location: France
Distribution: debian sarge
Posts: 109

Original Poster
Rep: Reputation: 15
i tried it didn't work, i'll try to reboot both server and client and retry
 
Old 06-09-2005, 06:41 PM   #14
wael_nasreddine
Member
 
Registered: Jun 2004
Location: France
Distribution: debian sarge
Posts: 109

Original Poster
Rep: Reputation: 15
nope it didn't work
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Superblock could not be read captainfreedom Linux - Newbie 2 03-02-2005 02:09 PM
/dev/sda1 - 'Can't read superblock' dickmobbis Fedora 1 12-02-2004 04:06 PM
Superblock could not be read zatka Red Hat 12 01-27-2004 04:22 AM
can't read superblock - new kernel jamesstaylor Linux - Newbie 3 09-29-2003 11:01 AM
unable to read superblock SPiZ Linux - General 2 12-31-2002 06:30 PM


All times are GMT -5. The time now is 05:23 AM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration