Mounted Hi-MD, can't view folders...

otakuprinzess · 05-01-2005, 11:19 PM

Alright, I put my Hi-MD recorder in fstab and it is safely mounted.

If I open up the folder I can view the folders I have on the disc, but then as soon as I click to open it I get an error saying "Couldn't display (folder) The attempt to login failed."

Can anyone explain this to me? I can see the partion plain as day....

And just so you know, I'm using my Son MZNH600D.

Thanks!

~Prinzess

fancypiper · 05-02-2005, 12:59 AM

And the entry for your Hi-MD recorder in your /etc/fstab wasn't posted.

Are there any members with ESP around that can see that entry?

Sorry for the RTFM answer, but better details yield better answers.

I can't seem to make my drives work like I want
# Managing drives
LNAG - Accessing my drives
Rute - Device Mounting - Automatic Mounts: fstab

otakuprinzess · 05-02-2005, 01:33 AM

Errr..sorry.

Thanks for the links. RTFM indeed!

Okay, so here's the fstab entry:

Code:

/dev/sdb /mnt/himd vfat umask=0,user,iocharset=iso8859-15,sync,kudzu,codepage=850,noauto,exec,users 0 0

I just ass-u-me-ed that since I could see the drive and all was well that it was another issue than the fstab entry...

~Prinzess

fancypiper · 05-02-2005, 02:10 AM

I avoid usb as much as possible, but I do see a couple of problems.

1. /dev/sdb should have a partition number. Has the drive been partitioned and formatted, if so, how?

# How are the hard drives partitioned
fdisk -l

2. umask phrase should read: umask0,0,0

Here is my /etc/fstab for comparison:

Code:

# Duron 950 Fedora Core 1 uilleann /etc/fstab file
/dev/hdb8       /               ext3            defaults                1 1
/dev/hdb1       /boot           ext3            defaults                1 2
none            /dev/pts        devpts          gid=5,mode=620          0 0
/dev/hdb11      /home           ext3            defaults                1 2
none            /proc           proc            defaults                0 0
none            /dev/shm        tmpfs           defaults                0 0
/dev/hdb12      /pub            ext3            defaults                1 2
/dev/hdb2       swap            swap            defaults                0 0
/dev/cdrom      /mnt/cdrom      udf,iso9660     noauto,owner,kudzu,ro   0 0
/dev/fd0        /mnt/floppy     auto            noauto,owner,kudzu      0 0
#/dev/hdb9      /mnt/debian     ext3            defaults                1 2
#/dev/hdb10     /mnt/fc3        ext3            defaults                1 2
#/dev/hdc1      /mnt/backup     ext3            defaults                1 2
#/dev/hdc1      /mnt/wav        ext3            defaults                1 2
#/dev/hdc1      /mnt/fat32      vfat            defaults,umask0,0,0     0 0
/dev/hda1       /mnt/WindowsXP  ntfs            defaults                0 0
/dev/hda5       /mnt/NTFSStorage        ntfs    defaults                0 0

otakuprinzess · 05-02-2005, 02:36 AM

Thanks. I'll try the umask fix here in a sec.

Its not partitioned because it doesn't need to be partitioned; its a super floppy. The format, if I'm not mistaken, is fat32.

We'll see if this works.....

~Prinzess

otakuprinzess · 05-02-2005, 02:45 AM

Unfortuantely even after making the changes my HiMD fairs no better...

Here's an update on my fstab:

/dev/hdc1 / ext3 defaults 1 1
/dev/hdb /mnt/cdrom auto umask=0,user,iocharset=iso8859-1,codepage=850,noauto,ro,exec,users 0 0
/dev/sda1 /mnt/removable auto umask=0,user,iocharset=iso8859-1,sync,kudzu,codepage=850,noauto,exec,users 0 0
/dev/hda1 /mnt/windows ntfs umask=0,user,codepage=850,iocharset=iso8859-1,nls=iso8859-1,noauto,ro,exec,kudzu 0 0
/dev/sda4 /mnt/zip2 auto umask=0,0,0,user,iocharset=iso8859-1,sync,kudzu,codepage=850,noauto,exec,users 0 0
/dev/hdc5 swap swap defaults 0 0
/dev/sdb /mnt/himd vfat umask=0,0,0,user,iocharset=iso8859-15,sync,kudzu,codepage=850,noauto,exec,users 0 0

