Hvordan mounter jeg en sekundær harddisk?

jaq det er det.

i din fstab der kopierer du linierne der mounter din nuværende /dev/hda

Hvis du har samme partitioner så skal de bare være ens. mens istedet for

/dev/hda

skal der f.eks. stå

/dev/hdb / c / d / e

alt efter hvilket drev der er tale om.

husk at ændre mount punkter (f.eks. /home) til f.eks. /home2

ja det skulle ikke være noget problem ..

skriv dmesg og find ud af hvad din gamle harddisk hedder... sikkert noget med hd(a/b/c....)

så mount dem med mount -t ext2 /dev/hdb1 eller hvad partitionen hedder i /tmp

feks mount -t ext2 /dev/hdb1 /tmp

du kan se hvilke partitioner der er på disken med fdisk
fdisk /dev/hdb
p (print partition tabels
q (quit

husk at dine nuværende linier i fstab ikke må ændres.

jå sådan kan man selvf. også gøre :o)

Tak for jeres indslag. Drevet hedder HDB; men når jeg prøver at mounte den som nævnt ovenfor
med "mount -t ext2 /dev/hdb1 /tmp"
eller "mount -t ext2 /dev/hdb /tmp"
eller "mount -t ext3 /dev/hdb1 /tmp"
eller "mount -t ext3 /dev/hdb /tmp"

(Da jeg er rimelig sikker på at filsystemet er EXT3, prøvede jeg med og uden EXT3 :O)) får jeg følgende fejlmedelelse:

---

mount: wrong fs type, bad option, bad superblock on /dev/hdb,
      or too many mounted file systems
      (could this be the IDE device where you in fact use
      ide-scsi so that sr0 or sda or so is needed?)

---

Og når jeg skriver "fdisk /dev/hdb"

---

Unable to read /dev/hdb

---

Dette siger mig desværre ikke så meget, da jeg er extrem ny på Linux området (har kun haft linux i en uge nu) :O)

På forhånd mange tak for hjælpen :)

tjaae.. undgå /tmp da du muligvis bruger den allerede

# cd
# mkdir /tmp2

Prøv igen

hvis du ikke kan læse /dev/hdb med fdisk så tyder det på at der er noget galt med disken ...

dank> Jeg har prøvet det; men får samme resultat som før :(
loadet> nej, det må du da ikke side.. endnu :O)

kunne det tænkes at begge diske står som hda (eller bærer samme navne) og derfor kæmper om at få systemets "opmærksomhed"?

prøv at paste
df
og
dmesg
her

og nej jeg kan ikke forestille mig at begge diske står som hda

jeg har oplevet et par gange at en disk ikke har virket men det har været et kernel problem eller driver support for den controller den sad på ..

Jo så gerne :O)
----

df:

----

[root@ns2 /]# df
Filesystem            Size  Used Avail Use% Mounted on
/dev/hda1            5.3G  1.1G  4.1G  20% /
/dev/hda6              32G  33M  32G  1% /home
[root@ns2 /]#

----

dmesg:

----

