|
[x]
Posted via EE Mobile
|
||
Search, ask, and monitor your questions on the go with EE Mobile. Visit Experts Exchange from your mobile device and never be out of touch again. |
||
| 03/26/2009 at 02:15AM PDT, ID: 24266506 |
|
[x]
Attachment Details
|
||
|
[x]
The Solution Rating System
|
||
With so many solutions, how can you tell which solutions are most likely to help you and which ones are not? To provide you with a tool to use, we rate our solutions based on various elements that most accurately determine if a solution is a quality solution. To explain what factors affect the solution rating, here are the elements we take into consideration when formulating our solution rating.
Your Input Matters If you have any suggestions that you would like to make for our rating system, please ask a question in the Suggestions Zone of Community Support. Thank you! |
||
Help! Kernal cannot find root device unless I manually assemble the MD arrays!
Asked by davepusey in Linux, Linux Administration, Linux Setup
The system has three MD raid arrays...
/dev/md0 is raid1 using /dev/sda1 /dev/sdb1 and /dev/sdc1 mounted as /
/dev/md1 is raid1 using /dev/sda2 /dev/sdb2 and /dev/sdc2 mounted as swap
/dev/md3 is raid5 using /dev/sda3 /dev/sdb3 and /dev/sdc3 mounted as /var/lib/mythtv
The problem I am having is that since adding /dev/sdc to each array, I now get an error (see attached screenshot) during boot and have to manually enter these commands at the prompt to get it to boot properly.
mdadm --assemble /dev/md0 /dev/sda1 /dev/sdb1 /dev/sdc1
mdadm --assemble /dev/md1 /dev/sda2 /dev/sdb2 /dev/sdc2
mdadm --assemble /dev/md3 /dev/sda3 /dev/sdb3 /dev/sdc3
exit
This is all very well and good, but seeing as this system is being used to do unattended recordings in the middle of the night by automatically booting up, recording, and then shutting down again at a specific time. If i'm not on hand to enter those commands it just sits at the prompt indefinatly.
It's almost as if the kernal doesn't know how to assemble the arrays by itself. I'm not very familar with how the kernal works or the booting process, so am a bit stuck in not know how to fix this.
Advertisement
- 1. fosiul01352,869
- 2. ai_ja_nai329,978
- 3. oklit262,340
- 4. arnold221,704
- 5. woolmilkp...207,669
- 6. KeremE182,407
- 7. omarfarid147,060
- 8. Tintin122,044
- 9. duncan_roe108,505
- 10. noci107,694
- 11. torimar107,523
- 12. mrjoltcola101,719
- 13. martin_2...95,130
- 14. Uberpappa93,517
- 15. mwecom...66,069
- 16. WizRd-Li...59,240
- 17. ravenpl57,309
- 18. Mysidia56,625
- 19. kosarajud...53,694
- 20. rindi53,614
- 21. cjl745,371
- 22. medvedd44,880
- 23. hfraser44,048
- 24. jools42,575
- 25. ozo41,684
- 1. ravenpl787,000
- 2. jlevie742,191
- 3. wesly_c...682,797
- 4. duncan_roe659,712
- 5. Tintin640,448
- 6. rindi541,343
- 7. omarfarid526,578
- 8. Gns509,632
- 9. fosiul01446,833
- 10. shakoush...406,756
- 11. pjedmond396,065
- 12. KeremE378,836
- 13. ai_ja_nai377,603
- 14. xDamox363,805
- 15. arnold361,303
- 16. Mysidia306,729
- 17. oklit286,090
- 18. ahoffmann270,110
- 19. noci269,046
- 20. woolmilkp...263,244
- 21. Nopius256,180
- 22. slyong254,367
- 23. nedvis233,870
- 24. ozo218,090
- 25. cjl7209,876