Now, I'm not too intelligent on the subject. But what I think might be happening is that the drive "times out." I've seen this happen in my Windows enviroment..where I have to open the file via the actual program its accessed with. But when I right-click or go into said program to open I have no luck...

~Prinzess

fancypiper · 05-02-2005, 03:26 AM

Perhaps you don't understand disk partitioning.

Results of this, please:

fdisk -l

I'll wager you will find a /dev/sdb1 partition you should have been using, rather than /dev/sdb which refers to an entire un-partitioned drive. You have to mount a partition of a hard drive.

Linux Partition HOWTO

I can't seem to make my drives work like I want
# Managing drives
LNAG - Accessing my drives
Rute - Device Mounting - Automatic Mounts: fstab

# Mandrake links
Mandrake home page
Mandrake Users website (needs money to access now)
Software management configuration: Easy urpmi config for Mandrake
Software management: urpmi mini-HOWTO
Software management: All You Ever Wanted to Know About Urpmi But Never Dared Asking Before
You didn't install the developmental packages? As root, command:
urpmi gcc
An Introduction to the Midnight Commander. You can install it by commanding:
urpmi mc
Midnight Commander home page

otakuprinzess · 05-02-2005, 10:39 AM

Hey fancypiper, thanks for all the help thus far.

I've looked around in MandrakeLinux Control Center and sure enough, you were right, it's partition was "sdb1."

So I edited fstab to reflect this, and now its not /dev/sdb but /dev/sdb1.

I'm just about ready to asume that the reports of people getting this to work are false, 'cause I've got nothing to go on.

I can't even mount the file system anymore, this is after I let Mandrake format one of my blank disks. You'd think that'd at least cure the problem.

Now everytime I try and mount it says

"Unable to mount selected volume. The volume is probably in a format that cannot be mounted."

Funny. DrakeDisk formatted it to fat32. Oh, go figure.

I'm reading some of the links you left for me, hopefully they will garnish better results.

~Prinzess

otakuprinzess · 05-02-2005, 11:17 AM

Alright, I'm so close now. Here's my fstab as it stands now:

/dev/hdc1 / ext3 defaults 1 1
/dev/hdb /mnt/cdrom auto umask=0,user,iocharset=iso8859-1,codepage=850,noauto,ro,exec,users 0 0
/dev/sda1 /mnt/removable auto umask=0,user,iocharset=iso8859-1,sync,kudzu,codepage=850,noauto,exec,users 0 0
/dev/hda1 /mnt/windows ntfs umask=0,user,codepage=850,iocharset=iso8859-1,nls=iso8859-1,noauto,ro,exec,kudzu 0 0
/dev/hdc5 swap swap defaults 0 0
/dev/sdb /mnt/himd vfat umask=0,user,iocharset=iso8859-1,sync,kudzu,codepage=850,noauto,exec,users 0 0
/dev/sdc4 /mnt/zip auto umask=0,user,iocharset=iso8859-1,sync,kudzu,codepage=850,noauto,exec,users 0 0

So my HiMD mounts cleanly, works, and its viewable.

You'll notice fstab now reports it again as /dev/sdb. I went a head and changed it just for the hell of it, and its working fine. Don't know why it works fine later than earlier, but that's the way its going.

But its read only.

Now we go to newbie territory...how do I change this so I can read and write?

Thanks again for all the help!

fancypiper · 05-02-2005, 11:47 AM

I have asked several times and gotten no answer. Why do you refuse to post the output of this, I wonder:

fdisk -l

How to get good answers with your questions about Linux

kudzu (the hardware probe/configurator) can act strange sometimes, therefore I removed it from /etc/fstab options so it couldn't screw it up any more.

The umask option (a board/google/LDP search will find lots of the answers I have already posted) will control the user access. Linux can safely write to Windows FAT, VFAT and FAT32 filesystems and several other non-Linux filesystems, but you are likely to corrupt an NTFS filesystem as it is still in the reverse-engineered, pre beta stage.

You can also open an x terminal and look at these for more (but geekier) information.

