LinuxQuestions.org
Support LQ: Use code LQ3 and save $3 on Domain Registration
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - General
User Name
Password
Linux - General This Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.

Notices

Reply
 
Search this Thread
Old 04-28-2011, 06:23 PM   #1
XXLRay
Member
 
Registered: May 2010
Posts: 126

Rep: Reputation: 16
Devices lost after Ubuntu installation


After I managed to crash my Debian on a version upgrade and failed to reinstall it by the netinstall CD I decided to switch to Ubuntu on my (old) fileserver.
Unfortunately some of the disks can not be mounted:
Code:
$ sudo mount -a
mount: special device /dev/sdb1 does not exist
mount: special device /dev/sdc1 does not exist
mount: special device /dev/sdd1 does not exist
My fstab:
Code:
$ cat /etc/fstab 
proc            /proc           proc    nodev,noexec,nosuid 0       0
########################
# Onboard IDE          #
########################
# slash
UUID=07b14e4b-af09-43a3-83b2-f504447dbd06 /               ext4    errors=remount-ro 0       1
# swap
UUID=99beaf05-bc67-4be5-a19a-9a2f0ef2b7d7 none            swap    sw              0       0

########################
# Promise Fasttrack100 #
########################
# Maxtor 6Y120L0 120GB - bucket
/dev/sdb1 /media/bucket reiserfs defaults 0 0
# IBM-DTLA-305040 40GB - plop ?
/dev/sdc1 /media/plop reiserfs defaults 0 0
# WDC WD600AB-00CBA1 60GB - plain
/dev/sdd1 /media/plain reiserfs defaults 0 0
# ST380021A 80GB - data
UUID=993bec4d-3cf2-464b-808d-c517a824f949 /media/data reiserfs defaults 0 0

########################
# Promise Ultra100TX2  #
########################
# WDC WD2000JB-00KFA0 200GB - video
UUID=639e6b95-2cf5-4dab-98f0-5679171fbf38 /media/video reiserfs defaults 0 0
# Samsung SP2014N 200GB - share
UUID=c21025b9-dfdf-45ce-a569-9dd6f0f534b8 /media/share reiserfs defaults 0 0
# IBM-DTLA-305040 40GB - temp
UUID=00d88220-3655-4ae5-a76a-af58b3db7eee /media/temp reiserfs defaults 0 0
# IC35L040AVER07-0 40GB - space
Logs:
Code:
$ dmesg
...
[    2.520173] sd 2:0:0:0: [sdb] 240121728 512-byte logical blocks: (122 GB/114 GiB)
[    2.520608] sd 2:0:0:0: [sdb] Write Protect is off
[    2.520620] sd 2:0:0:0: [sdb] Mode Sense: 00 3a 00 00
[    2.520778] sd 2:0:1:0: [sdc] 80418240 512-byte logical blocks: (41.1 GB/38.3 GiB)
[    2.520804] sd 2:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[    2.520972] sd 2:0:1:0: [sdc] Write Protect is off
[    2.520982] sd 2:0:1:0: [sdc] Mode Sense: 00 3a 00 00
[    2.521060] sd 2:0:1:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
...
Device folder:
Code:
~$ ls /dev/sd*
/dev/sda
/dev/sda1
/dev/sda2  
/dev/sdb  
/dev/sdc  
/dev/sdd  
/dev/sde  
/dev/sdf  
/dev/sdf1  
/dev/sdg  
/dev/sdg1  
/dev/sdh  
/dev/sdh1
I tried to recreate the devices by:
Code:
cd /dev
sudo MAKEDEV sdb
sudo MAKEDEV sdc
sudo MAKEDEV sdd
And even manually:
Code:
$ sudo mknod /dev/sdb1 b 8 17
$ sudo mknod /dev/sdc1 b 8 33
$ sudo mknod /dev/sdd1 b 8 4
Both throw up the following error:
Code:
$ sudo mount -a
mount: /dev/sdb1 already mounted or /media/bucket busy
mount: /dev/sdc1 already mounted or /media/plop busy
mount: /dev/sdd1 already mounted or /media/plain busy
The UUIDs:
Code:
$ sudo blkid
/dev/sda1: LABEL="slash" UUID="07b14e4b-af09-43a3-83b2-f504447dbd06" TYPE="ext4" 
/dev/sda2: UUID="99beaf05-bc67-4be5-a19a-9a2f0ef2b7d7" TYPE="swap" 
/dev/sdf1: UUID="639e6b95-2cf5-4dab-98f0-5679171fbf38" TYPE="reiserfs" 
/dev/sdg1: UUID="c21025b9-dfdf-45ce-a569-9dd6f0f534b8" TYPE="reiserfs" 
/dev/sdh1: UUID="00d88220-3655-4ae5-a76a-af58b3db7eee" TYPE="reiserfs" 
/dev/sdb: TYPE="promise_fasttrack_raid_member" 
/dev/sdc: TYPE="promise_fasttrack_raid_member" 
/dev/sdd: TYPE="promise_fasttrack_raid_member" 
/dev/sde: TYPE="promise_fasttrack_raid_member" 
/dev/mapper/pdc_gcdjbfhd1: UUID="993bec4d-3cf2-464b-808d-c517a824f949" TYPE="reiserfs"

