iB::Topic::mounting /dev/sda2

	Damn Small Linux :: Damn Small Linux Board The DSL Forums

» Welcome Guest
[ Log In :: Register ]

Damn Small Linux Board » Damn Small Linux » USB booting » mounting /dev/sda2

		Mini-ITX Boards Sale, Fanless BareBones Mini-ITX, Bootable 1G DSL USBs, 533MHz Fanless PC <-- SALE $200 each!
		Get The Official Damn Small Linux Book. DSL Market , Great VPS hosting provided by Tektonic

[ Track this topic :: Email this topic :: Print this topic ]

Topic: mounting /dev/sda2, 2nd data - linux partition

< Next Oldest | Next Newest >

dewman

Group: Members
Posts: 3
Joined: June 2005

Posted: July 01 2005,18:38

Ok, so I have to finally post a question to the forum. I have a lexar 256 jump drive. DSL is up and running from booting off the usb drive. Everything works wonderfully , but I can't get the second partition to mount after booting.

If I put the drive in my Suse box, and can mount it and write to it just fine. But, under DSL, a mount attempt just results in an invalid block device error.

I'm thinking I'm booting with the wrong parameters, or mounting improperly for dsl.

mount /dev/sda2 /mnt is what I've been using. Like I said, it works under my other linux box.

Any suggestions on what to try? I've tried a bunch of things, like specifying the fs type, and mounting it somewhere else. Nothing seems to work.

Thanks,
dewman

from my suse box...

Code Sample

# fdisk -l /dev/sda

Disk /dev/sda: 262 MB, 262144000 bytes
16 heads, 32 sectors/track, 1000 cylinders
Units = cylinders of 512 * 512 = 262144 bytes

Device Boot Start End Blocks Id System
/dev/sda1 * 1 250 63999+ 6 FAT16
/dev/sda2 251 984 187904 83 Linux

dmesg
usb 1-2: new full speed USB device using address 3
usb 1-2: Product: JUMPDRIVE2
usb 1-2: Manufacturer: LEXAR MEDIA
usb 1-2: SerialNumber: 0000002726
Initializing USB Mass Storage driver...
scsi0 : SCSI emulation for USB Mass Storage devices
Vendor: Generic Model: STORAGE DEVICE Rev: 1.25
Type: Direct-Access ANSI SCSI revision: 02
SCSI device sda: 512000 512-byte hdwr sectors (262 MB)
sda: assuming Write Enabled
sda: assuming drive cache: write through
sda: sda1 sda2
Attached scsi removable disk sda at scsi0, channel 0, id 0, lun 0
USB Mass Storage device found at 3
drivers/usb/core/usb.c: registered new driver usb-storage
USB Mass Storage support registered.
Attached scsi generic sg0 at scsi0, channel 0, id 0, lun 0, type 0

dewman

Group: Members
Posts: 3
Joined: June 2005

Posted: July 01 2005,18:39

I forgot to mention, I formatted the /dev/sda2 partition as ext2.

dewman - not logged in
Unregistered

Posted: July 01 2005,19:27

Here is the dmesg from within dsl. I would belive it if I hadn't been able to get it to mount and work on suse.

Also, some attempts to show the geometry in dsl, as well as a df -k.

Code Sample