man mount
info mount
man fstab
info fstab
man umount
info umount

otakuprinzess · 05-02-2005, 07:51 PM

Ahh, forgot to mention.

fdisk -l

Bash: unrecognized command.

fancypiper · 05-02-2005, 08:30 PM

Did you remember that you need to be root to administer to your system?

Basic system administration
To change to the full root account (system administrator), if you are running X, open an x terminal and use these commands from your user account. Note the change in the prompt. You can do the same from a virtual terminal as well, but you can't open an x terminal to do so.

Code:

[fancy@tinwhistle fancy]$ su -
Password: <give root password and press enter>
[root@tinwhistle root]#

Remember, now whatever you command in root (it's the "god" mode. You can bless or destroy at your whim) usually gets done if enough system is left to carry out the command.

Sit on your hands and read the commands you type at least 3 times before pressing the enter key when in root.

Code:

Mon May 02 09:27 PM fancy@uilleann ~ $ su -
Password:
Mon May 02 09:28 PM root@uilleann ~ # fdisk -l
 
Disk /dev/hdc: 80.0 GB, 80026361856 bytes
255 heads, 63 sectors/track, 9729 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
 
   Device Boot    Start       End    Blocks   Id  System
/dev/hdc1   *         1      9729  78148161    c  Win95 FAT32 (LBA)
 
Disk /dev/hda: 82.3 GB, 82348277760 bytes
255 heads, 63 sectors/track, 10011 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
 
   Device Boot    Start       End    Blocks   Id  System
/dev/hda1   *         1      5008  40226728+   7  HPFS/NTFS
/dev/hda2          5009     10010  40178565    f  Win95 Ext'd (LBA)
/dev/hda5          5009     10010  40178533+   7  HPFS/NTFS
 
Disk /dev/hdb: 160.0 GB, 160041885696 bytes
255 heads, 63 sectors/track, 19457 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
 
   Device Boot    Start       End    Blocks   Id  System
/dev/hdb1   *         1         7     56196   83  Linux
/dev/hdb2             8       130    987997+  83  Linux
/dev/hdb3           131       143    104422+  83  Linux
/dev/hdb4           144     19457 155139705    5  Extended
/dev/hdb5           144      1056   7333641   83  Linux
/dev/hdb6          1057      1665   4891761   83  Linux
/dev/hdb7          1666      2274   4891761   83  Linux
/dev/hdb8          2275      2883   4891761   83  Linux
/dev/hdb9          2884      3492   4891761   83  Linux
/dev/hdb10         3493      4101   4891761   83  Linux
/dev/hdb11         4102      8357  34186288+  83  Linux
/dev/hdb12         8358     19457  89160718+  83  Linux
Mon May 02 09:28 PM root@uilleann ~ #

otakuprinzess · 05-02-2005, 10:08 PM

Gawd, I feel so stupid. Since the "command" was not found, I just figured it wasn't there. I didn't even bother to run it under root. It usually says "permission denied," but I suppose this is not the case with that command...

Here's whats going on at the moment:

Disk /dev/hda: 8037 MB, 8037679104 bytes
49 heads, 63 sectors/track, 5085 cylinders
Units = cylinders of 3087 * 512 = 1580544 bytes

Device Boot Start End Blocks Id System
/dev/hda1 * 1 5086 7849264+ 7 HPFS/NTFS

Disk /dev/hdc: 10.2 GB, 10262568960 bytes
255 heads, 63 sectors/track, 1247 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/hdc1 * 1 1194 9590773+ 83 Linux
/dev/hdc2 1195 1247 425722+ 5 Extended
/dev/hdc5 1195 1247 425691 82 Linux swap

Disk /dev/sda: 120.0 GB, 120034123776 bytes
255 heads, 63 sectors/track, 14593 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/sda1 1 14593 117218241 c W95 FAT32 (LBA)
Note: sector size is 2048 (not 512)

Disk /dev/sdb: 305 MB, 305915904 bytes
10 heads, 59 sectors/track, 253 cylinders
Units = cylinders of 590 * 2048 = 1208320 bytes

Disk /dev/sdb doesn't contain a valid partition table

Disk /dev/sdc: 100 MB, 100663296 bytes
64 heads, 32 sectors/track, 96 cylinders
Units = cylinders of 2048 * 512 = 1048576 bytes

Device Boot Start End Blocks Id System
/dev/sdc4 * 1 96 98288 6 FAT16

How does that work out?

/dev/sdb doesn't contain a valid partion table..how cute..I can still see and read everything! But its mounted read only. I used DiskDrake to format an MD into fat32, but it said the same damned thing. Go figure. But when I booted into Win2K I could see it the drive and use it all fine and dandy. So this morning I edited fstab and I just went with /dev/sdb instead of /dev/sdb1 and here we are: read only. Hmmph.

fancypiper · 05-02-2005, 10:28 PM

Well, on a drive /dev/hd<whatever> you can:

1. have from 1-4 primary partitions such as:
/dev/sda1

or

/dev/sda1
and
/dev/sda2

or

/dev/sda1
and
/dev/sda2
and
/dev/sda3

or

/dev/sda1
and
/dev/sda2
and
/dev/sda3
and
/dev/sda4.

2. One of these 4 partitions can be a, well, please, please, with sugar and cream on it, read the Linux Partition HOWTO. They explain much better than I can...

Links are posted to help, not be ignored, please a few clickies....

I can't seem to make my drives work like I want
# Managing drives
LNAG - Accessing my drives
Rute - Device Mounting - Automatic Mounts: fstab

Some stuff I have found handy:

What's this bash command stuff?
# Bash shell commands
Command Reference NHF
O'Reilly Directory of Linux Commands
# Handy bash commands I might use or ask a newbie to use:
# Find CPU specifications
cat /proc/cpuinfo
# Find running kernel version
uname -r
# What modules are loaded
cat /proc/modules
/sbin/lsmod
# What compiler version do I have installed
gcc -v
gcc --version
# What is the running kernel and compiler installed
cat /proc/version
# Find X server version
X -showconfig
# What pci cards are installed and what irq/port is used
cat /proc/pci
# What kernel modules are loaded
lsmod
# Memory and swap information
cat /proc/meminfo
free
An article: Tips for Optimizing Linux Memory
# How are the hard drives partitioned
fdisk -l
# How much free/used drive space
df -h
# What drives are mounted
mount
# How much used drive space in a directory
du -sh /path/to/directory
# Show disk usage by current directory and all subdirectories
du | less
# What is the distribution
cat /etc/.product
cat /etc/.issue
cat /etc/issue
cat /etc/issue.net
sysinfo
# For finding or locating files
find
locate (updatedb needs to be run first)
which
whereis
# Use dmesg to view the kernel ring buffer (error messages)
dmesg | less
# Watch error messages as they happen (sysklog needed)
as root, tail -f /var/log/messages (shows last 10 lines, use a number in front of f for more lines)
# What processes are running
ps -A
# Find a process by name
ps -ef | grep -i <plain text>
For example, XCDroast
ps -ef xcdroast
# See current environment list, or pipe to file
env | more
env > environmentvariablelist.txt
# Show current userid and assigned groups
id
# See all command aliases for the current user
alias
# See rpms installed on current system
rpmquery --all | less
rpmquery --all > <filename>
rpmquery --all | grep -i <plaintext>
Autospec for tarballs
RPM tools
# What directory am I using
pwd
# Get ls colors in less
ls --color=always | less -R
Look at man <command> or info <command> for the flags I used and for other options you can use for bash commands.

Are there any good Linux books?
# Good Linux books
Running Linux
Rute User's Tutorial and Exposition

fancypiper · 05-02-2005, 10:31 PM

Oh, btw, ignore the 1024 boundary error messages if you have a CPU bigger than an i386 processor. That is for backwards compatability. Most folk are i686 or higher now.

If you attempt to mount an extended partition (what you are attempting to do according to your /etc/fstab file), the drive does contain partitions as shown by your output, intepretatitation left to learner), Linux is smart enough to do what you are trying to tell it to do, but you are telling it wrong, so it does the best it can and mounts it read only.

Make a mount point for each of those partitions and mount each primary and logical partitions you found on that drive.

Edit /etc/fstab to reflect your changes and comment it so you can have some 'remembry.