The operating system hard disk is connected to the onboard IDE controller all other disks are connected to two PCI IDE controllers. All disks are accessed separately no hardware RAID is set up. The configuration worked on my old Debian system.

Any ideas or suggestions?

My system:
Code:
$ uname -r && cat /etc/issue
2.6.38-8-generic
Ubuntu 11.04
 
Old 04-28-2011, 07:43 PM   #2
T3RM1NVT0R
Senior Member
 
Registered: Dec 2010
Location: Internet
Distribution: Linux Mint, Ubuntu, SLES, CentOS
Posts: 1,790

Rep: Reputation: 324Reputation: 324Reputation: 324Reputation: 324
@ Reply

Hi there,

Please paste the output of fdisk -l

Also did you try mounting the devices that you have created manually on any other folder other than /media

Also try the following:

1. Rem out the entries related to dev/sdb1, /dev/sdc1 and /dev/sdd1 from /etc/fstab
2. Reboot the system.
3. Try to mount dev/sdb1, /dev/sdc1 and /dev/sdd1
4. Paste the output of df -h here in this thread.

Note:Take a backup of your /etc/fstab before making any changes.
 
Old 04-29-2011, 02:08 AM   #3
XXLRay
Member
 
Registered: May 2010
Posts: 126

Original Poster
Rep: Reputation: 16
fdisk output (note that the order has changed - the functional disks are sdb1, sdc1 and sdd1 now the trouble disks are labled sde1, sdf1, sdg1 and sdh1):
Code:
$ sudo fdisk -l

Disk /dev/sda: 4311 MB, 4311982080 bytes
255 heads, 63 sectors/track, 524 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x7a36d966

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *           1         365     2931831   83  Linux
/dev/sda2             366         525     1277952   82  Linux swap / Solaris
Partition 2 does not end on cylinder boundary.

Disk /dev/sdb: 200.0 GB, 200049647616 bytes
255 heads, 63 sectors/track, 24321 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1               1       24321   195358401   83  Linux

Disk /dev/sdc: 200.0 GB, 200049647616 bytes
255 heads, 63 sectors/track, 24321 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

   Device Boot      Start         End      Blocks   Id  System
/dev/sdc1               1       24321   195358401   83  Linux

Disk /dev/sdd: 41.2 GB, 41174138880 bytes
16 heads, 63 sectors/track, 79780 cylinders
Units = cylinders of 1008 * 512 = 516096 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

   Device Boot      Start         End      Blocks   Id  System
/dev/sdd1               1       79780    40209088+  83  Linux

Disk /dev/sde: 122.9 GB, 122942324736 bytes
16 heads, 63 sectors/track, 238216 cylinders
Units = cylinders of 1008 * 512 = 516096 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

   Device Boot      Start         End      Blocks   Id  System