[root@ns2 /]# dmesg
Linux version 2.4.19-16mdk (quintela@bi.mandrakesoft.com) (gcc version 3.2 (Mand
rake Linux 9.0 3.2-1mdk)) #1 Fri Sep 20 18:15:05 CEST 2002
BIOS-provided physical RAM map:
BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
BIOS-e820: 0000000000100000 - 0000000005800000 (usable)
BIOS-e820: 00000000ffff0000 - 0000000100000000 (reserved)
88MB LOWMEM available.
Advanced speculative caching feature not present
On node 0 totalpages: 22528
zone(0): 4096 pages.
zone(1): 18432 pages.
zone(2): 0 pages.
Kernel command line: BOOT_IMAGE=linux ro root=301 devfs=mount hdb=ide-scsi quiet
ide_setup: hdb=ide-scsi
No local APIC present or hardware disabled
Initializing CPU#0
Detected 233.868 MHz processor.
Console: colour dummy device 80x25
Calibrating delay loop... 466.94 BogoMIPS
Memory: 86572k/90112k available (1176k kernel code, 3152k reserved, 444k data, 1
36k init, 0k highmem)
Dentry cache hash table entries: 16384 (order: 5, 131072 bytes)
Inode cache hash table entries: 8192 (order: 4, 65536 bytes)
Mount-cache hash table entries: 2048 (order: 2, 16384 bytes)
Buffer-cache hash table entries: 4096 (order: 2, 16384 bytes)
Page-cache hash table entries: 32768 (order: 5, 131072 bytes)
CPU: Before vendor init, caps: 008001bf 00000000 00000000, vendor = 0
Intel Pentium with F0 0F bug - workaround enabled.
CPU: After vendor init, caps: 008001bf 00000000 00000000 00000000
CPU:    After generic, caps: 008001bf 00000000 00000000 00000000
CPU:            Common caps: 008001bf 00000000 00000000 00000000
CPU: Intel Pentium MMX stepping 03
Checking 'hlt' instruction... OK.
POSIX conformance testing by UNIFIX
mtrr: v1.40 (20010327) Richard Gooch (rgooch@atnf.csiro.au)
mtrr: detected mtrr type: none
PCI: PCI BIOS revision 2.10 entry at 0xfb420, last bus=0
PCI: Using configuration type 1
PCI: Probing PCI hardware
PCI: Using IRQ router PIIX [8086/7110] at 00:07.0
Limiting direct PCI/PCI transfers.
isapnp: Scanning for PnP cards...
isapnp: No Plug & Play device found
Linux NET4.0 for Linux 2.4
Based upon Swansea University Computer Society NET3.039
Initializing RT netlink socket
apm: BIOS version 1.2 Flags 0x07 (Driver version 1.16)
Starting kswapd
VFS: Diskquotas version dquot_6.5.0 initialized
devfs: v1.12a (20020514) Richard Gooch (rgooch@atnf.csiro.au)
devfs: boot_options: 0x1
vesafb: framebuffer at 0xe0000000, mapped to 0xc6002000, size 2048k
vesafb: mode is 800x600x16, linelength=1600, pages=1
vesafb: protected mode interface info at c000:4749
vesafb: scrolling: redraw
vesafb: directcolor: size=0:5:6:5, shift=0:11:5:0
Looking for splash picture.... found (800x600, 30412 bytes).
Console: switching to colour frame buffer device 80x16
fb0: VESA VGA frame buffer device
pty: 256 Unix98 ptys configured
Serial driver version 5.05c (2001-07-08) with HUB-6 MANY_PORTS MULTIPORT SHARE_I
RQ SERIAL_PCI ISAPNP enabled
ttyS00 at 0x03f8 (irq = 4) is a 16550A
ttyS01 at 0x02f8 (irq = 3) is a 16550A
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
PIIX4: IDE controller on PCI bus 00 dev 39
PIIX4: chipset revision 1
PIIX4: not 100% native mode: will probe irqs later
    ide0: BM-DMA at 0xf000-0xf007, BIOS settings: hda:DMA, hdb:DMA
    ide1: BM-DMA at 0xf008-0xf00f, BIOS settings: hdc:pio, hdd:pio
