Can't mount a newly created ext3 partition from the new Hard Disk I installed...

2005-12-22 Thread Dom 
I bought a Western Digital 80GB Hard Disk as a second disk for my
GNU/Linux Debian system (kernel 2.6.8-2-386).

I attached it as a Slave and set its jumper accordingly. The next step
was to create partition, and I created one by running (under root of
course) 'fdisk /dev/hdb' and using the command new (n) to create a
primary partition with partition number 1 for which I only used 12GB
(of 80GB available). Also with command 't' I made sure the filesystem
is ext3 (code 83).

I created a directory /music on which I plan to mount this filesystem.

Then I went to change my fstab file which now looks like this:


# /etc/fstab: static file system information.
#
# file system mount point   type  options   dump  pass
proc/proc   procdefaults0   0
/dev/hda1   /   ext3defaults,errors=remount-ro 0   1
/dev/hda2   /localdisk  ext3defaults0   0
/dev/hda5   noneswapsw  0   0
/dev/hdb1   /music  ext3defaults0   0
/dev/hdc/media/cdrom0   udf,iso9660 ro,users,noauto,unhide  0   0
/dev/hdd/media/cdrom1   udf,iso9660 ro,users,noauto,unhide  0   0
/dev/sda/media/usb0 autorw,users,noauto  0   0
/dev/sda1   /media/usb1 vfatrw,users,noauto  0   0
shmfs   /dev/shmshm defaults 0   0


I restarted my system and the filesystem was not mounted. Here's my syslog:


kernel: klogd 1.4.1#17, log source = /proc/kmsg started.
kernel: Inspecting /boot/System.map-2.6.8-2-386
kernel: Loaded 28182 symbols from /boot/System.map-2.6.8-2-386.
kernel: Symbols match kernel version 2.6.8.
kernel: No module symbols loaded - kernel modules not enabled.
kernel: Linux version 2.6.8-2-386 ([EMAIL PROTECTED])
(gcc version 3.3.5 (Debian 1:3.3.5-12)) #1 Thu May 19 17:40:50 JST
2005
kernel: BIOS-provided physical RAM map:
kernel:  BIOS-e820:  - 0009fc00 (usable)
kernel:  BIOS-e820: 0009fc00 - 000a (reserved)
kernel:  BIOS-e820: 000f - 0010 (reserved)
kernel:  BIOS-e820: 0010 - 0bffc000 (usable)
kernel:  BIOS-e820: 0bffc000 - 0bfff000 (ACPI data)
kernel:  BIOS-e820: 0bfff000 - 0c00 (ACPI NVS)
kernel:  BIOS-e820:  - 0001 (reserved)
kernel: 191MB LOWMEM available.
kernel: On node 0 totalpages: 49148
kernel:   DMA zone: 4096 pages, LIFO batch:1
kernel:   Normal zone: 45052 pages, LIFO batch:10
kernel:   HighMem zone: 0 pages, LIFO batch:1
kernel: DMI 2.3 present.
kernel: ACPI disabled because your bios is from 2000 and too old
kernel: You can enable it with acpi=force
kernel: Built 1 zonelists
kernel: Kernel command line: root=/dev/hda1 ro
kernel: Local APIC disabled by BIOS -- reenabling.
kernel: Found and enabled local APIC!
kernel: Initializing CPU#0
kernel: PID hash table entries: 1024 (order 10: 8192 bytes)
kernel: Detected 604.287 MHz processor.
kernel: Using tsc for high-res timesource
kernel: Console: colour VGA+ 80x25
kernel: Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
kernel: Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
kernel: Memory: 187500k/196592k available (1336k kernel code, 8468k
reserved, 732k data, 204k init, 0k highmem)
kernel: Checking if this processor honours the WP bit even in
supervisor mode... Ok.
kernel: Calibrating delay loop... 1187.84 BogoMIPS
kernel: Security Scaffold v1.0.0 initialized
kernel: Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
kernel: CPU: After generic identify, caps: 0383fbff   
kernel: CPU: After vendor identify, caps:  0383fbff   
kernel: CPU: L1 I cache: 16K, L1 D cache: 16K
kernel: CPU: L2 cache: 256K
kernel: CPU: After all inits, caps:0383fbff   0040
kernel: CPU: Intel Pentium III (Coppermine) stepping 01
kernel: Enabling fast FPU save and restore... done.
kernel: Enabling unmasked SIMD FPU exception support... done.
kernel: Checking 'hlt' instruction... OK.
kernel: Checking for popad bug... OK.
kernel: enabled ExtINT on CPU#0
kernel: ESR value before enabling vector: 
kernel: ESR value after enabling vector: 
kernel: Using local APIC timer interrupts.
kernel: calibrating APIC timer ...
kernel: . CPU clock speed is 604.0154 MHz.
kernel: . host bus clock speed is 100.0692 MHz.
kernel: checking if image is initramfs...it isn't (ungzip failed);
looks like an initrd
kernel: Freeing initrd memory: 4216k freed
kernel: NET: Registered protocol family 16
kernel: EISA bus registered
kernel: PCI: PCI BIOS revision 2.10 entry at 0xf0890, last bus=1
kernel: PCI: Using configuration type 1
kernel: mtrr: v2.0 (20020519)
kernel: ACPI: Subsystem revision 20040326
kernel: ACPI: Interpreter disabled.
kernel: Linux Plug and Play Support v0.97 (c) Adam Belay
kernel: PnPBIOS: Scanning system for

