LinuxQuestions.org
Go Job Hunting at the LQ Job Marketplace
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Newbie
User Name
Password
Linux - Newbie This Linux forum is for members that are new to Linux.
Just starting out and have a question? If it is not in the man pages or the how-to's this is the place!

Notices

Reply
 
Search this Thread
Old 02-23-2007, 05:19 AM   #31
Fixed_it
Member
 
Registered: Jun 2006
Location: New England
Distribution: FC11
Posts: 48

Original Poster
Rep: Reputation: 15

When I try to mount the drive I get a "/dev/sdb1 already mounted, or /mnt/sdb1 busy" I know it is not mounted, unless the mount point if somewhere hidden, not with the other mounted devices. Not sure why the directory just created would be busy. But if it is as you say and I was able to mkdosfs therefore I was able to write to it, then the LVM is hosed, cause issuing the Logical management commands cause there own errors. When I set it up on installation I left this drive alone (So I thought!). So I dont really understand.
 
Old 02-23-2007, 06:13 AM   #32
saikee
Senior Member
 
Registered: Sep 2005
Location: Newcastle upon Tyne UK
Distribution: Any free distro.
Posts: 3,398
Blog Entries: 1

Rep: Reputation: 112Reputation: 112
Let's confine our attention to the Linux from the Knoppix Live CD first.

I believe Knoppix could have mounted your sdb1 in /media directory which seems to be catching on whereas other distros could mount it on /mnt. So do try to check /media too. This could be the case with a modern distro like Knoppix which will mount every partitions that are mountable on a boot up. Since your sda1 has been formatted and so it has a valid filing structure inside and becomes an ideal candidate for a distro wanting to show that it can mount everything.

When Knoppix looks at your disk it may or may not be reading your LVM. If the LVM is broken then Knoppix can read/write sdb1 as a stand alone disk. Knoppix is the king of Live CD or at one time it was regarded as such. Fedora is a server based distro and so theese distros have radically outlooks on their ultimate applications and your sdb1 can be treated differently, especially if Knoppix doesn't read it as part of the LVM.

To me the right thing to do is to stick with a distro that can work with the sdb1, write some files on it and verify it is in a working order first before examining the problem it has with Fedora.

If you boot up the latest Slax and it still can't see sdb1 or reports the presence of sdb in "fdisk -l" then I would say it is a hardware problem. Before that I still think it could be LVM-related.

Fedora C6 is a Red Hat, Knoppix (latest is V5.1.1) is a Debian and Slax (latest V6)is from Slackware. The three opinions together are sufficient to tell what is wrong with sdb1. I wouldn't pay too much attention to the errors from just one distro especially the issue is complicated by the LVM.
 
Old 02-23-2007, 06:18 PM   #33
Fixed_it
Member
 
Registered: Jun 2006
Location: New England
Distribution: FC11
Posts: 48

Original Poster
Rep: Reputation: 15
Ok, I am getting more confused now! Knoppix is a no go. It performs the mkdosfs command, and shows the sdb1 disk on an fdisk -l, but it is not automatically mounted anywhere, and I am unable to manually mount it. So I tried each live disk in turn and I found that sdb1 was automatically mounted and I can write to it and read from it with Scientific Linux 5, which is a R.H.E. linux. isn't that the same as FC6?? Also of note was the inability to recognize the logical volume sda2. Anyway, it seems I do not have a hardware issue, but I am not sure were to go from here.
 
Old 02-23-2007, 06:30 PM   #34
saikee
Senior Member
 
Registered: Sep 2005
Location: Newcastle upon Tyne UK
Distribution: Any free distro.
Posts: 3,398
Blog Entries: 1

Rep: Reputation: 112Reputation: 112
It is pretty obvious to me that you either get an expert on how to repair your LVM or ditch it by reinstalling FC6 into a single partition.

If you give only one partition to FC6 installer to mount its "/" then the /boot will have to be a subdirectory to "/" and FC6 cannot use LVM if it wants itself to be booted.
 