/dev/sde1               1      238216   120060832+  83  Linux

Disk /dev/sdf: 41.2 GB, 41174138880 bytes
16 heads, 63 sectors/track, 79780 cylinders
Units = cylinders of 1008 * 512 = 516096 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

   Device Boot      Start         End      Blocks   Id  System
/dev/sdf1               1       79780    40209088+  83  Linux

Disk /dev/sdg: 60.0 GB, 60022480896 bytes
16 heads, 63 sectors/track, 116301 cylinders
Units = cylinders of 1008 * 512 = 516096 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

   Device Boot      Start         End      Blocks   Id  System
/dev/sdg1   *           1      116301    58615672+  83  Linux

Disk /dev/sdh: 80.0 GB, 80026361856 bytes
255 heads, 63 sectors/track, 9729 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

   Device Boot      Start         End      Blocks   Id  System
/dev/sdh1               1        9729    78148161   83  Linux

Disk /dev/dm-0: 122.9 GB, 122942292480 bytes
16 heads, 63 sectors/track, 238215 cylinders
Units = cylinders of 1008 * 512 = 516096 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

     Device Boot      Start         End      Blocks   Id  System
/dev/dm-0p1               1      238216   120060832+  83  Linux

Disk /dev/dm-2: 80.0 GB, 80026329600 bytes
255 heads, 63 sectors/track, 9729 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

     Device Boot      Start         End      Blocks   Id  System
/dev/dm-2p1               1        9729    78148161   83  Linux

Disk /dev/dm-1: 60.0 GB, 60022448640 bytes
16 heads, 63 sectors/track, 116300 cylinders
Units = cylinders of 1008 * 512 = 516096 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

     Device Boot      Start         End      Blocks   Id  System
/dev/dm-1p1   *           1      116301    58615672+  83  Linux

Disk /dev/dm-4: 80.0 GB, 80023716864 bytes
255 heads, 63 sectors/track, 9728 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

Disk /dev/dm-4 doesn't contain a valid partition table

Disk /dev/dm-3: 41.2 GB, 41174106624 bytes
16 heads, 63 sectors/track, 79779 cylinders
Units = cylinders of 1008 * 512 = 516096 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

     Device Boot      Start         End      Blocks   Id  System
/dev/dm-3p1               1       79780    40209088+  83  Linux
A shorter overview:
Code:
$ sudo fdisk -l | grep "GB"
Disk /dev/sdb: 200.0 GB, 200049647616 bytes
Disk /dev/sdc: 200.0 GB, 200049647616 bytes
Disk /dev/sde: 122.9 GB, 122942324736 bytes
Disk /dev/sdf: 41.2 GB, 41174138880 bytes
Disk /dev/sdd: 41.2 GB, 41174138880 bytes
Disk /dev/sdg: 60.0 GB, 60022480896 bytes
Disk /dev/sdh: 80.0 GB, 80026361856 bytes
Disk /dev/dm-3: 41.2 GB, 41174106624 bytes
Disk /dev/dm-0: 122.9 GB, 122942292480 bytes
Disk /dev/dm-4 doesn't contain a valid partition table
Disk /dev/dm-2: 80.0 GB, 80026329600 bytes
Disk /dev/dm-1: 60.0 GB, 60022448640 bytes
Disk /dev/dm-4: 80.0 GB, 80023716864 bytes
sudo fdisk -l /dev/<device> gives an output for sda1, sda2, sdb1, sdc1 and sdd1 bt not for sde1, sdf1, sdg1 and sdh1.