Re: Can't mount a newly created ext3 partition from the new Hard Disk I installed...

2005-12-22 Thread Mike McCarty 

Dom wrote:

I bought a Western Digital 80GB Hard Disk as a second disk for my
GNU/Linux Debian system (kernel 2.6.8-2-386).

I attached it as a Slave and set its jumper accordingly. The next step
was to create partition, and I created one by running (under root of
course) 'fdisk /dev/hdb' and using the command new (n) to create a
primary partition with partition number 1 for which I only used 12GB
(of 80GB available). Also with command 't' I made sure the filesystem
is ext3 (code 83).


Nope. You created a partition, not a file system.


I created a directory /music on which I plan to mount this filesystem.

Then I went to change my fstab file which now looks like this:


[snip]


I restarted my system and the filesystem was not mounted. Here's my syslog:


[snip]

What file system? I don't see where you ran mkfs.

All you've got is a blank partition.

Mike
--
p=p=%c%s%c;main(){printf(p,34,p,34);};main(){printf(p,34,p,34);}
This message made from 100% recycled bits.
You have found the bank of Larn.
I can explain it for you, but I can't understand it for you.
I speak only for myself, and I am unanimous in that!


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: Can't mount a newly created ext3 partition from the new Hard Disk I installed...

2005-12-22 Thread Dom 
On 12/22/05, Mike McCarty [EMAIL PROTECTED] wrote:

 What file system? I don't see where you ran mkfs.

 All you've got is a blank partition.

 Mike

Thanks Mike! I've done it.

Re: Can't mount a newly created ext3 partition from the new Hard Disk I installed...

2005-12-22 Thread Mike McCarty 

Dom wrote:

On 12/22/05, Mike McCarty [EMAIL PROTECTED] wrote:


What file system? I don't see where you ran mkfs.

All you've got is a blank partition.

Mike



Thanks Mike! I've done it.


Are you saying that you have now run mkfs and it mounts?

If so, then congratulations!

Or are you saying that you just omitted to mention that you
already ran mkfs, but it doesn't mount?

If so, then I'm as mystified as you are.

Mike
--
p=p=%c%s%c;main(){printf(p,34,p,34);};main(){printf(p,34,p,34);}
This message made from 100% recycled bits.
You have found the bank of Larn.
I can explain it for you, but I can't understand it for you.
I speak only for myself, and I am unanimous in that!


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: Can't mount a newly created ext3 partition from the new Hard Disk I installed...

2005-12-22 Thread Stephen Cormier 
On Thursday 22 December 2005 16:39, Dom wrote:
 I bought a Western Digital 80GB Hard Disk as a second disk for my
 GNU/Linux Debian system (kernel 2.6.8-2-386).

 I attached it as a Slave and set its jumper accordingly. The next
 step was to create partition, and I created one by running (under
 root of course) 'fdisk /dev/hdb' and using the command new (n) to
 create a primary partition with partition number 1 for which I only
 used 12GB (of 80GB available). Also with command 't' I made sure the
 filesystem is ext3 (code 83).

 I created a directory /music on which I plan to mount this
 filesystem.

 and this is what I get when I enter dmesg | tail:


 SCSI subsystem initialized
 VFS: Can't find ext3 filesystem on dev hdb1.
 VFS: Can't find ext3 filesystem on dev hdb1.


 Please help, I'm new with all of this and I really can't figure out
 what I did wrong nor can I find an adequate solution Googleing the
 web.

 Can you see what I'm doing wrong?

 Thanks in advance!

I see no mention of you having formatted the partition so.

mkfs.ext3 /dev/hdb1

Stephen


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: Can't mount a newly created ext3 partition from the new Hard Disk I installed...

2005-12-22 Thread Dom 
On 12/22/05, Mike McCarty [EMAIL PROTECTED] wrote:
 Dom wrote:
  On 12/22/05, Mike McCarty [EMAIL PROTECTED] wrote:
 
 What file system? I don't see where you ran mkfs.
 
 All you've got is a blank partition.
 
 Mike
 
 
  Thanks Mike! I've done it.

 Are you saying that you have now run mkfs and it mounts?

 If so, then congratulations!

 Or are you saying that you just omitted to mention that you
 already ran mkfs, but it doesn't mount?

 If so, then I'm as mystified as you are.

I'm saying that I have run mkfs only now and it mounts.

Thanks really on that, it's simply me not knowing...

Dom

Re: Can't mount a newly created ext3 partition from the new Hard Disk I installed...

2005-12-22 Thread Mike McCarty 

Dom wrote:

On 12/22/05, Mike McCarty [EMAIL PROTECTED] wrote:


[snip]


I'm saying that I have run mkfs only now and it mounts.

Thanks really on that, it's simply me not knowing...


Everybody's ignorant, just about different things.
Will Rogers

Mike
--
p=p=%c%s%c;main(){printf(p,34,p,34);};main(){printf(p,34,p,34);}
This message made from 100% recycled bits.
You have found the bank of Larn.
I can explain it for you, but I can't understand it for you.
I speak only for myself, and I am unanimous in that!


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]