hda: WDC WD400BB-00DEA0, ATA DISK drive
hdb: ST31720A, ATA DISK drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
hda: 78165360 sectors (40021 MB) w/2048KiB Cache, CHS=4865/255/63, UDMA(33)
Partition check:
/dev/ide/host0/bus0/target0/lun0: p1 p2 < p5 p6 >
RAMDISK driver initialized: 16 RAM disks of 32000K size 1024 blocksize
md: md driver 0.90.0 MAX_MD_DEVS=256, MD_SB_DISKS=27
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP, IGMP
IP: routing cache hash table of 512 buckets, 4Kbytes
TCP: Hash tables configured (established 8192 bind 16384)
Linux IP multicast router 0.06 plus PIM-SM
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
RAMDISK: Compressed image found at block 0
Freeing initrd memory: 122k freed
VFS: Mounted root (ext2 filesystem).
Mounted devfs on /dev
Journalled Block Device driver loaded
EXT3-fs: INFO: recovery required on readonly filesystem.
EXT3-fs: write access will be enabled during recovery.
kjournald starting.  Commit interval 5 seconds
EXT3-fs: recovery complete.
EXT3-fs: mounted filesystem with ordered data mode.
Mounted devfs on /dev
Freeing unused kernel memory: 136k freed
Real Time Clock Driver v1.10e
usb.c: registered new driver usbdevfs
usb.c: registered new driver hub
usb-uhci.c: $Revision: 1.275 $ time 18:49:04 Sep 20 2002
usb-uhci.c: High bandwidth mode enabled
PCI: Found IRQ 11 for device 00:07.2
PCI: Sharing IRQ 11 with 00:14.0
usb-uhci.c: USB UHCI at I/O 0x6400, IRQ 11
usb-uhci.c: Detected 2 ports
usb.c: new USB bus registered, assigned bus number 1
hub.c: USB hub found
hub.c: 2 ports detected
usb-uhci.c: v1.275:USB Universal Host Controller Interface driver
usbdevfs: remount parameter error
EXT3 FS 2.4-0.9.17, 10 Jan 2002 on ide0(3,1), internal journal
Adding Swap: 248968k swap-space (priority -1)
SCSI subsystem driver Revision: 1.00
scsi0 : SCSI host adapter emulation for IDE ATAPI devices
hdb: status error: status=0x51 { DriveReady SeekComplete Error }
hdb: status error: error=0x04 { DriveStatusError }
ide-scsi: Strange, packet command initiated yet DRQ isn't asserted
hdb: status error: status=0x51 { DriveReady SeekComplete Error }
hdb: status error: error=0x04 { DriveStatusError }
ide-scsi: Strange, packet command initiated yet DRQ isn't asserted
hdb: status error: status=0x51 { DriveReady SeekComplete Error }
hdb: status error: error=0x04 { DriveStatusError }
ide-scsi: Strange, packet command initiated yet DRQ isn't asserted
hdb: status error: status=0x51 { DriveReady SeekComplete Error }
hdb: status error: error=0x04 { DriveStatusError }
hda: DMA disabled
hdb: DMA disabled
ide-scsi: Strange, packet command initiated yet DRQ isn't asserted
ide0: reset: success
hdb: status error: status=0x51 { DriveReady SeekComplete Error }
hdb: status error: error=0x04 { DriveStatusError }
ide-scsi: Strange, packet command initiated yet DRQ isn't asserted
hdb: status error: status=0x51 { DriveReady SeekComplete Error }
hdb: status error: error=0x04 { DriveStatusError }
ide-scsi: Strange, packet command initiated yet DRQ isn't asserted
hdb: status error: status=0x51 { DriveReady SeekComplete Error }
hdb: status error: error=0x04 { DriveStatusError }
ide-scsi: Strange, packet command initiated yet DRQ isn't asserted
hdb: status error: status=0x51 { DriveReady SeekComplete Error }
hdb: status error: error=0x04 { DriveStatusError }
ide-scsi: Strange, packet command initiated yet DRQ isn't asserted
ide0: reset: success
hdb: status error: status=0x51 { DriveReady SeekComplete Error }
hdb: status error: error=0x04 { DriveStatusError }
scsi0 channel 0 : resetting for second half of retries.
SCSI bus is being reset for host 0 channel 0.
ide-scsi: Strange, packet command initiated yet DRQ isn't asserted
hdb: status error: status=0x51 { DriveReady SeekComplete Error }
hdb: status error: error=0x04 { DriveStatusError }
ide-scsi: Strange, packet command initiated yet DRQ isn't asserted
hdb: status error: status=0x51 { DriveReady SeekComplete Error }
hdb: status error: error=0x04 { DriveStatusError }
ide-scsi: Strange, packet command initiated yet DRQ isn't asserted
hdb: status error: status=0x51 { DriveReady SeekComplete Error }
hdb: status error: error=0x04 { DriveStatusError }
ide-scsi: Strange, packet command initiated yet DRQ isn't asserted
hdb: status error: status=0x51 { DriveReady SeekComplete Error }
hdb: status error: error=0x04 { DriveStatusError }
ide-scsi: Strange, packet command initiated yet DRQ isn't asserted
ide0: reset: success
hdb: status error: status=0x51 { DriveReady SeekComplete Error }
hdb: status error: error=0x04 { DriveStatusError }
ide-scsi: Strange, packet command initiated yet DRQ isn't asserted
hdb: status error: status=0x51 { DriveReady SeekComplete Error }
hdb: status error: error=0x04 { DriveStatusError }
ide-scsi: Strange, packet command initiated yet DRQ isn't asserted
hdb: status error: status=0x51 { DriveReady SeekComplete Error }
hdb: status error: error=0x04 { DriveStatusError }
ide-scsi: Strange, packet command initiated yet DRQ isn't asserted
hdb: status error: status=0x51 { DriveReady SeekComplete Error }
hdb: status error: error=0x04 { DriveStatusError }
ide-scsi: Strange, packet command initiated yet DRQ isn't asserted
ide0: reset: success
hdb: status error: status=0x51 { DriveReady SeekComplete Error }
hdb: status error: error=0x04 { DriveStatusError }
ide-scsi: Strange, packet command initiated yet DRQ isn't asserted
hdb: status error: status=0x51 { DriveReady SeekComplete Error }
hdb: status error: error=0x04 { DriveStatusError }
ide-scsi: Strange, packet command initiated yet DRQ isn't asserted
hdb: status error: status=0x51 { DriveReady SeekComplete Error }
hdb: status error: error=0x04 { DriveStatusError }
ide-scsi: Strange, packet command initiated yet DRQ isn't asserted
hdb: status error: status=0x51 { DriveReady SeekComplete Error }
hdb: status error: error=0x04 { DriveStatusError }
ide-scsi: Strange, packet command initiated yet DRQ isn't asserted
hdb: status error: status=0x51 { DriveReady SeekComplete Error }
hdb: status error: error=0x04 { DriveStatusError }
ide-scsi: Strange, packet command initiated yet DRQ isn't asserted
ide0: reset: success
hdb: status error: status=0x51 { DriveReady SeekComplete Error }
hdb: status error: error=0x04 { DriveStatusError }
ide-scsi: Strange, packet command initiated yet DRQ isn't asserted
hdb: status error: status=0x51 { DriveReady SeekComplete Error }
hdb: status error: error=0x04 { DriveStatusError }
ide-scsi: Strange, packet command initiated yet DRQ isn't asserted
hdb: status error: status=0x51 { DriveReady SeekComplete Error }
hdb: status error: error=0x04 { DriveStatusError }
ide-scsi: Strange, packet command initiated yet DRQ isn't asserted
hdb: status error: status=0x51 { DriveReady SeekComplete Error }
hdb: status error: error=0x04 { DriveStatusError }
ide-scsi: Strange, packet command initiated yet DRQ isn't asserted
ide0: reset: success
hdb: status error: status=0x51 { DriveReady SeekComplete Error }
hdb: status error: error=0x04 { DriveStatusError }
ide-scsi: Strange, packet command initiated yet DRQ isn't asserted
kjournald starting.  Commit interval 5 seconds
EXT3 FS 2.4-0.9.17, 10 Jan 2002 on ide0(3,6), internal journal
EXT3-fs: mounted filesystem with ordered data mode.
8139too Fast Ethernet driver 0.9.25
PCI: Found IRQ 11 for device 00:14.0
PCI: Sharing IRQ 11 with 00:07.2
eth0: RealTek RTL8139 Fast Ethernet at 0xc638f000, 00:50:fc:5e:6f:38, IRQ 11
eth0:  Identified 8139 chip type 'RTL-8139C'
eth0: Setting 100mbps full-duplex based on auto-negotiated partner ability 45e1.
Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
inserting floppy driver for 2.4.19-16mdk
FDC 0 is a post-1991 82077
Splash status on console 0 changed to off
attempt to access beyond end of device
03:02: rw=0, want=2, (=0x2), limit=1
EXT3-fs: unable to read superblock
attempt to access beyond end of device
03:02: rw=0, want=2, (=0x2), limit=1
EXT2-fs: unable to read superblock
hdb : bad access: block=2, count=2
end_request: I/O error, dev 03:40 (hdb), sector 2
EXT3-fs: unable to read superblock
hdb : bad access: block=2, count=2
end_request: I/O error, dev 03:40 (hdb), sector 2
EXT2-fs: unable to read superblock
ide-floppy driver 0.99b
hdb : bad access: block=2, count=2
end_request: I/O error, dev 03:40 (hdb), sector 2
EXT2-fs: unable to read superblock
hdb : bad access: block=2, count=2
end_request: I/O error, dev 03:40 (hdb), sector 2
EXT2-fs: unable to read superblock
parport0: PC-style at 0x378 [PCSPP]
lp0: using parport0 (polling).
hdb : bad access: block=2, count=2
end_request: I/O error, dev 03:40 (hdb), sector 2
EXT3-fs: unable to read superblock
hdb : bad access: block=2, count=2
end_request: I/O error, dev 03:40 (hdb), sector 2
EXT2-fs: unable to read superblock
hdb : bad access: block=2, count=2
end_request: I/O error, dev 03:40 (hdb), sector 2
EXT3-fs: unable to read superblock
hdb : bad access: block=2, count=2
end_request: I/O error, dev 03:40 (hdb), sector 2
EXT3-fs: unable to read superblock
hdb : bad access: block=2, count=2
end_request: I/O error, dev 03:40 (hdb), sector 2
EXT2-fs: unable to read superblock
[root@ns2 /]#

