hello here below the fstab from laptop2: # /etc/fstab: static file system information. # # <file system> <mount point> <type> <options> <dump> <pass> proc /proc proc defaults 0 0 /dev/sda5 / ext3 defaults,errors=remount-ro 0 1 /dev/sda8 /E vfat uid=1000,gid=1001,user,rw,umask=022,noexec,nosuid,codepage=850,iocharset=iso8859-15 0 2 /dev/sda6 /home ext3 defaults 0 2 /dev/sda3 none swap sw 0 0 /dev/hdc /media/cdrom0 udf,iso9660 ro,user,noauto 0 0 /dev/fd0 /media/floppy0 auto rw,user,noauto 0 0 /dev/sda7 /data ext3 defaults 0 2
Regarding the syslog of laptop2, again no error appeared in it regarding sda8 or sda during the crash time. And the crash occurred again today, after the vfat was re-formatted yesterday !! The programs that where open during the crash: oowriter, thunderbird. But the only messages showed indicates just that the /E was empty. No application crash error. I really do not see what is appening. Juan. Le Monday 13 February 2006 14:39, Johannes Wiedersich a écrit : > Juan Piñeros wrote: > > ------------------------------------------------- > > cat /etc/fstab > > # /etc/fstab: static file system information. > > # > > # <file system> <mount point> <type> <options> > > <dump> <pass> > > proc /proc proc defaults 0 > > 0 > > #cd-rom > > /dev/hdc /media/cdrom0 iso9660 ro,user,noauto 0 > > 0 > > #hard disk > > /dev/hda3 / ext3 > > defaults,errors=remount-ro 0 1 > > /dev/hda2 none swap sw 0 > > 0 > > /dev/hda6 /mnt/hda6 ext3 defaults 0 > > 2 > > /dev/hda1 /mnt/hda1 ntfs > > gid=1002,user,rw,umask=002,noexec,nosuid 0 0 > > Well, I wouldn't mount ntfs with rw! > According to the documentation found in (sarge has the slightly older > 2.6.8 kernel): > /usr/src/linux-source-2.6.12/Documentation/filesystems/ntfs.txt > > To mount an NTFS 1.2/3.x (Windows NT4/2000/XP/2003) volume, use the file > system type 'ntfs'. The driver currently supports read-only mode (with > no fault-tolerance, encryption or journalling) and very limited, but > safe, write support. > > From your description of the fat32 problem, I cannot say anything of > what might have happened. > > What were the first symptoms of the problem? How did it first show off? > What does syslog say about it? Have you run smartctl from package > smartmontools to diagnose the hardware status of the disks? > > Johannes