Old 02-23-2007, 08:05 PM   #35
Fixed_it
Member
 
Registered: Jun 2006
Location: New England
Distribution: FC11
Posts: 48

Original Poster
Rep: Reputation: 15
Well I am not liking the LVM much, so I will ditch it when I get my external drive to back up data. So thats how to install without LVM, having the /boot as a subdirectory? I was looking for a radio button or command line option when I initially installed.
 
Old 02-24-2007, 02:35 AM   #36
saikee
Senior Member
 
Registered: Sep 2005
Location: Newcastle upon Tyne UK
Distribution: Any free distro.
Posts: 3,398
Blog Entries: 1

Rep: Reputation: 112Reputation: 112
If you look at the output of "fdisk -l" in your very first Post #1 you will see your FC6 has two partitions

sda1 type 83 for native Linux as /boot
sda2 type 8e as a LVM for the root of FC6.

Linux boot loaders Lilo and Grub cannot read a LVM so /boot must be created as a separate partition so that the kernels are placed there for access by the boot loaders, whenever a LVM is used.

If you offer only one partition to the FC6 installer then /boot will be a subdirectory inside "/", same as /home, /usr, /etc, /var etc. Since there is only one partition FC6 installer cannot install LVM.

Last edited by saikee; 02-24-2007 at 02:37 AM.
 
Old 03-17-2007, 09:35 AM   #37
Fixed_it
Member
 
Registered: Jun 2006
Location: New England
Distribution: FC11
Posts: 48

Original Poster
Rep: Reputation: 15
Hope you are still there....
I finally got things up and able to re-install. And believe it or not there is no change at all!!

fdisk -l:
Quote:
Disk /dev/sda: 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/sda1 * 1 25 200781 83 Linux
/dev/sda2 26 90 522112+ 82 Linux swap / Solaris
/dev/sda3 91 9729 77425267+ 83 Linux

Disk /dev/sdb: 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/sdb1 * 1 10011 80413326 b W95 FAT32
mount :
Quote:
[root@localhost ~]# mount
/dev/sda3 on / type ext3 (rw)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
devpts on /dev/pts type devpts (rw,gid=5,mode=620)
/dev/sda1 on /boot type ext3 (rw)
tmpfs on /dev/shm type tmpfs (rw)
none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw)
sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw)
/dev/sdc1 on /media/DellUtility type vfat (rw,noexec,nosuid,nodev,shortname=winnt,uid=500)
/dev/sdc2 on /media/disk type vfat (rw,noexec,nosuid,nodev,shortname=winnt,uid=500)
and finally /dev :
Quote:
[root@localhost dev]# ls
adsp fd0u360 port stderr tty38 usb
agpgart fd0u720 ppp stdin tty39 usbdev1.1_ep00
audio fd0u800 ptmx stdout tty4 usbdev1.1_ep81
bus fd0u820 pts systty tty40 usbdev1.4_ep00
cdrom fd0u830 ram tty tty41 usbdev1.4_ep81
cdrom-hda floppy-fd0 ram0 tty0 tty42 usbdev2.1_ep00
cdrom-hdb full ram1 tty1 tty43 usbdev2.1_ep81
cdrw gpmctl ram10 tty10 tty44 usbdev3.1_ep00
cdrw-hda hda ram11 tty11 tty45 usbdev3.1_ep81
cdrw-hdb hdb ram12 tty12 tty46 usbdev4.1_ep00
cdwriter hpet ram13 tty13 tty47 usbdev4.1_ep81
cdwriter-hda initctl ram14 tty14 tty48 usbdev5.1_ep00
cdwriter-hdb input ram15 tty15 tty49 usbdev5.1_ep81
console kmsg ram2 tty16 tty5 usbdev5.2_ep00
core log ram3 tty17 tty50 usbdev5.2_ep01
cpu loop0 ram4 tty18 tty51 usbdev5.2_ep82
disk loop1 ram5 tty19 tty52 vcs
dri loop2 ram6 tty2 tty53 vcs1
dsp loop3 ram7 tty20 tty54 vcs2
dvd loop4 ram8 tty21 tty55 vcs3
dvd-hda loop5 ram9 tty22 tty56 vcs4
dvd-hdb loop6 ramdisk tty23 tty57 vcs5
dvdrw loop7 random tty24 tty58 vcs6
dvdrw-hdb lp0 root tty25 tty59 vcs7
dvdwriter MAKEDEV rtc tty26 tty6 vcs8
dvdwriter-hdb mapper sda tty27 tty60 vcsa
fd md0 sda1 tty28 tty61 vcsa1
fd0 mem sda2 tty29 tty62 vcsa2
fd0u1040 mixer sda3 tty3 tty63 vcsa3
fd0u1120 net sdb tty30 tty7 vcsa4
fd0u1440 null sdb1 tty31 tty8 vcsa5
fd0u1680 nvram sequencer tty32 tty9 vcsa6
fd0u1722 par0 sequencer2 tty33 ttyS0 vcsa7
fd0u1743 parport0 sg0 tty34 ttyS1 vcsa8
fd0u1760 parport1 sg1 tty35 ttyS2 X0R
fd0u1840 parport2 shm tty36 ttyS3 xen
fd0u1920 parport3 snd tty37 urandom zero
In startup I have the same error that it was already mounted or the mount point was busy. This has gone on too long. please advise. thanks again
 