Den virkede ellers fint i morges. Jeg tror vist maskinen frøs, så jeg genstartede den.. hvorefter mit dilemma startede :(

sidder hdb på en raid controller ?

nej, de sidder begge to på en almindelig IDE(33, tror jeg det er) og i PRIMARY IDE

jeg ved desværre ikke hvad det kan være så .. det eneste forslag jeg har er at lave en my kernel og se om det hjælper på det.

eller smide disken over på en anden maskine og se om den kan genkende den.

fik du nogensinde prøvet

# fdisk /dev/hdb

Quote bbrockie >

Og når jeg skriver "fdisk /dev/hdb"

---

Unable to read /dev/hdb

Jeg har desværre ikke mulighed for at smide den over i en anden maskine, da jeg kun har linux på den ene PC :(

Findes der ikke et eller andet recovery halløj til linux? Det ville godt nok være surt at miste alt mit arbejde fra /var/www/html :(
Det andet der ligger på drevet har sådan set ikke noget betydning

loadet> Hvad mener du forresten med at lave en ny kernel? Skal jeg bare installere en ny og se hvad der sker?

Jeg ser lige på en "alternativ" løsning på:
http://www.mandrakeuser.org/docs/admin/print/recov.html

Jeg skal melde tilbage hertil hvis jeg kommer videre ;)

Jeg havde ikke meget held med den side der, så jeg prøvede, hvad jeg skulle have gjort fra starten af; nemlig at fjerne den nye og så fortsætte med den gamle. Efter at have set hvad der rent faktist sker på skærmen, viste det sig at der ikke var noget galt med filsystemet, det kørte helt indtil Mandrake skulle til at starte den ene service, hvor efter den så begynder at hænge..

Det drejer sig om 'saslauthd' der godt nok kommer forbi 'OK' stadiet; men så hænger den bare derefter. Jeg kører lige nu i "Interactive Startup Mode", hvor jeg så får lov til at godkende hvilke services jeg må få lov til at starte. Jeg vil herefter forsøge at få overført filerne via netværket for derefter at vende tilbage til jer med en statusrapport :O)

Nej hvor lækkert.. det eneste der nu skulle til var 'samba restart' og så fik jeg reddet alle mine filer! :O)

Du er dog utrolig heldig bbrockie - 2 gange inden for 12 timer har du selv fundet løsningen på dit problem efter at en masse mennesker har forsøgt at hjælpe dig - kender du historien om "ulven kommer" ????

LOL.. nej den har jeg ikke hørt; men desværre så kunne jeg ikke bruge deres løsninger. Plejer dog normalt at poste mine resultater hvis jeg selv har fået løst dem, da der jo kunne være en eller anden derude med netop samme problem :O)