[SOLVED]New drive not showing up

[WhateverFits]

My system crashed and I'm starting over with a new drive. I added a new extra drive for storage in my core and I think I may have hit "Ignore this device every time" on it since I had a slew of those notifications because it detected every non-MD system on the network and attempted adding all their drives too at the same time. So, I'm pretty sure it is my fault. Anyone know how to un-ignore this device? I looked in the MySQL tables and nothing stood out at me and I didn't find anything in the interface.  If not, how do I best add this device?

Thanks!

[tschak909]

You will need to go to the web admin, Advanced > Configuration > Unknown devices, find your device in the list, click unlock. You'll then want to DELETE FROM PnpQueue; if you want the pnp subsystem to figure this out, faster.. Reload router.

-Thom

[WhateverFits]

Thanks Thom! Helpful as always. I'll try it tomorrow and see if I can get it to work.

[WhateverFits]

Still not showing up. The device is virtualized on vSphere (probably the problem) and I'm trying to debug this. I added a second disk to see if I can find the problem. I have a bunch of entries like the following:

Code:

|        3978 | 2013-03-17 17:30:05 |               |      |           |            |          | aa193b52-d3bb-46be-82aa-3153e6d1b73b |             8 |              0 |              1790 |                 0 |                  1 |           |       0 |    10 |         1 | 267|aa193b52-d3bb-46be-82aa-3153e6d1b73b|277|696.54 GB | 696.54 GB [sdc1] Virtual_disk on dcerouter |   NULL |      NULL |     NULL |          0 | 2013-03-17 17:30:05 |         NULL |
|        3979 | 2013-03-17 17:40:05 |               |      |           |            |          | aa193b52-d3bb-46be-82aa-3153e6d1b73b |             8 |              0 |              1790 |                 0 |                  1 |           |       0 |    10 |         1 | 267|aa193b52-d3bb-46be-82aa-3153e6d1b73b|277|696.54 GB | 696.54 GB [sdc1] Virtual_disk on dcerouter |   NULL |      NULL |     NULL |          0 | 2013-03-17 17:40:05 |         NULL |

So, is scan_drives.sh used for scanning drives? If so, what calls that? If not, what does this type of scan? I'm trying to dig in and fix whatever is this problem. If it is the virtualization, then I'll try a different method. I'll see what I can figure out but I can't find the entry point of this scan just yet.


Thanks1

[tschak909]

is the share showing up on the 192.168.80.0 network?

-Thom

[WhateverFits]

It is a new disk installed into the core machine. It shows up as local disk /dev/sdc1 and is a fresh mkfs.ext4 drive. I just don't see anything wrong but that it won't show up. The original disk is mounted currently (I needed the space) but the new one is in pristine condition as I've done nothing with it yet but attempt to debug why it isn't showing itself.

[tschak909]

Did the device somehow wind up on the Unlock Devices page? (it is there by uuid).

Also, you may want to see the output of the StorageDevices_*Radar.sh scripts after running set -x

-Thom

[WhateverFits]

Nothing is showing up in the Unlock Devices page. This is absolutely something to do with the virtualized drives, I'm sure of it now. It was working previously before my drive got corrupted and I lost all of my configurations for my LMCE virtual images. Yeah, that was fun.

So, the current state as of late last night when I gave up and went to bed: I got rid of the virtual drives and mapped drives directly in. Now they no longer show up as "Virtual Disk" inside the PnpQueue rather they show real hard drive details and they get added! Yeah! Well, almost a yeah. The drives get added automatically and the process continues as usual until the drives go to get mounted. /mnt/device/71 fails with "Cannot find hal object with..." and exits due to weirdness in the partitions. The volumes have no UUID, serial, or label. I'm working on tracking this down right now. I hacked up the auto.PlutoStorageDevices to get it to work but the data on these drives doesn't show up in the orbiters. It is cataloged properly and works if I search by name but I cannot browse it. I'm looking into why the partition has no details (the drive does).

Questions: Do you want me to try and figure out why the virtualized drive detection doesn't work? Is that something worth fixing? If so, I'll track that down. Any idea why it wouldn't show up to browse in an orbiter?

[tschak909]

Are your virtualized drives showing up as /dev/sdX?

-Thom

[WhateverFits]

Yes, they are. I just found out that tune2fs has

Code:

Filesystem volume name:   BOB
Last mounted on:          /mnt/device/72
Filesystem UUID:          995013e8-c86d-453c-af46-800c73eb2167

and lshal has:

Code:

  block.device = '/dev/sdc1'  (string)
  volume.label = ''  (string)
  volume.uuid = ''  (string)

OK, so something is wrong with my HAL. I'm sorry Dave, I'm afraid I can't do that.

I just restarted the hald and all my information is showing back up. Really strange. OK, at least I know what is causing that one.

I still don't know why these drives aren't showing up in the orbiters.

[WhateverFits]

Once I reset the hald, everything started filtering into place. At least I learned more about the system by doing this. Thanks for all the help Thom!