Results 1 to 10 of 11
I have installed suse 11.1 but whenever i shutdown it freezes at..
unmounting fuse control file system --------- failed
unmounting file system
there's one more problem...
it detects my pendrive ...
- 01-27-2009 #1Just Joined!
- Join Date
- Jan 2009
- Posts
- 11
shutdown problem in suse....
I have installed suse 11.1 but whenever i shutdown it freezes at..
unmounting fuse control file system --------- failed
unmounting file system
there's one more problem...
it detects my pendrive but whenever i try to access it, it gives an error..
- 01-27-2009 #2Just Joined!
- Join Date
- Jan 2009
- Posts
- 6
Can you give me what error it shows???
- 01-27-2009 #3Just Joined!
- Join Date
- Jan 2009
- Posts
- 11
thanks for quick reply...
thanks for the quick reply.....
error : "org.freedesktop.DBus.Error.NoReply:did not recieve a reply.possible causes include: remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout period, or the network connection was broken."
this was the error shown by Dolphin, while Konquerer shows pendrive in sysinfo:
but on clicking on its link doen't respond.
- 01-27-2009 #4Linux Guru
- Join Date
- Jan 2009
- Location
- Dover, NH
- Posts
- 1,633
A umount will fail if anything is still running that keeps the device open. Everything is supposed to be killed before you get to that stage, but sometimes something is real stubborn. The fact that you're running through fuse tells me something is not using a native interface.
As far as the USB device: Sounds like the pen drive is using an encrypted file system. You'll be able to see it but will not be able to access the files on it (if I'm right).
I hope I'm wrong on both accounts, but we'll see. With the computer up and running and the pen drive plugged in, open a terminal to run these commands and post their outputs:
We'll see what we can come up with.Code:user@computer ~$ su Enter Password for root: (Enter PW: no echo) root@computer /home/user# fdisk -l (Post Output) root@computer /home/user# cat /etc/fstab (Post Output)
- 01-27-2009 #5Just Joined!
- Join Date
- Jan 2009
- Posts
- 11
..thanks...
I am logged in as root
and on running these commands in Konsole this is what I m getting:
linux-rv33:~ # fdisk -l
Disk /dev/sda: 80.0 GB, 80026361856 bytes
255 heads, 63 sectors/track, 9729 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0xb96ab96a
Device Boot Start End Blocks Id System
/dev/sda1 1 1698 13631152 7 HPFS/NTFS
/dev/sda2 * 1698 2363 5341582 83 Linux
/dev/sda3 2434 9728 58597087+ f W95 Ext'd (LBA)
/dev/sda4 2363 2433 570307 82 Linux swap / Solaris
/dev/sda5 2434 5697 26218048+ 7 HPFS/NTFS
/dev/sda6 5698 8423 21896563+ 7 HPFS/NTFS
/dev/sda7 8424 9728 10482381 7 HPFS/NTFS
Partition table entries are not in disk order
Disk /dev/sdb: 511 MB, 511488000 bytes
56 heads, 32 sectors/track, 557 cylinders
Units = cylinders of 1792 * 512 = 917504 bytes
Disk identifier: 0x00000000
Device Boot Start End Blocks Id System
/dev/sdb1 1 558 499312 b W95 FAT32
linux-rv33:~ # cat /etc/fstab
/dev/disk/by-id/ata-WDC_WD800BB-60JKA0_WD-WCAMD1054225-part4 swap swap defaults 0 0
/dev/disk/by-id/ata-WDC_WD800BB-60JKA0_WD-WCAMD1054225-part2 / ext3 acl,user_xattr 1 1
/dev/disk/by-id/ata-WDC_WD800BB-60JKA0_WD-WCAMD1054225-part1 /windows/C ntfs-3g users,gid=users,fmask=133,dmask=022,locale=en_US.U TF-8 0 0
/dev/disk/by-id/ata-WDC_WD800BB-60JKA0_WD-WCAMD1054225-part5 /windows/D ntfs-3g users,gid=users,fmask=133,dmask=022,locale=en_US.U TF-8 0 0
/dev/disk/by-id/ata-WDC_WD800BB-60JKA0_WD-WCAMD1054225-part6 /windows/E ntfs-3g users,gid=users,fmask=133,dmask=022,locale=en_US.U TF-8 0 0
/dev/disk/by-id/ata-WDC_WD800BB-60JKA0_WD-WCAMD1054225-part7 /windows/F ntfs-3g users,gid=users,fmask=133,dmask=022,locale=en_US.U TF-8 0 0
proc /proc proc defaults 0 0
sysfs /sys sysfs noauto 0 0
debugfs /sys/kernel/debug debugfs noauto 0 0
usbfs /proc/bus/usb usbfs noauto 0 0
devpts /dev/pts devpts mode=0620,gid=5 0 0
/dev/sdb1 /mnt/usb msdos noauto 0 0
- 01-27-2009 #6Linux Guru
- Join Date
- Jan 2009
- Location
- Dover, NH
- Posts
- 1,633
Well, I don't see anything particularly wrong with the hard drive setup, so the shutdown issue doesn't appear to be here.
The usb key however is.
With this, the pen drive will not auto-mount. Two possible solutions:/dev/sdb1 /mnt/usb msdos noauto 0 0
1) (assuming a GUI is loaded; for some reason, I can't make auto-mount work on USB devices without it) as root, pull the pen drive and edit /etc/fstab to remove or comment out the above line. Should restore auto mounting.
or
2) manually mount the pen drive with sudo mount /dev/sdb1 (sudo (or execute as root) because the key user is not specified in fstab), and according to the fstab, the mount will be made to /mnt/usb.
Let me know how this works.
- 01-27-2009 #7Linux Guru
- Join Date
- Jan 2009
- Location
- Dover, NH
- Posts
- 1,633
I just remembered something... if you chose the manual mount method, you'll need to edit fstab anyway or the pen drive will likely be read-only to everyone but root... edit that one line to read:
/dev/sdb1 /mnt/usb vfat noauto,rw,user,umask=0000 0 0
These edits will allow either FAT 16 or 32 will full LFN support, users can mount the device, and all users can read and write to the drive.
- 01-28-2009 #8Just Joined!
- Join Date
- Jan 2009
- Posts
- 11
..thanks for your help.
actually I added this line for usb, as without it and now even with that line usb drive is not working. So I think I should modify this line....as you have told, I hope it works...
thanks once again....
- 01-28-2009 #9Just Joined!
- Join Date
- Jan 2009
- Posts
- 11
...not working!
I have edited the /etc/fstab
by writing....
now on manual mounting.... its giving a warning..Code:/dev/sdb1 /mnt/usb vfat noauto,rw,user,umask=0000 0 0
and its stops there......Code:linux-rv33:~ # sudo mount /dev/sdb1 [mntent]: warning: no final newline at the end of /etc/fstab
I dont know whats the problem as pendrive was working correctly in suse 10.3
Its vfat and surely not encrypted....as it can be accessed on any other system..
- 01-29-2009 #10Linux Guru
- Join Date
- Jan 2009
- Location
- Dover, NH
- Posts
- 1,633
mount is a little fickle with the fstab. Re-edit and make sure the file actually ends with a blank line.


Reply With Quote