You are not logged in.
Ran pacman -Syu, and part of the update was to the new dmraid. After rebooting, my /dev/mapper directory only has "control" in it. I looked through these two forum posts, but I still don't have any idea where to even begin to try and fix this.
http://bbs.archlinux.org/viewtopic.php?id=57579
http://bbs.archlinux.org/viewtopic.php?id=56641
The output from dmraid -ay:
ERROR: isw: Could not find disk /dev/sdc in the metadata
ERROR: isw: Could not find disk /dev/sdb in the metadata
no raid disks
The raid array is a 500GB array that is only used for storage, so I can still boot fine. dm_mod is loaded. Everything still seems to work, with the exception of my raid array. Any kind of help would be appreciated.
Offline
Perhaps the ID for the devices has changed?
Prediction...This year will be a very odd year!
Hard work does not kill people but why risk it: Charlie Mccarthy
A man is not complete until he is married..then..he is finished.
When ALL is lost, what can be found? Even bytes get lonely for a little bit! X-ray confirms Iam spineless!
Offline
Perhaps the ID for the devices has changed?
But then shouldn't the device still be in /dev/mapper by some name, even if it is a different one?
Offline
What does
cat /proc/mdstat
return?
Got Leenucks? :: Arch: Power in simplicity :: Get Counted! Registered Linux User #392717 :: Blog thingy
Offline
What does
cat /proc/mdstat
return?
[user@computar ~]$ cat /proc/mdstat
Personalities :
unused devices: <none>
Last edited by tehfishman (2008-11-10 23:55:19)
Offline
Sorry... I was thinking about mdadm, but you're actually using dmraid...
Got Leenucks? :: Arch: Power in simplicity :: Get Counted! Registered Linux User #392717 :: Blog thingy
Offline
Try reading the Outputs from Pacman. There was a change in the way devices are named.
>>> IMPORTANT DMRAID UPGRADE NOTICE
>>> -------------------------------
>>> Version 1.0.15rc introduce a new name scheme:
>>> You need to add an additional 'p' in front of your number.
>>> e.g. <yourname><number> --> <yourname>p<number>
>>> firsthd1 --> firsthdp1
>>> Please change your bootloader and fstab accordingly.
>>>
This was the output of dmraid. So you should just change in fstab and in Grub your device name from /dev/sda1 to /dev/sdap1
Saludos
Offline
Ekmino, that's all well and good and I am aware of the change in naming scheme (I said that i read those two forum posts, one was about the change in naming). The problem is that the devices aren't being recognized (did you read my post?). Maybe the devices are being recognized and I'm being silly somehow and not seeing that they are? If so could you point it out to me?
Offline
I read your post, but took the chance that the name scheme was the problem, and didn't enter those threads.(I'm sorry for being rude). Try running cfdisk <device>, just to check if it's there. if it is paste the output of df -h.
Offline
'sokay
output from cfdisk on /dev/sdb
FATAL ERROR: Bad primary partition 0: Partition ends after end-of-disk
Press any key to exit cfdisk
output from cfdisk on /dev/sdc
Unknown partition table type
Do you wish to start with a zero table [y/N] ?
Answered that last one with N.
df -h gives
Filesystem Size Used Avail Use% Mounted on
/dev/sda3 94G 24G 65G 27% /
none 2.0G 0 2.0G 0% /dev/shm
/dev/sda1 101G 7.4G 94G 8% /mnt/xp
/dev/sda2 99G 79G 21G 80% /mnt/vista
Offline
Just to clear up any possible confusion, I should probably add that /dev/sda is my primary drive which holds my operating systems. /dev/sdb and /dev/sdc are the two drives that make up a raid 0.
Offline
Ok, I'm not liking the research I'm reading, I think you're disks are screwed. Lots of people say they have fixed the same problem with Gparted. http://gparted.sourceforge.net
Offline
Perhaps gparted will give some help?
Prediction...This year will be a very odd year!
Hard work does not kill people but why risk it: Charlie Mccarthy
A man is not complete until he is married..then..he is finished.
When ALL is lost, what can be found? Even bytes get lonely for a little bit! X-ray confirms Iam spineless!
Offline
Well, I just restarted and am now looking at my raid disk in Vista. Works fine from here. I can go try it from XP if necessary as well.
Offline
Reading and writing works flawlessly. I just started up chkdsk.
Offline
Humm, do you know if dmraid, has a config file where it sets the disk cilinders... adn etc... maybe that's screwed up. I doubt it though, a file just doesn't change for itself. Now that I'm thinking, the new version came with a new config file and you used it?
Offline
I actually have no idea if dmraid uses any config files. When I first set up the raid array to work in linux, i just loaded the modules and ran dmraid -ay. That created /dev/mapper/ohgodsomehugeobnoxiousname. I could mount the device that dmraid created without editing any config files other than having the module get loaded from rc.conf.
Offline
I ran out of ideas, I just hope somebody who uses dmraid is paying attention. Sorry i couldn't be much help. Still i would try gparted, just to check if it works under another raid proof linux
Offline
Eh, thanks for trying. I'm going to let chkdsk finish up, back up what's on the disk and then maybe start poking around with gparted. Hopefully that will yeild something helpful.
Offline
I have the same problem.
Unfortunetly my root partition is on fakeraid, so i can't boot.
Output from dmraid -ay:
ERROR: isw: Could not find disk /dev/sdb in the metadata
ERROR: isw: Could not find disk /dev/sdc in the metadata
ERROR: isw: Could not find disk /dev/sdd in the metadata
ERROR: isw: Could not find disk /dev/sda in the metadata
no raid disks
There are no devices in /dev/mapper.
Disk and raid are fine, becouse Vista works as usual.
I'm downloading usb boot image so i can revert kernel to previous one.
This was the output of dmraid. So you should just change in fstab and in Grub your device name from /dev/sda1 to /dev/sdap1
I upgraded dmraid before kernel upgrade, and i saw this notice. I update acording files, and system didn't boot, becouse naming schema didn't change! Revert back to old ones, and arch was runining fine until evening upgrade(including kernel update).
edit
usb pen with arch image freez my pc on bios screen
Last edited by extcake (2008-11-11 10:59:46)
Offline
Same issue here, updated last night, booted now:
[zaggynl@6750 ~]$ sudo dmraid -ay
ERROR: isw: Could not find disk /dev/sdc in the metadata
ERROR: isw: Could not find disk /dev/sdb in the metadata
no raid disks
baw
Offline
What does gparted show for those drives? Are they recognized as sdb1 or sdbp1? Are they missing?
EDIT: What is shown in dmesg?
Last edited by lilsirecho (2008-11-11 17:03:14)
Prediction...This year will be a very odd year!
Hard work does not kill people but why risk it: Charlie Mccarthy
A man is not complete until he is married..then..he is finished.
When ALL is lost, what can be found? Even bytes get lonely for a little bit! X-ray confirms Iam spineless!
Offline
What does gparted show for those drives? Are they recognized as sdb1 or sdbp1? Are they missing?
EDIT: What is shown in dmesg?
gparted shows three hard disks on my system; sda, sdb, and sdc. No sd*p1. sdb and sdc are the two disks that make up the raid array.
dmesg shows a huge amount of errors about sdb and referencing blocks outside of the range of the disk. It did this before the upgrade without any problems, and I assume that it has to do with the fact that the disk is part of a raid array.
attempt to access beyond end of device
sdb: rw=0, want=976751808, limit=488397168
__ratelimit: 155 callbacks suppressed
Buffer I/O error on device sdb1, logical block 976751744
attempt to access beyond end of device
sdb: rw=0, want=976751809, limit=488397168
EDIT: the above error is repeated about 50 times, with a different number for want each time
Last edited by tehfishman (2008-11-11 19:57:44)
Offline