Yes, I tried to mount the devices manually (after deletion of fstab entries and reboot):
Code:
$ cd /dev
$ sudo MAKEDEV sdh
$ mkdir /tmp/sdh1
$ sudo mount -t reiserfs /dev/sdh1 /tmp/sdh1/
mount: /dev/sdh1 already mounted or /tmp/sdh1/ busy
df output:
Code:
$ df -h
Filesystem            Size  Used Avail Use% Mounted on
/dev/sda1             2.8G  1.5G  1.2G  57% /
none                  495M  216K  494M   1% /dev
none                  501M     0  501M   0% /dev/shm
none                  501M  340K  501M   1% /var/run
none                  501M     0  501M   0% /var/lock
/dev/sdb1             187G  179G  7.7G  96% /media/video
/dev/sdc1             187G  133G   54G  72% /media/share
/dev/sdd1              39G   25G   15G  64% /media/temp
/dev/mapper/pdc_gcdjbfhd1
                       75G   74G  651M 100% /media/data
I recognized some error messages on boot:
Code:
udevd-work[149]: inotify:add_watch(6, /dev/sde, 10) failed: No such file or directory
udevd-work[87]: inotify:add_watch(6, /dev/sdh, 10) failed: No such file or directory
udevd-work[148]: inotify:add_watch(6, /dev/sdf, 10) failed: No such file or directory
udevd-work[155]: inotify:add_watch(6, /dev/sdeg 10) failed: No such file or directory

Last edited by XXLRay; 04-29-2011 at 02:15 AM. Reason: added on boot error message
 
Old 04-29-2011, 02:15 AM   #4
zhjim
Senior Member
 
Registered: Oct 2004
Distribution: Debian Squeeze x86_64
Posts: 1,467
Blog Entries: 11