Old 04-02-2007, 04:06 PM   #38
saikee
Senior Member
 
Registered: Sep 2005
Location: Newcastle upon Tyne UK
Distribution: Any free distro.
Posts: 3,398
Blog Entries: 1

Rep: Reputation: 112Reputation: 112
I have been away for two weeks.

Your current setup is different in it there is no longer any LVM. That should make life simpler.

I have not kept up to date with your problem but sdb1 should be mountable manually by commands
Code:
mkdir /mnt/sdb1
mount /dev/sdb1 /mnt/sdb1
The above will fail "only" if sdb1 has no filing system inside or has not been formatted. A partition can only be mounted if it can be read or written. To do it there must be a filing system or the partition has been formatted.

Modern Linux does not need the filing type declared but older kernel may required the use of the "t" parameter like
Code:
mount -t vfat /dev/sdb1 /mnt/sdb1
Get the partition mounted manually first before implementing it in the /etyc/fstab
 
Old 04-15-2007, 03:27 PM   #39
Fixed_it
Member
 
Registered: Jun 2006
Location: New England
Distribution: FC11
Posts: 48

Original Poster
Rep: Reputation: 15
I haven't given up, but....
repartitioned the sda drive so I could put a few more distros on it. What I found was 2 of the 2 new distros were able to see the sdb drive with no problem, no configuration at all. I checked the fstab to see if it was any different than what I had in FC6 but there was none. seems to me there is a bug here. The drive is definitely not mountable in FC6, so I will wait to see if it is fixed in FC7 I guess. Thanks for the help, it was greatly appreciated. It doesn't look like this will get resolved in the way I was hoping, but it works now, kinda, after 2 installs later. I needed to get out and see other distros any way....
hey what are all those numbers scrolling up my screen now-AHHHHH see you in the wireless troubleshooting section
 
  


Reply

Tags
mount, sata, secondary


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
where are files after mount sdb1? LetMeTryToo Linux - Newbie 3 11-08-2006 03:52 AM
mount: /dev/sdb1 is not a valid block device zaltar Linux - General 8 07-13-2005 02:07 AM
SDB1 IS NOT A VALID BLOCK DEVICE - CF reader help woodo Linux - Software 12 07-07-2004 09:52 AM
mount: wrong fs type, bad option, bad superblock on /dev/sdb1 pmoreira Linux - Hardware 5 02-26-2004 10:31 AM
sdb but no sdb1? Moebius Linux - Hardware 3 02-15-2004 06:16 AM


All times are GMT -5. The time now is 11:04 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