[SLL] unable to mount old drive when it's secondary
Ana
christiana at hipointcoffee.com
Thu Oct 18 13:11:54 PDT 2007
On Thu, Oct 18, 2007 at 10:45:21AM -0700, Rob Smith wrote:
> On 10/18/07, Ana <christiana at hipointcoffee.com> wrote:
> > root at betty:/# mount -t ext3 /dev/sdb1 /mnt
> > mount: /dev/sdb1 already mounted or /mnt busy
> > root at betty:/# cat /proc/mounts | grep sdb
> > root at betty:/# lsof -n | grep mnt
> > root at betty:/#
> <SNIP>
> > It occurred to me today that my old drive is SATA-1 and my new drive is
> > SATA-2. dmesg indicates that the kernel recognizes this and seems to
> > initialize each properly. I wonder though, when SATA-2 is being used as
> > the primary drive (with the 3Gb speeds), is it problematic to mount a
> > partition on a SATA-1 at a necessarily slower speed? Is this a known
> > limitation or bug? Perhaps my hardware is somehow unusual?
> >
> > I have 6 SATA sockets on this new main-board. One thing I haven't tried
> > is plugging the two drives into slots that are very distant from one
> > another. dmesg suggests that the 6 might be grouped in 2's... so maybe
> > three SATA controllers for 6 slots? I'll try plugging the slower drive
> > into the last slot to see if that changes anything, tomorrow.
>
> check /etc/mtab?
nothing
root at betty:~# grep sdb /etc/mtab
root at betty:~#
>
> Mixing sata-1 and 2 is fine, I do it all the time.
>
> lspci is how you would show the number of sata controlers, and
> typially it will only be one, with three channels of two drives each
> channel.
good thinking. This looks like 3 controllers to me but I don't really
know how to tell the difference. There are 3 interrupts involved. I
would think one interrupt per controller, but maybe it's one interrupt
per channel.
00:0d.0 IDE interface: nVidia Corporation MCP55 SATA Controller (rev a2) (prog-if 85 [Master SecO PriO])
Subsystem: Foxconn International, Inc. Unknown device 0d06
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 0 (750ns min, 250ns max)
Interrupt: pin A routed to IRQ 21
Region 0: I/O ports at 09f0 [size=8]
Region 1: I/O ports at 0bf0 [size=4]
Region 2: I/O ports at 0970 [size=8]
Region 3: I/O ports at 0b70 [size=4]
Region 4: I/O ports at dc00 [size=16]
Region 5: Memory at dfffd000 (32-bit, non-prefetchable) [size=4K]
Capabilities: [44] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [b0] Message Signalled Interrupts: Mask- 64bit+ Queue=0/2 Enable-
Address: 0000000000000000 Data: 0000
Capabilities: [cc] HyperTransport: MSI Mapping
00:0d.1 IDE interface: nVidia Corporation MCP55 SATA Controller (rev a2) (prog-if 85 [Master SecO PriO])
Subsystem: Foxconn International, Inc. Unknown device 0d06
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 0 (750ns min, 250ns max)
Interrupt: pin B routed to IRQ 20
Region 0: I/O ports at 09e0 [size=8]
Region 1: I/O ports at 0be0 [size=4]
Region 2: I/O ports at 0960 [size=8]
Region 3: I/O ports at 0b60 [size=4]
Region 4: I/O ports at c800 [size=16]
Region 5: Memory at dfffc000 (32-bit, non-prefetchable) [size=4K]
Capabilities: [44] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [b0] Message Signalled Interrupts: Mask- 64bit+ Queue=0/2 Enable-
Address: 0000000000000000 Data: 0000
Capabilities: [cc] HyperTransport: MSI Mapping
00:0d.2 IDE interface: nVidia Corporation MCP55 SATA Controller (rev a2) (prog-if 85 [Master SecO PriO])
Subsystem: Foxconn International, Inc. Unknown device 0d06
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 0 (750ns min, 250ns max)
Interrupt: pin C routed to IRQ 23
Region 0: I/O ports at c400 [size=8]
Region 1: I/O ports at c000 [size=4]
Region 2: I/O ports at bc00 [size=8]
Region 3: I/O ports at b800 [size=4]
Region 4: I/O ports at b400 [size=16]
Region 5: Memory at dfffb000 (32-bit, non-prefetchable) [size=4K]
Capabilities: [44] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [b0] Message Signalled Interrupts: Mask- 64bit+ Queue=0/2 Enable-
Address: 0000000000000000 Data: 0000
Capabilities: [cc] HyperTransport: MSI Mapping
> if your drive is hot swap safe, I'd boot up and then plug in the drive
> and see if I could mount it then. That would prevent any boot-time
> weirdness from screwing with things.
After doing a little research, I think it is hot swap safe. I've never
pulled a plug from an operating device before so this makes me a little
nervous. I will try it though.
- Ana
More information about the linux-list
mailing list