Rep: Reputation: 184Reputation: 184
From a short look I'd say you don't mount a member of a raid through its own device file. Use the mapper device file. In your first post /dev/sdb - /dev/sdd are raid members, so you need the raid to be *build*/*setup*, maybe through mdadm or your raid controller should do that and then mount the appropiate /dev/mapper/raid_device_name.
 
Old 04-29-2011, 03:56 AM   #5
XXLRay
Member
 
Registered: May 2010
Posts: 126

Original Poster
Rep: Reputation: 16
Oh I never did that before. Just to be sure I do not screw anything could you please check whether the following commands looks right?:
Code:
mdadm --create /dev/md0 --level=0 --raid-devices=1 /dev/sde1
mdadm --create /dev/md1 --level=0 --raid-devices=1 /dev/sdf1
mdadm --create /dev/md2 --level=0 --raid-devices=1 /dev/sdg1
mdadm --create /dev/md3 --level=0 --raid-devices=1 /dev/sdh1
Will this persist after reboot?

Any idea why this is not needed for the other controller and why I can access a single disc on this one?
 
Old 04-29-2011, 05:27 AM   #6
zhjim
Senior Member
 
Registered: Oct 2004
Distribution: Debian Squeeze x86_64
Posts: 1,467
Blog Entries: 11

Rep: Reputation: 184Reputation: 184
I'm not so deb into mdadm but looks good from here. At least the syntax but having a raid 0 with just one drive...

Maybe a
Code:
mdadm -A
does the trick automaticly. -A stands for assemble a preexisting array (of disks). Should be the safer option to not screw up.

To be persistent check out /etc/mdadm.conf. It's the config file.
Sorry for not beeing a great help. I can assist you later the day or on sunday. Then I can also check out my raid setup with mdadm I have going on an old system.
 
Old 04-29-2011, 06:07 AM   #7
XXLRay
Member
 
Registered: May 2010
Posts: 126

Original Poster
Rep: Reputation: 16
The disks on the controller are configures as single drives. I could not find that mdadm offers such an option. Thus I chose raid 0 (stripe) with just one disk. Can anyone else comment on this? I am really frightened to loose my data as I have no chance of backing up this amount.
 
Old 04-29-2011, 07:57 AM   #8
T3RM1NVT0R
Senior Member
 
Registered: Dec 2010
Location: Internet
Distribution: Linux Mint, Ubuntu, SLES, CentOS
Posts: 1,790

Rep: Reputation: 324Reputation: 324Reputation: 324Reputation: 324
@ Reply

Not sure why you have configured RAID level 0 with 1 disk as I don't think so this will enhance or do anything good for disk I/O with one device.

Commands are fine. Did you try to check the details of every RAID configured device using:

mdadm --detail /dev/device_name (say device_name=md0 or md1 and so on you can get the list by cd /dev && ls -l md*)

Also not sure why you were trying to create a device when they were part of RAID. The only problem earlier was that you were trying to mount them as individual devices and not as a RAID devices.

As you said that you tried to re-create the device that means you were trying to re-create those devices which are already part of RAID. Keep your fingers crossed as it is quite possible that you have lost your data.

You can give a try to mount the device as a RAID device using the following command:

mount /dev/device_name where device_name will be any of the devices which says something like md0, md1 etc.
 
Old 04-29-2011, 08:14 AM   #9
XXLRay
Member
 
Registered: May 2010
Posts: 126

Original Poster
Rep: Reputation: 16
Quote:
Originally Posted by T3RM1NVT0R View Post
Not sure why you have configured RAID level 0 with 1 disk as I don't think so this will enhance or do anything good for disk I/O with one device.
...
Also not sure why you were trying to create a device when they were part of RAID. The only problem earlier was that you were trying to mount them as individual devices and not as a RAID devices.
I do not remember to have done that on purpose as in my old Debian system all disks were mounted as single devices (I still have a copy of my old fstab which did not work after the Ubuntu installation).

The idea of RAIDs just came from zhjim and I don't understand why the devices I used as single drives before now seem to be only recognized as RAIDs.

I will try to check the details when I am back home. I cannot access the server yet from here.
 
Old 04-29-2011, 09:03 AM   #10
zhjim
Senior Member
 
Registered: Oct 2004
Distribution: Debian Squeeze x86_64
Posts: 1,467
Blog Entries: 11

Rep: Reputation: 184Reputation: 184
Quote:
Originally Posted by XXLRay View Post
The UUIDs:
Code:
$ sudo blkid
/dev/sda1: LABEL="slash" UUID="07b14e4b-af09-43a3-83b2-f504447dbd06" TYPE="ext4" 
/dev/sda2: UUID="99beaf05-bc67-4be5-a19a-9a2f0ef2b7d7" TYPE="swap" 
/dev/sdf1: UUID="639e6b95-2cf5-4dab-98f0-5679171fbf38" TYPE="reiserfs" 
/dev/sdg1: UUID="c21025b9-dfdf-45ce-a569-9dd6f0f534b8" TYPE="reiserfs" 
/dev/sdh1: UUID="00d88220-3655-4ae5-a76a-af58b3db7eee" TYPE="reiserfs" 
/dev/sdb: TYPE="promise_fasttrack_raid_member" 
/dev/sdc: TYPE="promise_fasttrack_raid_member" 
/dev/sdd: TYPE="promise_fasttrack_raid_member" 
/dev/sde: TYPE="promise_fasttrack_raid_member" 
/dev/mapper/pdc_gcdjbfhd1: UUID="993bec4d-3cf2-464b-808d-c517a824f949" TYPE="reiserfs"
I came up with mdadm cause the UUIDs said raid_member. Sorry if I create inconvinience. Hopefully you did not created the array with the command you posted. I thought you set them up...
 
Old 04-29-2011, 09:14 AM   #11
T3RM1NVT0R
Senior Member
 
Registered: Dec 2010
Location: Internet
Distribution: Linux Mint, Ubuntu, SLES, CentOS
Posts: 1,790

Rep: Reputation: 324Reputation: 324Reputation: 324Reputation: 324
@ Reply

Quote:
mdadm --create /dev/md0 --level=0 --raid-devices=1 /dev/sde1
mdadm --create /dev/md1 --level=0 --raid-devices=1 /dev/sdf1
mdadm --create /dev/md2 --level=0 --raid-devices=1 /dev/sdg1
mdadm --create /dev/md3 --level=0 --raid-devices=1 /dev/sdh1
The above commands are used to set up a new RAID array with the mentioned device/devices

Basically you are instructing the system to create a new RAID array /dev/md0 with level=0 and raid-devices involved in this will be = 1 /dev/sde1 and so on. I think there is one --add option is missing in the above command because I have tested it with RedHat and it requires --add command to set up a new RAID array. Might be possible that it worked that way on Ubuntu

@ zhjim
Quote:
Hopefully you did not created the array with the command you posted. I thought you set them up..
If you are talking about the above commands then yes it is used to create new RAID array.
 
Old 04-29-2011, 09:16 AM   #12
XXLRay
Member
 
Registered: May 2010
Posts: 126

Original Poster
Rep: Reputation: 16
No I did not do anything yet but what am I supposed to do now? First ls -l /dev/md* an then do the mdadm --detail /dev/device_name check?

Can anyone explain what the /dev/mapper/pdc_gcdjbfhd1 is? I can mount it and due to the data it is one of the disks on the trouble controller.
 
Old 04-29-2011, 11:03 AM   #13
zhjim
Senior Member
 
Registered: Oct 2004
Distribution: Debian Squeeze x86_64
Posts: 1,467
Blog Entries: 11

Rep: Reputation: 184Reputation: 184
Quote:
Originally Posted by XXLRay View Post
No I did not do anything yet but what am I supposed to do now? First ls -l /dev/md* an then do the mdadm --detail /dev/device_name check?
At least the data is still there...

Quote:
Originally Posted by XXLRay View Post
Can anyone explain what the /dev/mapper/pdc_gcdjbfhd1 is? I can mount it and due to the data it is one of the disks on the trouble controller.
/dev/mapper/ normally holds substitute devices build from fake(/software) raids and logical volume manager.
So I'd say this the automatically setup raid. Does your /etc/mdadm.conf contain anything?

I guess we should look what parts of your system are to your liking and which are not. When I get it right everything after sde needs a remake. So how we go from here. I'd say something like this for the first shot
Code:
madadm -Q /dev/sde
madadm -Q /dev/sdf
....
This queries the device to see if its part of a raid. After this we know what is a raid member and what not. After that mdadm -E with all the devices to see what the superblock tells about the raid (parts).
I hope this will get us on the right track.
 
Old 04-29-2011, 11:54 AM   #14
XXLRay
Member
 
Registered: May 2010
Posts: 126

Original Poster
Rep: Reputation: 16
Hmm:
Code:
$ sudo mdadm -Q /dev/sde 
/dev/sde: is not an md array
$ sudo mdadm -Q /dev/sdf
/dev/sdf: is not an md array
$ sudo mdadm -Q /dev/sdg
/dev/sdg: is not an md array
$ sudo mdadm -Q /dev/sdh
This somehow seems to destroy our ideas...
 
Old 04-29-2011, 01:12 PM   #15
T3RM1NVT0R
Senior Member
 
Registered: Dec 2010
Location: Internet
Distribution: Linux Mint, Ubuntu, SLES, CentOS
Posts: 1,790

Rep: Reputation: 324Reputation: 324Reputation: 324Reputation: 324
@ Reply

Quote:
$ sudo mdadm -Q /dev/sde
/dev/sde: is not an md array
$ sudo mdadm -Q /dev/sdf
/dev/sdf: is not an md array
$ sudo mdadm -Q /dev/sdg
/dev/sdg: is not an md array
$ sudo mdadm -Q /dev/sdh
Issue is becoming more and more interesting. Let see what type of partitions are there on this devices. Do the following for each device

fdisk /dev/sde and then hit p to print the partition table. Lets see if they are Linux partitions or any of the partition is showing up as raid fastdetect.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Solo 5300 with Ubuntu 7.04 lost PCMCIA slots upon installation Smoothops Linux - Hardware 1 04-06-2008 02:42 AM
Lost USB devices SUSE 10.2 ionmich Suse/Novell 1 06-01-2007 09:04 AM
sysfs and udev lost my cdrom devices cexshun Linux - Hardware 0 09-11-2004 07:23 PM
Devices lost after kernel upgrade! Adam Shapiro Linux - Software 4 02-05-2003 07:25 AM


All times are GMT -5. The time now is 12:08 PM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration