Nebka load is still high, so I have not done anything yet. I looked into what I am supposed to do, and I must confess I do not understand what I am supposed to do and especially what to do if something does not work right. I have attached a file containing detailed instructions and questions. Please amend so that I can work with it, hopefully tomorrow. Also, how long is this supposed to take? Christian Zimmermann FIGUGEGL! Department of Economics University of Connecticut 341 Mansfield Road, Unit 1063 Storrs, CT 06269-1063 http://ideas.repec.org/zimm/ christian.zimmermann@uconn.edu http://ideas.repec.org/e/pzi1.html
The file sent was incomplete. Here it is complete. On Wed, 12 Mar 2008, Christian Zimmermann wrote:
Nebka load is still high, so I have not done anything yet. I looked into what I am supposed to do, and I must confess I do not understand what I am supposed to do and especially what to do if something does not work right.
I have attached a file containing detailed instructions and questions. Please amend so that I can work with it, hopefully tomorrow.
Also, how long is this supposed to take?
Christian Zimmermann FIGUGEGL! Department of Economics University of Connecticut 341 Mansfield Road, Unit 1063 Storrs, CT 06269-1063 http://ideas.repec.org/zimm/ christian.zimmermann@uconn.edu http://ideas.repec.org/e/pzi1.html
Christian Zimmermann writes
reboot # into 2.4 or 2.6?
into 2.6, SECOND entry,
#at reboot in grub: single user mode (select kernel, press "e", select kernel line, press "e", append "single" at the end of the line, "enter", press "b", root password)
use the second entry, no editing required, I think.
mount -o ro,remount /dev/sda1
Mount root disk read-only. Important.
e2fsck -c -y /dev/sda1
#according to the man page: # Note that in general it is not safe to run e2fsck on mounted filesys- # tems. The only exception is if the -n option is specified, and -c, -l, # or -L options are not specified. However, even if it is safe to do # so, the results printed by e2fsck are not valid if the filesystem is # mounted. If e2fsck asks whether or not you should check a filesystem # which is mounted, the only correct answer is "no". Only experts who # really know what they are doing should consider answering this question # in any other way. #I am no expert, in fact, I hardly understand what I am supposed to do here, #are you sure you want to do this?
A read only mounted disk can be savely checked. Otherwise how would you check the file system
# this takes a few hours. # what if something is wrong?
The -y option will automatically take corrective action required
reboot
#single user again
rsync -va --exclude /vol --exclude /proc --exclude /sys / /vol
grub-install --directory /vol/boot/grub /dev/sdb1
# do you mean #grub-install --root-directory=/vol/boot/grub /dev/sdb1
Yes, sorry!
# this is how I would understand it from the man page on nebka. # and why not use update-grub?
That does a different thing, it updates the list of kernels that are available.
#sdb1, not sdb, right?
I think, but if it gripes try /dev/sdb instead.
#edit /vol/etc/fstab putting the right device for the swap, but how?
I am not sure. Actually, there is a step missing, you need to format the disk. I will do this right now. Inspect and change partition table: nebka:~# cfdisk /dev/sdb nebka:~# nebka:~# nebka:~# nebka:~# mke2fs -j /dev/sdb1 mke2fs 1.40-WIP (14-Nov-2006) /dev/sdb1 is mounted; will not make a filesystem here! nebka:~# mount /dev/sdb1 mount: /dev/sdb1 already mounted or /vol busy mount: according to mtab, /dev/sdb1 is already mounted on /vol nebka:~# cd /vol nebka:/vol# ls lost+found opt nebka:/vol# cd I should have done this to start with: nebka:~# umount /vol but it works like this too... nebka:~# mke2fs -j /dev/sdb1 mke2fs 1.40-WIP (14-Nov-2006) Filesystem label= OS type: Linux Block size=4096 (log=2) Fragment size=4096 (log=2) 17924096 inodes, 35838999 blocks 1791949 blocks (5.00%) reserved for the super user First data block=0 Maximum filesystem blocks=0 1094 block groups 32768 blocks per group, 32768 fragments per group 16384 inodes per group Superblock backups stored on blocks: 32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208, 4096000, 7962624, 11239424, 20480000, 23887872 Writing inode tables: done Creating journal (32768 blocks): done Writing superblocks and filesystem accounting information: done This filesystem will be automatically checked every 29 mounts or 180 days, whichever comes first. Use tune2fs -c or -i to override. nebka:~# mkswap /dev/sdb2 /dev/sdb2: No such device or address It does not like to do the swap, but the /dev/sdb2 is now earmarked for swap. It should be ok for you to let the partition table be as is, just comment out the part that mounts /dev/sdb Actually I did it for you. nebka:~# cat /etc/fstab # /etc/fstab: static file system information. # # <file system> <mount point> <type> <options> <dump> <pass> proc /proc proc defaults 0 0 /dev/sda5 none swap sw 0 0 /dev/sda1 / ext3 defaults,errors=remount-ro 0 1 /dev/hda /media/cdrom iso9660 ro,user,noauto 0 0 /dev/fd0 /media/floppy auto rw,user,noauto 0 0 /dev/hda /cdrom iso9660 ro,user,noauto 0 0 #/dev/sdb1 /vol ext3 defaults 0 1
And I suppose that file will be rsynched from /etc/fstab, right?
Correct. If you switch the two disks, as you must do before the final boot, it will say that what now is /dev/sdb is what gets called /dev/sda, and the current configuration, which places the swap at the end should be just fine. I will go to town now, later to the opera. I expert to be back by 23:00 local time, your 13:00. If you start doing it then you can call me any time during the night, leave me a number and I'll call you right back to discuss the situation with you. Good luck! Cheers, Thomas Krichel http://openlib.org/home/krichel RePEc:per:1965-06-05:thomas_krichel phone: +7 383 330 6813 skype: thomaskrichel
OK. I worked on it. No success so far: it went all fine until rsync. There I first needed to mount the volume, which I did (uncommenting its fstab line). Once the volume was about 4% full, rsync stopped with the message: sent 26876823 bytes received 36660 bytes 68569.38 bytes/sec total size is 55688285389 speedup is 2069.16 rsync error: some files could not be transferred (code 23) at main.c(977) [sendr=2.6.9] along with many readonly errors (on the new volume!) umount, mount -o rw rsync repeatedly, same errors umount, mount -o rw cp -u -a /home/* /vol/home/. gets me to 5%, then readonly errors Capturing the error messages to see the first ones, I see the following: attempt to access beyond end of device sdb1: rw=0 want=281018384, limit 273442302 EXT3-fs eror (device sdb1): read_inode_bitmap: Cannot read inode bitmap - blockgroup=1072, inode_bitmap=35127297 Aborting journal on device sdb1. ... Remounting filesystem read-only Great... output from df: /dev/sdb1 141106132 5751332 128187004 5% /vol from fstab: /dev/sdb1 /vol ext3 defaults 0 1 from e2fsck -c -y /dev/sdb1 /dev/sdb1: recovering journal The filesystem size (according to the superblock) is 35838999 blocks The physical size of the device is 34180287 Either the superblock or the partition table is likely to be corrupt! Abort? yes I am back in my office to get some warmth. I can be reached at xx1-860-486-3272 until I head back to the machine rom with suggestions. Machine was left in single user mode. By the way, it boots by default into kernel 2.4, but I worked with 2.6. Christian Zimmermann FIGUGEGL! Department of Economics University of Connecticut 341 Mansfield Road, Unit 1063 Storrs, CT 06269-1063 http://ideas.repec.org/zimm/ christian.zimmermann@uconn.edu http://ideas.repec.org/e/pzi1.html On Thu, 13 Mar 2008, Thomas Krichel wrote:
Christian Zimmermann writes
reboot # into 2.4 or 2.6?
into 2.6, SECOND entry,
#at reboot in grub: single user mode (select kernel, press "e", select kernel line, press "e", append "single" at the end of the line, "enter", press "b", root password)
use the second entry, no editing required, I think.
mount -o ro,remount /dev/sda1
Mount root disk read-only. Important.
e2fsck -c -y /dev/sda1
#according to the man page: # Note that in general it is not safe to run e2fsck on mounted filesys- # tems. The only exception is if the -n option is specified, and -c, -l, # or -L options are not specified. However, even if it is safe to do # so, the results printed by e2fsck are not valid if the filesystem is # mounted. If e2fsck asks whether or not you should check a filesystem # which is mounted, the only correct answer is "no". Only experts who # really know what they are doing should consider answering this question # in any other way. #I am no expert, in fact, I hardly understand what I am supposed to do here, #are you sure you want to do this?
A read only mounted disk can be savely checked. Otherwise how would you check the file system
# this takes a few hours. # what if something is wrong?
The -y option will automatically take corrective action required
reboot
#single user again
rsync -va --exclude /vol --exclude /proc --exclude /sys / /vol
grub-install --directory /vol/boot/grub /dev/sdb1
# do you mean #grub-install --root-directory=/vol/boot/grub /dev/sdb1
Yes, sorry!
# this is how I would understand it from the man page on nebka. # and why not use update-grub?
That does a different thing, it updates the list of kernels that are available.
#sdb1, not sdb, right?
I think, but if it gripes try /dev/sdb instead.
#edit /vol/etc/fstab putting the right device for the swap, but how?
I am not sure. Actually, there is a step missing, you need to format the disk. I will do this right now.
Inspect and change partition table:
nebka:~# cfdisk /dev/sdb nebka:~# nebka:~# nebka:~# nebka:~# mke2fs -j /dev/sdb1 mke2fs 1.40-WIP (14-Nov-2006) /dev/sdb1 is mounted; will not make a filesystem here! nebka:~# mount /dev/sdb1 mount: /dev/sdb1 already mounted or /vol busy mount: according to mtab, /dev/sdb1 is already mounted on /vol nebka:~# cd /vol nebka:/vol# ls lost+found opt nebka:/vol# cd
I should have done this to start with:
nebka:~# umount /vol
but it works like this too...
nebka:~# mke2fs -j /dev/sdb1 mke2fs 1.40-WIP (14-Nov-2006) Filesystem label= OS type: Linux Block size=4096 (log=2) Fragment size=4096 (log=2) 17924096 inodes, 35838999 blocks 1791949 blocks (5.00%) reserved for the super user First data block=0 Maximum filesystem blocks=0 1094 block groups 32768 blocks per group, 32768 fragments per group 16384 inodes per group Superblock backups stored on blocks: 32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208, 4096000, 7962624, 11239424, 20480000, 23887872
Writing inode tables: done Creating journal (32768 blocks): done Writing superblocks and filesystem accounting information: done
This filesystem will be automatically checked every 29 mounts or 180 days, whichever comes first. Use tune2fs -c or -i to override.
nebka:~# mkswap /dev/sdb2 /dev/sdb2: No such device or address
It does not like to do the swap, but the /dev/sdb2 is now earmarked for swap.
It should be ok for you to let the partition table be as is, just comment out the part that mounts /dev/sdb Actually I did it for you.
nebka:~# cat /etc/fstab # /etc/fstab: static file system information. # # <file system> <mount point> <type> <options> <dump> <pass> proc /proc proc defaults 0 0 /dev/sda5 none swap sw 0 0 /dev/sda1 / ext3 defaults,errors=remount-ro 0 1 /dev/hda /media/cdrom iso9660 ro,user,noauto 0 0 /dev/fd0 /media/floppy auto rw,user,noauto 0 0 /dev/hda /cdrom iso9660 ro,user,noauto 0 0 #/dev/sdb1 /vol ext3 defaults 0 1
And I suppose that file will be rsynched from /etc/fstab, right?
Correct. If you switch the two disks, as you must do before the final boot, it will say that what now is /dev/sdb is what gets called /dev/sda, and the current configuration, which places the swap at the end should be just fine.
I will go to town now, later to the opera. I expert to be back by 23:00 local time, your 13:00. If you start doing it then you can call me any time during the night, leave me a number and I'll call you right back to discuss the situation with you.
Good luck!
Cheers,
Thomas Krichel http://openlib.org/home/krichel RePEc:per:1965-06-05:thomas_krichel phone: +7 383 330 6813 skype: thomaskrichel
Reboot in multi-user mode, I will have a look, maybe I can figure out. It looks like a prepared /dev/sdb wrongly. Cheers, Thomas Krichel http://openlib.org/home/krichel RePEc:per:1965-06-05:thomas_krichel phone: +7 383 330 6813 skype: thomaskrichel
OK. Will have to treck back to the machine room first. authors.repec.org is redirected elsewhere. Is it thus possible to work out everything in multi-user mode? Or should I stay in the machine room? Christian Zimmermann FIGUGEGL! Department of Economics University of Connecticut 341 Mansfield Road, Unit 1063 Storrs, CT 06269-1063 http://ideas.repec.org/zimm/ christian.zimmermann@uconn.edu http://ideas.repec.org/e/pzi1.html On Thu, 13 Mar 2008, Thomas Krichel wrote:
Reboot in multi-user mode, I will have a look, maybe I can figure out. It looks like a prepared /dev/sdb wrongly.
Cheers,
Thomas Krichel http://openlib.org/home/krichel RePEc:per:1965-06-05:thomas_krichel phone: +7 383 330 6813 skype: thomaskrichel
Christian Zimmermann writes
OK. Will have to treck back to the machine room first.
authors.repec.org is redirected elsewhere. Is it thus possible to work out everything in multi-user mode? Or should I stay in the machine room?
No get out of there, let me try to fix it. This sdb shit looks suspiciously as having the signature "Thomas Krichel". Cheers, Thomas Krichel http://openlib.org/home/krichel RePEc:per:1965-06-05:thomas_krichel phone: +7 383 330 6813 skype: thomaskrichel
Machine is back inmulti-user mode. Bootedinto 2.6, default is 2.4 Hung on disk error for sdb1, Ctrl-D'ed to finish boot. Probably need to hang around here, because a reboot would not conclude if this error persists. Christian Zimmermann FIGUGEGL! Department of Economics University of Connecticut 341 Mansfield Road, Unit 1063 Storrs, CT 06269-1063 http://ideas.repec.org/zimm/ christian.zimmermann@uconn.edu http://ideas.repec.org/e/pzi1.html On Thu, 13 Mar 2008, Thomas Krichel wrote:
Christian Zimmermann writes
OK. Will have to treck back to the machine room first.
authors.repec.org is redirected elsewhere. Is it thus possible to work out everything in multi-user mode? Or should I stay in the machine room?
No get out of there, let me try to fix it. This sdb shit looks suspiciously as having the signature "Thomas Krichel".
Cheers,
Thomas Krichel http://openlib.org/home/krichel RePEc:per:1965-06-05:thomas_krichel phone: +7 383 330 6813 skype: thomaskrichel
Christian Zimmermann writes
Machine is back inmulti-user mode. Bootedinto 2.6, default is 2.4
Hung on disk error for sdb1, Ctrl-D'ed to finish boot. Probably need to hang around here, because a reboot would not conclude if this error persists.
I am on the case. I redid the partitioning and formated sdb1, set up swap on sdb2, this time without a problem. The rsync is running. If/when it has finished, run the grub command, then swap the disks. I am awfully tired, will try to sleep but don't hesitate to call, I'll call you back. Cheers, Thomas Krichel http://openlib.org/home/krichel RePEc:per:1965-06-05:thomas_krichel phone: +7 383 330 6813 skype: thomaskrichel
Clarification: for the swsap, do I chnage fstab? Christian Zimmermann FIGUGEGL! Department of Economics University of Connecticut 341 Mansfield Road, Unit 1063 Storrs, CT 06269-1063 http://ideas.repec.org/zimm/ christian.zimmermann@uconn.edu http://ideas.repec.org/e/pzi1.html On Fri, 14 Mar 2008, Thomas Krichel wrote:
Christian Zimmermann writes
Machine is back inmulti-user mode. Bootedinto 2.6, default is 2.4
Hung on disk error for sdb1, Ctrl-D'ed to finish boot. Probably need to hang around here, because a reboot would not conclude if this error persists.
I am on the case. I redid the partitioning and formated sdb1, set up swap on sdb2, this time without a problem.
The rsync is running. If/when it has finished, run the grub command, then swap the disks.
I am awfully tired, will try to sleep but don't hesitate to call, I'll call you back.
Cheers,
Thomas Krichel http://openlib.org/home/krichel RePEc:per:1965-06-05:thomas_krichel phone: +7 383 330 6813 skype: thomaskrichel
rsync finished, tried the grub-install, it failed: end_request: I/O error, dev fd0, sector 0 end_request: I/O error, dev fd0, sector 0 end_request: I/O error, dev fd0, sector 0 end_request: I/O error, dev fd0, sector 0 end_request: I/O error, dev fd0, sector 0 end_request: I/O error, dev fd0, sector 0 The file /vol/boot/grub/boot/grub/stage1 not read correctly I have not touched /etc/fstab/. I have not rebooted. Note that it will reboot into kernel 2.4 by default. I have not restarted rid. I am out of here. I can get back to the machine room Friday 7:30am EDT. Christian Zimmermann FIGUGEGL! Department of Economics University of Connecticut 341 Mansfield Road, Unit 1063 Storrs, CT 06269-1063 http://ideas.repec.org/zimm/ christian.zimmermann@uconn.edu http://ideas.repec.org/e/pzi1.html On Thu, 13 Mar 2008, Christian Zimmermann wrote:
Clarification: for the swsap, do I chnage fstab?
Christian Zimmermann FIGUGEGL! Department of Economics University of Connecticut 341 Mansfield Road, Unit 1063 Storrs, CT 06269-1063 http://ideas.repec.org/zimm/ christian.zimmermann@uconn.edu http://ideas.repec.org/e/pzi1.html
On Fri, 14 Mar 2008, Thomas Krichel wrote:
Christian Zimmermann writes
Machine is back inmulti-user mode. Bootedinto 2.6, default is 2.4
Hung on disk error for sdb1, Ctrl-D'ed to finish boot. Probably need to hang around here, because a reboot would not conclude if this error persists.
I am on the case. I redid the partitioning and formated sdb1, set up swap on sdb2, this time without a problem.
The rsync is running. If/when it has finished, run the grub command, then swap the disks.
I am awfully tired, will try to sleep but don't hesitate to call, I'll call you back.
Cheers,
Thomas Krichel http://openlib.org/home/krichel RePEc:per:1965-06-05:thomas_krichel phone: +7 383 330 6813 skype: thomaskrichel
_______________________________________________ RAS-run mailing list RAS-run@lists.openlib.org http://lists.openlib.org/cgi-bin/mailman/listinfo/ras-run
Christian Zimmermann writes
rsync finished, tried the grub-install, it failed:
end_request: I/O error, dev fd0, sector 0 end_request: I/O error, dev fd0, sector 0 end_request: I/O error, dev fd0, sector 0 end_request: I/O error, dev fd0, sector 0 end_request: I/O error, dev fd0, sector 0 end_request: I/O error, dev fd0, sector 0 The file /vol/boot/grub/boot/grub/stage1 not read correctly
I have not touched /etc/fstab/. I have not rebooted. Note that it will reboot into kernel 2.4 by default. I have not restarted rid.
I am out of here. I can get back to the machine room Friday 7:30am EDT.
You could have woken me up. Anyway, having woken up, I did nebka:~# grub-install --root-directory=/vol /dev/sdb /dev/sdb does not have any corresponding BIOS drive. Googling for this I did nebka:~# grub-install --recheck --root-directory=/vol /dev/sdb1 Probing devices to guess BIOS drives. This may take a long time. Installation finished. No error reported. This is the contents of the device map /vol/boot/grub/device.map. Check if this is correct or not. If any of the lines is incorrect, fix it and re-run the script `grub-install'. (fd0) /dev/fd0 (hd0) /dev/sda (hd1) /dev/sdb We should be ready now to exchange the disks. Take the 80G out. Put the 140 into the physical place where the 80G was. Go into the bios to check that the bios sees only the 140G disk. You may have to do this a couple of times, the bios is sometimes "slow". Then reboot to Linux, everything should start as normal. If this fails, put the 80G back and check that the bios boots off it. Then you can change the root parameter in the /boot/grub/menu.lst The default entry is set on line 12 of this file. The numbering starts at 0. It used to be set to 2, to prevent firing up the 2.6 kernel. I have set it to 0. Thus kernel /boot/vmlinuz-2.6.18-6-686 root=/dev/sda1 ro noacpi noapic can be changed to kernel /boot/vmlinuz-2.6.18-6-686 root=/dev/sdb1 ro noacpi noapic Then we have the 80G disk in there. In /boot/grub/menu.lst change kernel /boot/vmlinuz-2.6.18-6-686 root=/dev/sda1 ro single kernel /boot/vmlinuz-2.4.27-2-686 root=/dev/sda1 ro noacpi noapic kernel /boot/vmlinuz-2.4.27-2-686 root=/dev/sda1 ro single to kernel /boot/vmlinuz-2.6.18-6-686 root=/dev/sdb1 ro single kernel /boot/vmlinuz-2.4.27-2-686 root=/dev/sdb1 ro noacpi noapic kernel /boot/vmlinuz-2.4.27-2-686 root=/dev/sdb1 ro single and reboot. It then should see the 80G as a boot disk, and use the 140G as the root. Cheers, Thomas Krichel http://openlib.org/home/krichel RePEc:per:1965-06-05:thomas_krichel phone: +7 383 330 6813 skype: thomaskrichel
Don't you want me to put the 80GB disk in place of the new one, i.e., just switch places? It looks like you want only the 140GB, and keep the current placement only if BIOS does not boot off 140GB. Christian Zimmermann FIGUGEGL! Department of Economics University of Connecticut 341 Mansfield Road, Unit 1063 Storrs, CT 06269-1063 http://ideas.repec.org/zimm/ christian.zimmermann@uconn.edu http://ideas.repec.org/e/pzi1.html On Fri, 14 Mar 2008, Thomas Krichel wrote:
Christian Zimmermann writes
rsync finished, tried the grub-install, it failed:
end_request: I/O error, dev fd0, sector 0 end_request: I/O error, dev fd0, sector 0 end_request: I/O error, dev fd0, sector 0 end_request: I/O error, dev fd0, sector 0 end_request: I/O error, dev fd0, sector 0 end_request: I/O error, dev fd0, sector 0 The file /vol/boot/grub/boot/grub/stage1 not read correctly
I have not touched /etc/fstab/. I have not rebooted. Note that it will reboot into kernel 2.4 by default. I have not restarted rid.
I am out of here. I can get back to the machine room Friday 7:30am EDT.
You could have woken me up.
Anyway, having woken up, I did
nebka:~# grub-install --root-directory=/vol /dev/sdb /dev/sdb does not have any corresponding BIOS drive.
Googling for this I did
nebka:~# grub-install --recheck --root-directory=/vol /dev/sdb1 Probing devices to guess BIOS drives. This may take a long time. Installation finished. No error reported. This is the contents of the device map /vol/boot/grub/device.map. Check if this is correct or not. If any of the lines is incorrect, fix it and re-run the script `grub-install'.
(fd0) /dev/fd0 (hd0) /dev/sda (hd1) /dev/sdb
We should be ready now to exchange the disks. Take the 80G out. Put the 140 into the physical place where the 80G was. Go into the bios to check that the bios sees only the 140G disk. You may have to do this a couple of times, the bios is sometimes "slow". Then reboot to Linux, everything should start as normal.
If this fails, put the 80G back and check that the bios boots off it. Then you can change the root parameter in the
/boot/grub/menu.lst
The default entry is set on line 12 of this file. The numbering starts at 0. It used to be set to 2, to prevent firing up the 2.6 kernel. I have set it to 0. Thus
kernel /boot/vmlinuz-2.6.18-6-686 root=/dev/sda1 ro noacpi noapic
can be changed to
kernel /boot/vmlinuz-2.6.18-6-686 root=/dev/sdb1 ro noacpi noapic
Then we have the 80G disk in there. In /boot/grub/menu.lst change
kernel /boot/vmlinuz-2.6.18-6-686 root=/dev/sda1 ro single kernel /boot/vmlinuz-2.4.27-2-686 root=/dev/sda1 ro noacpi noapic kernel /boot/vmlinuz-2.4.27-2-686 root=/dev/sda1 ro single
to
kernel /boot/vmlinuz-2.6.18-6-686 root=/dev/sdb1 ro single kernel /boot/vmlinuz-2.4.27-2-686 root=/dev/sdb1 ro noacpi noapic kernel /boot/vmlinuz-2.4.27-2-686 root=/dev/sdb1 ro single
and reboot. It then should see the 80G as a boot disk, and use the 140G as the root.
Cheers,
Thomas Krichel http://openlib.org/home/krichel RePEc:per:1965-06-05:thomas_krichel phone: +7 383 330 6813 skype: thomaskrichel
Christian Zimmermann writes
Don't you want me to put the 80GB disk in place of the new one, i.e., just switch places? It looks like you want only the 140GB, and keep the current placement only if BIOS does not boot off 140GB.
Yes, if my theory is correct, the problems comes from hardware problem with the 80G, so we need to take it out. Where the 80G was, put the 140G in. Cheers, Thomas Krichel http://openlib.org/home/krichel RePEc:per:1965-06-05:thomas_krichel phone: +7 383 330 6813 skype: thomaskrichel
Would it hurt to still have the 80G in, in the third slot? Christian Zimmermann FIGUGEGL! Department of Economics University of Connecticut 341 Mansfield Road, Unit 1063 Storrs, CT 06269-1063 http://ideas.repec.org/zimm/ christian.zimmermann@uconn.edu http://ideas.repec.org/e/pzi1.html On Fri, 14 Mar 2008, Thomas Krichel wrote:
Christian Zimmermann writes
Don't you want me to put the 80GB disk in place of the new one, i.e., just switch places? It looks like you want only the 140GB, and keep the current placement only if BIOS does not boot off 140GB.
Yes, if my theory is correct, the problems comes from hardware problem with the 80G, so we need to take it out. Where the 80G was, put the 140G in.
Cheers,
Thomas Krichel http://openlib.org/home/krichel RePEc:per:1965-06-05:thomas_krichel phone: +7 383 330 6813 skype: thomaskrichel
Christian Zimmermann writes
Would it hurt to still have the 80G in, in the third slot?
Yes. Disk make heat, no good for fellow disks. Cheers, Thomas Krichel http://openlib.org/home/krichel RePEc:per:1965-06-05:thomas_krichel phone: +7 383 330 6813 skype: thomaskrichel
OK, I am heading over. Hopefully, I will find some screw drivers there. Christian Zimmermann FIGUGEGL! Department of Economics University of Connecticut 341 Mansfield Road, Unit 1063 Storrs, CT 06269-1063 http://ideas.repec.org/zimm/ christian.zimmermann@uconn.edu http://ideas.repec.org/e/pzi1.html On Fri, 14 Mar 2008, Thomas Krichel wrote:
Christian Zimmermann writes
Would it hurt to still have the 80G in, in the third slot?
Yes. Disk make heat, no good for fellow disks.
Cheers,
Thomas Krichel http://openlib.org/home/krichel RePEc:per:1965-06-05:thomas_krichel phone: +7 383 330 6813 skype: thomaskrichel
On it right now. After three boots, the BIOS still does not recognize the new config. However, there is a RAID container configuratyion utility. Is this something I can use? Christian Zimmermann FIGUGEGL! Department of Economics University of Connecticut 341 Mansfield Road, Unit 1063 Storrs, CT 06269-1063 http://ideas.repec.org/zimm/ christian.zimmermann@uconn.edu http://ideas.repec.org/e/pzi1.html On Fri, 14 Mar 2008, Christian Zimmermann wrote:
OK, I am heading over. Hopefully, I will find some screw drivers there.
Christian Zimmermann FIGUGEGL! Department of Economics University of Connecticut 341 Mansfield Road, Unit 1063 Storrs, CT 06269-1063 http://ideas.repec.org/zimm/ christian.zimmermann@uconn.edu http://ideas.repec.org/e/pzi1.html
On Fri, 14 Mar 2008, Thomas Krichel wrote:
Christian Zimmermann writes
Would it hurt to still have the 80G in, in the third slot?
Yes. Disk make heat, no good for fellow disks.
Cheers,
Thomas Krichel http://openlib.org/home/krichel RePEc:per:1965-06-05:thomas_krichel phone: +7 383 330 6813 skype: thomaskrichel
_______________________________________________ RAS-run mailing list RAS-run@lists.openlib.org http://lists.openlib.org/cgi-bin/mailman/listinfo/ras-run
Christian Zimmermann writes
On it right now. After three boots, the BIOS still does not recognize the new config.
Are you in setup?
However, there is a RAID container configuratyion utility. Is this something I can use?
I don't know. Can I call you there? Cheers, Thomas Krichel http://openlib.org/home/krichel RePEc:per:1965-06-05:thomas_krichel phone: +7 383 330 6813 skype: thomaskrichel
On Fri, 14 Mar 2008, Thomas Krichel wrote:
Christian Zimmermann writes
On it right now. After three boots, the BIOS still does not recognize the new config.
Are you in setup?
Rebooted, now in BIOS setup.
However, there is a RAID container configuratyion utility. Is this something I can use?
I don't know.
Can I call you there?
There is no phone close to the rack. Besides it is very noisy with all the servers and the temperature control.
Cheers,
Thomas Krichel http://openlib.org/home/krichel RePEc:per:1965-06-05:thomas_krichel phone: +7 383 330 6813 skype: thomaskrichel
Christian Zimmermann writes
Are you in setup?
Rebooted, now in BIOS setup.
And the disk is not seen by the bios? Cheers, Thomas Krichel http://openlib.org/home/krichel RePEc:per:1965-06-05:thomas_krichel phone: +7 383 330 6813 skype: thomaskrichel
On Fri, 14 Mar 2008, Thomas Krichel wrote:
Christian Zimmermann writes
Are you in setup?
Rebooted, now in BIOS setup.
And the disk is not seen by the bios?
Nope. Says something is wrong with disk 0, then proceeds saying there is disk 0 with 80G and disk 1 with 140G.
Cheers,
Thomas Krichel http://openlib.org/home/krichel RePEc:per:1965-06-05:thomas_krichel phone: +7 383 330 6813 skype: thomaskrichel
Christian Zimmermann writes
Nope. Says something is wrong with disk 0, then proceeds saying there is disk 0 with 80G and disk 1 with 140G.
argh!!! put the 80g back in, when boot, edit the line to say that root=/dev/sdb1 Cheers, Thomas Krichel http://openlib.org/home/krichel RePEc:per:1965-06-05:thomas_krichel phone: +7 383 330 6813 skype: thomaskrichel
Not working. BIOS recognizes now only the 80GB, and linux waits forever for the root file system. I rebooted while changing in grub back to sdba1, same problem. Christian Zimmermann FIGUGEGL! Department of Economics University of Connecticut 341 Mansfield Road, Unit 1063 Storrs, CT 06269-1063 http://ideas.repec.org/zimm/ christian.zimmermann@uconn.edu http://ideas.repec.org/e/pzi1.html On Fri, 14 Mar 2008, Thomas Krichel wrote:
Christian Zimmermann writes
Nope. Says something is wrong with disk 0, then proceeds saying there is disk 0 with 80G and disk 1 with 140G.
argh!!!
put the 80g back in, when boot, edit the line to say that root=/dev/sdb1
Cheers,
Thomas Krichel http://openlib.org/home/krichel RePEc:per:1965-06-05:thomas_krichel phone: +7 383 330 6813 skype: thomaskrichel
Christian Zimmermann writes
Not working. BIOS recognizes now only the 80GB, and linux waits forever for the root file system. I rebooted while changing in grub back to sdba1, same problem.
Put it out again, switch on off, wait 10 seconds, switch it on, play until it only sees the 140G. if not start again... It is just a matter of fiddling with it. Cheers, Thomas Krichel http://openlib.org/home/krichel RePEc:per:1965-06-05:thomas_krichel phone: +7 383 330 6813 skype: thomaskrichel
I managed BIOS to recognize the 140Gb disk by fiddling in the RAID configuration utillity. But linux does not want to boot from it. Something must be done in the RAID thingy, but I have no idea what I am doing. On Fri, 14 Mar 2008, Thomas Krichel wrote:
Christian Zimmermann writes
Not working. BIOS recognizes now only the 80GB, and linux waits forever for the root file system. I rebooted while changing in grub back to sdba1, same problem.
Put it out again, switch on off, wait 10 seconds, switch it on, play until it only sees the 140G. if not start again...
It is just a matter of fiddling with it.
Cheers,
Thomas Krichel http://openlib.org/home/krichel RePEc:per:1965-06-05:thomas_krichel phone: +7 383 330 6813 skype: thomaskrichel
Christian Zimmermann writes
I managed BIOS to recognize the 140Gb disk by fiddling in the RAID configuration utillity. But linux does not want to boot from it.
What si the error? Do you see the grub screen?
Something must be done in the RAID thingy, but I have no idea what I am doing.
I don't nkow anythyn about RAID. Cheers, Thomas Krichel http://openlib.org/home/krichel RePEc:per:1965-06-05:thomas_krichel phone: +7 383 330 6813 skype: thomaskrichel
On Fri, 14 Mar 2008, Thomas Krichel wrote:
Christian Zimmermann writes
I managed BIOS to recognize the 140Gb disk by fiddling in the RAID configuration utillity. But linux does not want to boot from it.
What si the error? Do you see the grub screen?
Something like "try F1 to try booting", forever. I put 80 GB back inbto the first slot, 140GB in the other. BIOS recognizes them. Booted with root on sda1 (sdb1 does not work). Everything except sdb1 is not recognized. You can log in to look around. I am out of here for a while, there is a line of students waiting at my office.
Something must be done in the RAID thingy, but I have no idea what I am doing.
I don't nkow anythyn about RAID.
Cheers,
Thomas Krichel http://openlib.org/home/krichel RePEc:per:1965-06-05:thomas_krichel phone: +7 383 330 6813 skype: thomaskrichel
Christian Zimmermann writes
On Fri, 14 Mar 2008, Thomas Krichel wrote:
Christian Zimmermann writes
I managed BIOS to recognize the 140Gb disk by fiddling in the RAID configuration utillity. But linux does not want to boot from it.
What si the error? Do you see the grub screen?
Something like "try F1 to try booting", forever.
I put 80 GB back inbto the first slot, 140GB in the other. BIOS recognizes them. Booted with root on sda1 (sdb1 does not work). Everything except sdb1 is not recognized.
from dmesg, at first it is seen sd 0:0:0:0: Attached scsi removable disk sda SCSI device sdb: 286716544 512-byte hdwr sectors (146799 MB) sdb: assuming Write Enabled sdb: assuming drive cache: write through SCSI device sdb: 286716544 512-byte hdwr sectors (146799 MB) sdb: assuming Write Enabled sdb: assuming drive cache: write through sdb: unknown partition table sd 0:0:1:0: Attached scsi removable disk sdb but later aacraid: Host adapter reset request. SCSI hang ? aacraid: Host adapter reset request. SCSI hang ? aacraid: Host adapter reset request. SCSI hang ? No clue. That's the problem with scsi, very flaky. Cheers, Thomas Krichel http://openlib.org/home/krichel RePEc:per:1965-06-05:thomas_krichel phone: +7 383 330 6813 skype: thomaskrichel
I will be heading back to the server room with Tim in a few minutes. We will be trying to just get it to run with the second drive recognized. Christian Zimmermann FIGUGEGL! Department of Economics University of Connecticut 341 Mansfield Road, Unit 1063 Storrs, CT 06269-1063 http://ideas.repec.org/zimm/ christian.zimmermann@uconn.edu http://ideas.repec.org/e/pzi1.html On Fri, 14 Mar 2008, Christian Zimmermann wrote:
On Fri, 14 Mar 2008, Thomas Krichel wrote:
Christian Zimmermann writes
I managed BIOS to recognize the 140Gb disk by fiddling in the RAID configuration utillity. But linux does not want to boot from it.
What si the error? Do you see the grub screen?
Something like "try F1 to try booting", forever.
I put 80 GB back inbto the first slot, 140GB in the other. BIOS recognizes them. Booted with root on sda1 (sdb1 does not work). Everything except sdb1 is not recognized.
You can log in to look around. I am out of here for a while, there is a line of students waiting at my office.
Something must be done in the RAID thingy, but I have no idea what I am doing.
I don't nkow anythyn about RAID.
Cheers,
Thomas Krichel http://openlib.org/home/krichel RePEc:per:1965-06-05:thomas_krichel phone: +7 383 330 6813 skype: thomaskrichel
_______________________________________________ RAS-run mailing list RAS-run@lists.openlib.org http://lists.openlib.org/cgi-bin/mailman/listinfo/ras-run
Christian Zimmermann writes
I will be heading back to the server room with Tim in a few minutes. We will be trying to just get it to run with the second drive recognized.
meaning we will have to start all over again soon. But there may be a way to get to to boot the 140G. Cheers, Thomas Krichel http://openlib.org/home/krichel RePEc:per:1965-06-05:thomas_krichel phone: +7 383 330 6813 skype: thomaskrichel
Tim is convinced we do not have a disk problem on nebka. The crashes were due to software issues. Thus we want to just get the setup as a few days ago, and then see from there. Christian Zimmermann FIGUGEGL! Department of Economics University of Connecticut 341 Mansfield Road, Unit 1063 Storrs, CT 06269-1063 http://ideas.repec.org/zimm/ christian.zimmermann@uconn.edu http://ideas.repec.org/e/pzi1.html On Fri, 14 Mar 2008, Thomas Krichel wrote:
Christian Zimmermann writes
I will be heading back to the server room with Tim in a few minutes. We will be trying to just get it to run with the second drive recognized.
meaning we will have to start all over again soon. But there may be a way to get to to boot the 140G.
Cheers,
Thomas Krichel http://openlib.org/home/krichel RePEc:per:1965-06-05:thomas_krichel phone: +7 383 330 6813 skype: thomaskrichel
Christian Zimmermann writes
Clarification: for the swsap, do I chnage fstab?
No idea, I am sorry! Cheers, Thomas Krichel http://openlib.org/home/krichel RePEc:per:1965-06-05:thomas_krichel phone: +7 383 330 6813 skype: thomaskrichel
participants (2)
-
Christian Zimmermann -
Thomas Krichel