m main memory to use for agp memory: 1185M
agpgart: Detected Intel(R) 855PM chipset
agpgart: AGP aperture is 128M @ 0xe0000000
usb_control/bulk_msg: timeout
usb_control/bulk_msg: timeout
usb_control/bulk_msg: timeout
usb.c: USB disconnect on device 00:1d.7-6.4 address 5
hub.c: new USB device 00:1d.7-6.4, assigned address 7
WARNING: USB Mass Storage data integrity not assured
USB Mass Storage device found at 7
usb-storage: host_reset() requested but not implemented
scsi: device set offline - command error recover failed: host 0 channel 0 id 0 lun 0
SCSI disk error : host 0 channel 0 id 0 lun 0 return code = 6050000
I/O error: dev 08:01, sector 6674
FAT: Did not find valid FSINFO signature.
Found signature1 0x4e0005 signature2 0xc00b6600 sector=1.
VFS: Can't find a valid FAT filesystem on dev 03:01.
FAT: Did not find valid FSINFO signature.
Found signature1 0x4e0005 signature2 0xc00b6600 sector=1.
VFS: Can't find a valid FAT filesystem on dev 03:01.
NTFS driver v1.1.22 [Flags: R/W MODULE]
I/O error: dev 08:01, sector 6674
Directory sread (sector 0x1a12) failed
I/O error: dev 08:01, sector 6674
Directory sread (sector 0x1a12) failed
I/O error: dev 08:01, sector 6674
Directory sread (sector 0x1a12) failed
I/O error: dev 08:01, sector 6674
Directory sread (sector 0x1a12) failed
I/O error: dev 08:01, sector 6674
Directory sread (sector 0x1a12) failed
I/O error: dev 08:01, sector 6674
Directory sread (sector 0x1a12) failed
I/O error: dev 08:01, sector 6674
Directory sread (sector 0x1a12) failed
I/O error: dev 08:01, sector 6674
Directory sread (sector 0x1a12) failed
I/O error: dev 08:01, sector 6674
Directory sread (sector 0x1a12) failed
I/O error: dev 08:01, sector 6674
Directory sread (sector 0x1a12) failed
I/O error: dev 08:01, sector 6674
Directory sread (sector 0x1a12) failed
I/O error: dev 08:01, sector 6674
Directory sread (sector 0x1a12) failed
I/O error: dev 08:01, sector 6674
Directory sread (sector 0x1a12) failed
I/O error: dev 08:01, sector 6674
Directory sread (sector 0x1a12) failed
I/O error: dev 08:01, sector 6674
Directory sread (sector 0x1a12) failed
I/O error: dev 08:01, sector 6674
Directory sread (sector 0x1a12) failed
I/O error: dev 08:01, sector 6674
Directory sread (sector 0x1a12) failed
I/O error: dev 08:01, sector 6674
Directory sread (sector 0x1a12) failed
I/O error: dev 08:01, sector 6674
Directory sread (sector 0x1a12) failed
I/O error: dev 08:01, sector 6674
Directory sread (sector 0x1a12) failed
I/O error: dev 08:01, sector 6674
dev = 08:01, i_pos = 106786
Filesystem panic (dev 08:01).
msdos_write_inode: unable to read i-node block
File system has been set read-only
cdrom: open failed.
cdrom: open failed.
cdrom: open failed.
apm: BIOS not found.
tg3: eth0: Link is up at 1000 Mbps, full duplex.
tg3: eth0: Flow control is on for TX and on for RX.
I/O error: dev 08:01, sector 6674
dev = 08:01, i_pos = 106786
Filesystem panic (dev 08:01).
msdos_write_inode: unable to read i-node block
File system has been set read-only
tg3: eth0: Link is up at 1000 Mbps, full duplex.
tg3: eth0: Flow control is on for TX and on for RX.

root@box:~# fdisk -l /dev/sda
root@box:~# sfdisk -l /dev/sda
/dev/sda: No such device or address
sfdisk: cannot open /dev/sda for reading

root@box:~# fdisk -l /dev/sda1
root@box:~# sfdisk -l /dev/sda1
/dev/sda1: No such device or address

sfdisk: cannot open /dev/sda1 for reading
root@box:~# vi temp2.txt
root@box:~# vi temp2.txt

root@box:~# df -k
Filesystem 1k-blocks Used Available Use% Mounted on
/dev/ram0 3067 603 2464 20% /
/dev/sda1 63731 48085 15646 75% /cdrom
/dev/cloop 119058 119058 0 100% /KNOPPIX
/ramdisk 1016636 2132 1014504 0% /ramdisk

It also let's me get into /mnt, and sda2, but it shows it is mounted on / I don't understand this.

Code Sample

root@box:/mnt# ls -al
drwxr-xr-x 10 root root 1024 Jul 1 14:11 .
drwxr-xr-x 13 root root 1024 Jul 1 14:11 ..
drwxr-xr-x 4 root root 1024 Jul 1 14:11 auto
lrwxrwxrwx 1 root root 15 Jul 1 14:11 cdrom -> /mnt/auto/cdrom
lrwxrwxrwx 1 root root 16 Jul 1 14:11 floppy -> /mnt/auto/floppy
drwxr-xr-x 2 root root 1024 Jul 1 10:09 hd
drwxr-xr-x 2 root root 1024 Jul 1 14:11 hda1
drwxr-xr-x 2 root root 1024 Jul 1 14:11 pts
drwxr-xr-x 2 root root 1024 Jul 1 14:11 sda1
drwxr-xr-x 2 root root 1024 Jul 1 14:11 sda2
drwxr-xr-x 2 root root 1024 Jul 1 14:11 sys
drwxr-xr-x 2 root root 1024 Jul 1 10:09 test
root@box:/mnt# cd sda2
root@box:/mnt/sda2# ls
root@box:/mnt/sda2# ls -al
drwxr-xr-x 2 root root 1024 Jul 1 14:11 .
drwxr-xr-x 10 root root 1024 Jul 1 14:11 ..
root@box:/mnt/sda2# df -k .
Filesystem 1k-blocks Used Available Use% Mounted on
/dev/ram0 3067 603 2464 20% /

2 replies since July 01 2005,18:38

< Next Oldest | Next Newest >

[ Track this topic :: Email this topic :: Print this topic ]

Damn Small Linux Board » Damn Small Linux » USB booting » mounting /dev/sda2