Results 1 to 10 of 11
One of my disks pulled a Houdini (vanished).
We had an electrical storm last night. The computer was off, but it was plugged in.
It has 3 disks, each has ...
- 05-05-2009 #1Linux User
- Join Date
- Apr 2007
- Posts
- 289
Missing disk...
One of my disks pulled a Houdini (vanished).
We had an electrical storm last night. The computer was off, but it was plugged in.
It has 3 disks, each has OS's on it. 2 will boot, but the 3rd "does not exist", says GRUBloader.
If the machine powered off without proper dismount, would this be the result? How would I fix this?
Below is hardware, RED highlight is the question...
Code:chucknb@chucknb-desktop:~$ lshw WARNING: you should run this program as super-user. chucknb-desktop description: Computer width: 32 bits *-core description: Motherboard physical id: 0 *-memory description: System memory physical id: 0 size: 1011MiB *-cpu product: AMD Sempron(tm) vendor: Advanced Micro Devices [AMD] physical id: 1 bus info: cpu@0 version: 6.8.1 size: 1050MHz width: 32 bits capabilities: fpu fpu_exception wp vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 mmx fxsr sse syscall mp mmxext 3dnowext 3dnow up ts *-cache:0 description: L1 cache physical id: 0 size: 128KiB *-cache:1 description: L2 cache physical id: 1 size: 256KiB *-pci description: Host bridge product: nForce2 IGP2 vendor: nVidia Corporation physical id: 100 bus info: pci@0000:00:00.0 version: c1 width: 32 bits clock: 66MHz configuration: driver=agpgart-nvidia module=nvidia_agp *-memory:0 UNCLAIMED description: RAM memory product: nForce2 Memory Controller 0 vendor: nVidia Corporation physical id: 0.1 bus info: pci@0000:00:00.1 version: c1 width: 32 bits clock: 66MHz (15.2ns) configuration: latency=0 *-memory:1 UNCLAIMED description: RAM memory product: nForce2 Memory Controller 4 vendor: nVidia Corporation physical id: 0.2 bus info: pci@0000:00:00.2 version: c1 width: 32 bits clock: 66MHz (15.2ns) configuration: latency=0 *-memory:2 UNCLAIMED description: RAM memory product: nForce2 Memory Controller 3 vendor: nVidia Corporation physical id: 0.3 bus info: pci@0000:00:00.3 version: c1 width: 32 bits clock: 66MHz (15.2ns) configuration: latency=0 *-memory:3 UNCLAIMED description: RAM memory product: nForce2 Memory Controller 2 vendor: nVidia Corporation physical id: 0.4 bus info: pci@0000:00:00.4 version: c1 width: 32 bits clock: 66MHz (15.2ns) configuration: latency=0 *-memory:4 UNCLAIMED description: RAM memory product: nForce2 Memory Controller 5 vendor: nVidia Corporation physical id: 0.5 bus info: pci@0000:00:00.5 version: c1 width: 32 bits clock: 66MHz (15.2ns) configuration: latency=0 *-isa description: ISA bridge product: nForce2 ISA Bridge vendor: nVidia Corporation physical id: 1 bus info: pci@0000:00:01.0 version: a4 width: 32 bits clock: 66MHz capabilities: isa bus_master cap_list configuration: latency=0 *-serial description: SMBus product: nForce2 SMBus (MCP) vendor: nVidia Corporation physical id: 1.1 bus info: pci@0000:00:01.1 version: a2 width: 32 bits clock: 66MHz capabilities: cap_list configuration: driver=nForce2_smbus latency=0 maxlatency=1 mingnt=3 module=i2c_nforce2 *-usb:0 description: USB Controller product: nForce2 USB Controller vendor: nVidia Corporation physical id: 2 bus info: pci@0000:00:02.0 version: a4 width: 32 bits clock: 66MHz capabilities: ohci bus_master cap_list configuration: driver=ohci_hcd latency=0 maxlatency=1 mingnt=3 module=ohci_hcd *-usb:1 description: USB Controller product: nForce2 USB Controller vendor: nVidia Corporation physical id: 2.1 bus info: pci@0000:00:02.1 version: a4 width: 32 bits clock: 66MHz capabilities: ohci bus_master cap_list configuration: driver=ohci_hcd latency=0 maxlatency=1 mingnt=3 module=ohci_hcd *-usb:2 description: USB Controller product: nForce2 USB Controller vendor: nVidia Corporation physical id: 2.2 bus info: pci@0000:00:02.2 version: a4 width: 32 bits clock: 66MHz capabilities: ehci bus_master cap_list configuration: driver=ehci_hcd latency=0 maxlatency=1 mingnt=3 module=ehci_hcd *-network description: Ethernet interface product: nForce2 Ethernet Controller vendor: nVidia Corporation physical id: 4 bus info: pci@0000:00:04.0 logical name: eth0 version: a1 serial: 00:e0:4c:ba:36:9f width: 32 bits clock: 66MHz capabilities: bus_master cap_list ethernet physical configuration: broadcast=yes driver=forcedeth driverversion=0.61 latency=0 maxlatency=20 mingnt=1 module=forcedeth multicast=yes *-multimedia description: Multimedia audio controller product: nForce2 AC97 Audio Controler (MCP) vendor: nVidia Corporation physical id: 6 bus info: pci@0000:00:06.0 version: a1 width: 32 bits clock: 66MHz capabilities: bus_master cap_list configuration: driver=Intel ICH latency=0 maxlatency=5 mingnt=2 module=snd_intel8x0 *-pci:0 description: PCI bridge product: nForce2 External PCI Bridge vendor: nVidia Corporation physical id: 8 bus info: pci@0000:00:08.0 version: a3 width: 32 bits clock: 66MHz capabilities: pci normal_decode bus_master *-storage THE MISSING DISK IS ON THIS CARD description: RAID bus controller product: PCI0680 Ultra ATA-133 Host Controller vendor: Silicon Image, Inc. physical id: 8 bus info: pci@0000:01:08.0 version: 02 width: 32 bits clock: 33MHz capabilities: storage bus_master cap_list configuration: driver=pata_sil680 latency=32 module=pata_sil680 *-network description: Wireless interface product: AR2413 802.11bg NIC vendor: Atheros Communications Inc. physical id: a bus info: pci@0000:01:0a.0 logical name: wifi0 version: 01 serial: 00:14:78:ed:a5:b7 width: 32 bits clock: 33MHz capabilities: bus_master cap_list logical ethernet physical wireless configuration: broadcast=yes driver=ath_pci ip=192.168.0.103 latency=168 maxlatency=28 mingnt=10 module=ath_pci multicast=yes wireless=IEEE 802.11g *-ide description: IDE interface product: nForce2 IDE vendor: nVidia Corporation physical id: 9 bus info: pci@0000:00:09.0 logical name: scsi2 version: a2 width: 32 bits clock: 66MHz capabilities: ide bus_master cap_list emulated configuration: driver=pata_amd latency=0 maxlatency=1 mingnt=3 module=pata_amd *-cdrom:0 description: CD-R/CD-RW writer product: CR-4804TE vendor: MITSUMI physical id: 0.0.0 bus info: scsi@2:0.0.0 logical name: /dev/cdrom2 logical name: /dev/scd0 logical name: /dev/sr0 version: 2.6C serial: [MITSUMI CR-4804TE 2.6C capabilities: removable audio cd-r cd-rw configuration: ansiversion=5 status=open *-cdrom:1 description: DVD reader product: DVD D DH16D2P vendor: ATAPI physical id: 0.1.0 bus info: scsi@2:0.1.0 logical name: /dev/scd1 logical name: /dev/sr1 version: HP55 capabilities: removable audio dvd configuration: ansiversion=5 status=open *-pci:1 description: PCI bridge product: nForce2 AGP vendor: nVidia Corporation physical id: 1e bus info: pci@0000:00:1e.0 version: c1 width: 32 bits clock: 66MHz capabilities: pci normal_decode bus_master *-display description: VGA compatible controller product: NV20 [GeForce3 Ti 500] vendor: nVidia Corporation physical id: 0 bus info: pci@0000:02:00.0 version: a3 width: 32 bits clock: 66MHz capabilities: vga_controller bus_master cap_list configuration: driver=nvidia latency=248 maxlatency=1 mingnt=5 module=nvidia *-scsi physical id: 1 bus info: scsi@4 logical name: scsi4 capabilities: scsi-host configuration: driver=usb-storage chucknb@chucknb-desktop:~$
- 05-05-2009 #2Linux Guru
- Join Date
- Nov 2007
- Posts
- 1,695
No. "Dismount" is a filesystem operation (data) and has nothing to do with the physical operation/status of the HDD. If the drive doesn't show up in a HW or BIOS scan, it's toast.
Originally Posted by buccaneere 
- 05-05-2009 #3Linux User
- Join Date
- Apr 2007
- Posts
- 289
BIOS scan? Is this a function of BIOS [setup] configuration? Or a function of GRUB?
EDIT:
I've never seen it in BIOS, it's on a Raidbus (PCI) card. It's not on Primary IDE master or slave, or secondary IDE master or slave.
- 05-05-2009 #4Linux Guru
- Join Date
- Nov 2007
- Posts
- 1,695
- 05-05-2009 #5Linux User
- Join Date
- Apr 2007
- Posts
- 289
Other post edited...
EDIT:
I've never seen it in BIOS, it's on a Raidbus (PCI) card. It's not on Primary IDE master or slave, or secondary IDE master or slave.
- 05-05-2009 #6Linux Guru
- Join Date
- Nov 2007
- Posts
- 1,695
Nearly any bootable card will post following the motherboard's BIOS initialization - I have never seen one that doesn't. Most also have an option to enter the configuration menu for the card as well during initialization.
Google is your friend.
Silicon Image 0680 Docs
From "medley manual:"
This indicates that the card does post and does show up following the motherboard's BIOS routines.Creating and deleting RAID sets is a function found in the BIOS. During bootup, the following message
will appear, pausing for a few moments to allow the user to choose what to do:
Press F3 to enter RAID utility
- 05-05-2009 #7Linux User
- Join Date
- Apr 2007
- Posts
- 289
Raid function IS recognized, so card is recognized.
Now, I've pulled the disk, plugged it into an external USB enclosure, powered up, and the disk spun up. Plugged it into another machine, powered THAT machine up, and the GRUB menu from the EXTERNAL disk displayed.
SO, since the RAID function was recognized on the other machine, it is either a faulty molex connector (PSU), OR, a bad IDE cable).
No testing besides switching parts, I presume...
- 05-05-2009 #8Linux User
- Join Date
- Apr 2007
- Posts
- 289
Yup - just like Houdini - it's re-appeared again in the original machine.
Plugged it back in, and GRUB loaded up like nothin' ever was wrong.
- 05-05-2009 #9Linux Guru
- Join Date
- Nov 2007
- Posts
- 1,695
Many "wierd" things can happen electrically.
It could be that the card is failing, it could be that the HDD is failing, or it could be a random strange event and it runs fine for years to come.
I would watch the messages file for any HW messages and turn on the SMART daemon to make sure the HDD is monitored.
- 05-05-2009 #10Linux Guru
- Join Date
- Apr 2009
- Location
- I can be found either 40 miles west of Chicago, or in a galaxy far, far away.
- Posts
- 8,974
Something similar happened to me this weekend. We had a lengthy power failure and after some time my UPS shut off, resulting in a hard power down of the system, while I was in the process of shutting it down rationally of course. Fortunately, the damage to the file systems was repairable, but for some reason the USB hub in one of my monitors got toasted. I had to spend about 3 hours on the line with Dell to convince them that the USB hub was indeed toast and they need to send me a new monitor (it's still under warranty, fortunately). I'm thinking of sending them a bill for wasting my time...
Sometimes, real fast is almost as good as real time.
Just remember, Semper Gumbi - always be flexible!
Reply With Quote 
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts