Re: [SOLVED] How to tell the compiler NOT to assume cpu provides atomic instructions
On Mon, Mar 7, 2011 at 9:27 PM, RR wrote: > HI Brian, > > On Mon, Mar 7, 2011 at 9:03 PM, brian m. carlson < > sand...@crustytoothpaste.net> wrote: > >> On Mon, Mar 07, 2011 at 07:54:13PM -0500, RR wrote: >> > checking whether the C compiler (gcc -pthread -I../..//include >> > -I/usr/include/libxml2 -pipe -Wall -Wstrict-prototypes >> -Wmissing-prototypes >> > -Wmissing-declarations -g3 -mtune=ultrasparc -mcpu=v8 >> -fomit-frame-pointer >> > -O6) works ... yes >> > checking whether the C compiler (gcc -pthread -I../..//include >> > -I/usr/include/libxml2 -pipe -Wall -Wstrict-prototypes >> -Wmissing-prototypes >> > -Wmissing-declarations -g3 -mtune=ultrasparc -mcpu=v8 >> -fomit-frame-pointer >> > -O6) is a cross-compiler... no >> >> Okay. I've pinpointed the problem. If atomic intrinsics are used but >> not supported on the target architecture (variant), GCC will emit a link >> error for that function. >> >> Your problem is -mcpu=v8. v8 processors (AFAICT) do not support the >> intrinsics necessary. Remove that option (or whatever is causing that >> option) and it should work. It may be that for some reason configure >> thinks that 32-bit code should use -mcpu=v8, but that isn't the case. >> Debian's default configuration (without -mcpu and -mtune) should work >> just fine for you. > > > Believe it or not, I had the same suspicion after I pasted that output for > gcc for you. All I have found so far is that when the asterisk source > package is untarred, the Makefile is already configured to see sparc64 and > then add these lines re: -mcpu and -mtune to gcc. So I have manually removed > these lines from the Makefile and making/linking it from scratch. Is that > all that needed to be done or is there something else that needs to be done? > The make is running right now...takes about 10 mins or so to run so will > report back based on what happens. Hopefully this fixes it > You da Man! Make is complete without errors although I only removed the -mcpu line and left the -mtune line in there. Thanks SO much \R
Re: How to tell the compiler NOT to assume cpu provides atomic instructions
HI Brian, On Mon, Mar 7, 2011 at 9:03 PM, brian m. carlson < sand...@crustytoothpaste.net> wrote: > On Mon, Mar 07, 2011 at 07:54:13PM -0500, RR wrote: > > checking whether the C compiler (gcc -pthread -I../..//include > > -I/usr/include/libxml2 -pipe -Wall -Wstrict-prototypes > -Wmissing-prototypes > > -Wmissing-declarations -g3 -mtune=ultrasparc -mcpu=v8 > -fomit-frame-pointer > > -O6) works ... yes > > checking whether the C compiler (gcc -pthread -I../..//include > > -I/usr/include/libxml2 -pipe -Wall -Wstrict-prototypes > -Wmissing-prototypes > > -Wmissing-declarations -g3 -mtune=ultrasparc -mcpu=v8 > -fomit-frame-pointer > > -O6) is a cross-compiler... no > > Okay. I've pinpointed the problem. If atomic intrinsics are used but > not supported on the target architecture (variant), GCC will emit a link > error for that function. > > Your problem is -mcpu=v8. v8 processors (AFAICT) do not support the > intrinsics necessary. Remove that option (or whatever is causing that > option) and it should work. It may be that for some reason configure > thinks that 32-bit code should use -mcpu=v8, but that isn't the case. > Debian's default configuration (without -mcpu and -mtune) should work > just fine for you. Believe it or not, I had the same suspicion after I pasted that output for gcc for you. All I have found so far is that when the asterisk source package is untarred, the Makefile is already configured to see sparc64 and then add these lines re: -mcpu and -mtune to gcc. So I have manually removed these lines from the Makefile and making/linking it from scratch. Is that all that needed to be done or is there something else that needs to be done? The make is running right now...takes about 10 mins or so to run so will report back based on what happens. Hopefully this fixes it
Re: How to tell the compiler NOT to assume cpu provides atomic instructions
On Mon, Mar 7, 2011 at 7:38 PM, brian m. carlson < sand...@crustytoothpaste.net> wrote: > Hi. *Please* do not CC me; I'm subscribed to the list. Sorry, the default on my gmail is "Reply All" and usually I remove relevant parties from the To/Cc: headers, guess missed it this time. Wasn't intentional. > > umm sorry if this is a stupid question but I don't know what other output > to > > provide other than what I provided above which was from the 'make' > command. > > The beginning of that is: > > Normally, make will print the actual command line of the command it is > running. In this case, Asterisk upstream has hidden this and printed > something else instead. > > > # make > > CC="cc" CXX="" LD="" AR="" RANLIB="" CFLAGS="" make -C menuselect > > CONFIGURE_SILENT="--silent" makeopts > > Using --silent as an argument to make will prevent it from printing > the commands as they are executed. You should probably ask Asterisk > upstream how to get the commands printed as they are executed. I need to > see the compilation command line (probably starting "cc" or "gcc") so > that I know what flags are being used. The command line used for linking > would also be useful. > Ok, I'll leave an email in the Asterisk list but in the meantime, this is what I found from the make output (just posting the relevant lines): CC="cc" CXX="" LD="" AR="" RANLIB="" CFLAGS="" make -C menuselect CONFIGURE_SILENT="--silent" menuselect make[1]: Entering directory `/usr/src/asterisk-1.8.3/menuselect' gcc -g -c -D_GNU_SOURCE -Wall -c -o menuselect.o menuselect.c gcc -g -c -D_GNU_SOURCE -Wall -c -o strcompat.o strcompat.c gcc -g -c -D_GNU_SOURCE -Wall -c -o menuselect_stub.o menuselect_stub.c make[2]: Entering directory `/usr/src/asterisk-1.8.3/menuselect/mxml' gcc -Os -g -Wall -c mxml-attr.c gcc -Os -g -Wall -c mxml-entity.c gcc -Os -g -Wall -c mxml-file.c gcc -Os -g -Wall -c mxml-index.c gcc -Os -g -Wall -c mxml-node.c gcc -Os -g -Wall -c mxml-search.c gcc -Os -g -Wall -c mxml-set.c gcc -Os -g -Wall -c mxml-private.c gcc -Os -g -Wall -c mxml-string.c /bin/rm -f libmxml.a /usr/bin/ar crvs libmxml.a mxml-attr.o mxml-entity.o mxml-file.o mxml-index.o mxml-node.o mxml-search.o mxml-set.o mxml-private.o mxml-string.o a - mxml-attr.o a - mxml-entity.o a - mxml-file.o a - mxml-index.o a - mxml-node.o a - mxml-search.o a - mxml-set.o a - mxml-private.o a - mxml-string.o ranlib libmxml.a make[2]: Leaving directory `/usr/src/asterisk-1.8.3/menuselect/mxml' gcc -o menuselect menuselect.o strcompat.o menuselect_stub.o mxml/libmxml.a ...and this might be even more relevant? checking for gcc... gcc checking whether the C compiler (gcc -pthread -I../..//include -I/usr/include/libxml2 -pipe -Wall -Wstrict-prototypes -Wmissing-prototypes -Wmissing-declarations -g3 -mtune=ultrasparc -mcpu=v8 -fomit-frame-pointer -O6) works ... yes checking whether the C compiler (gcc -pthread -I../..//include -I/usr/include/libxml2 -pipe -Wall -Wstrict-prototypes -Wmissing-prototypes -Wmissing-declarations -g3 -mtune=ultrasparc -mcpu=v8 -fomit-frame-pointer -O6) is a cross-compiler... no checking whether we are using GNU C... yes checking whether gcc accepts -g... yes checking how to run the C preprocessor... gcc -E checking for mawk... mawk checking host system type... sparc64-unknown-linux-gnu checking for a BSD compatible install... /usr/bin/install -c checking for ranlib... ranlib checking for ar... /usr/bin/ar checking for tgetent in -ltermcap... yes checking for termcap.h... yes checking for sys/cdefs.h... yes checking for vis.h... no checking for issetugid... no checking for fgetln... no checking for strvis... no checking for strunvis... no checking for strlcpy... no checking for strlcat... no HTH
Re: How to tell the compiler NOT to assume cpu provides atomic instructions
Hi Brian, On Mon, Mar 7, 2011 at 7:12 PM, brian m. carlson < sand...@crustytoothpaste.net> wrote: > On Mon, Mar 07, 2011 at 06:27:22PM -0500, RR wrote: > > astobj2.o: In function `ast_atomic_fetchadd_int': > > /usr/src/asterisk-1.8.3/include/asterisk/lock.h:589: undefined reference > to > > `__sync_fetch_and_add_4' > > /usr/src/asterisk-1.8.3/include/asterisk/lock.h:589: undefined reference > to > > `__sync_fetch_and_add_4' > > /usr/src/asterisk-1.8.3/include/asterisk/lock.h:589: undefined reference > to > > `__sync_fetch_and_add_4' > > /usr/src/asterisk-1.8.3/include/asterisk/lock.h:589: undefined reference > to > > `__sync_fetch_and_add_4' > > /usr/src/asterisk-1.8.3/include/asterisk/lock.h:589: undefined reference > to > > `__sync_fetch_and_add_4' > > astobj2.o:/usr/src/asterisk-1.8.3/include/asterisk/lock.h:589: more > > undefined references to `__sync_fetch_and_add_4' follow > > utils.o: In function `ast_atomic_dec_and_test': > > /usr/src/asterisk-1.8.3/include/asterisk/lock.h:635: undefined reference > to > > `__sync_sub_and_fetch_4' > > utils.o: In function `ast_atomic_fetchadd_int': > > /usr/src/asterisk-1.8.3/include/asterisk/lock.h:589: undefined reference > to > > `__sync_fetch_and_add_4' > > collect2: ld returned 1 exit status > > make[1]: *** [asterisk] Error 1 > > make: *** [main] Error 2 > > > > Credible people in the Asterisk list believe that it's because the > configure > > script is somehow determining that my CPU provides atomic instructions > but > > it fails to find it when it tries to link. Does anyone know what options > can > > be provided to the "configure" script via CFLAGS or CXXFLAGS etc to tell > > make/compiler about this or to fix this? > > Please provide the output of the compilation command line and the > linking command line. Also, please provide the output of gcc -v. I > have some conjectures as to what might be going on, but I'll need to do > some tests to see. Ok, so the output of gcc -v is: # gcc -v Using built-in specs. Target: sparc-linux-gnu Configured with: ../src/configure -v --with-pkgversion='Debian 4.4.5-8' --with-bugurl=file:///usr/share/doc/gcc-4.4/README.Bugs --enable-languages=c,c++,fortran,objc,obj-c++ --prefix=/usr --program-suffix=-4.4 --enable-shared --enable-multiarch --enable-linker-build-id --with-system-zlib --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --with-gxx-include-dir=/usr/include/c++/4.4 --libdir=/usr/lib --enable-nls --enable-clocale=gnu --enable-libstdcxx-debug --enable-objc-gc --enable-targets=all --with-long-double-128 --enable-checking=release --build=sparc-linux-gnu --host=sparc-linux-gnu --target=sparc-linux-gnu Thread model: posix gcc version 4.4.5 (Debian 4.4.5-8) umm sorry if this is a stupid question but I don't know what other output to provide other than what I provided above which was from the 'make' command. The beginning of that is: # make CC="cc" CXX="" LD="" AR="" RANLIB="" CFLAGS="" make -C menuselect CONFIGURE_SILENT="--silent" makeopts
How to tell the compiler NOT to assume cpu provides atomic instructions
Hello All, I'm trying to compile the latest Asterisk release 1.8.3 on a V240 Sparc running Debian Squeeze. However, during make, it crashes with the following: Generating embedded module rules ... [LD] abstract_jb.o acl.o alaw.o aoc.o app.o ast_expr2.o ast_expr2f.o asterisk.o astfd.o astmm.o astobj2.o audiohook.o autochan.o autoservice.o bridging.o callerid.o ccss.o cdr.o cel.o channel.o chanvars.o cli.o config.o data.o datastore.o db.o devicestate.o dial.o dns.o dnsmgr.o dsp.o enum.o event.o features.o file.o fixedjitterbuf.o frame.o framehook.o fskmodem.o global_datastores.o hashtab.o heap.o http.o image.o indications.o io.o jitterbuf.o loader.o lock.o logger.o manager.o md5.o netsock.o netsock2.o pbx.o plc.o poll.o privacy.o rtp_engine.o say.o sched.o security_events.o sha1.o slinfactory.o srv.o ssl.o stdtime/localtime.o strcompat.o strings.o stun.o syslog.o taskprocessor.o tcptls.o tdd.o term.o test.o threadstorage.o timing.o translate.o udptl.o ulaw.o utils.o version.o xml.o xmldoc.o editline/libedit.a db1-ast/libdb1.a -> asterisk astobj2.o: In function `ast_atomic_fetchadd_int': /usr/src/asterisk-1.8.3/include/asterisk/lock.h:589: undefined reference to `__sync_fetch_and_add_4' /usr/src/asterisk-1.8.3/include/asterisk/lock.h:589: undefined reference to `__sync_fetch_and_add_4' /usr/src/asterisk-1.8.3/include/asterisk/lock.h:589: undefined reference to `__sync_fetch_and_add_4' /usr/src/asterisk-1.8.3/include/asterisk/lock.h:589: undefined reference to `__sync_fetch_and_add_4' /usr/src/asterisk-1.8.3/include/asterisk/lock.h:589: undefined reference to `__sync_fetch_and_add_4' astobj2.o:/usr/src/asterisk-1.8.3/include/asterisk/lock.h:589: more undefined references to `__sync_fetch_and_add_4' follow utils.o: In function `ast_atomic_dec_and_test': /usr/src/asterisk-1.8.3/include/asterisk/lock.h:635: undefined reference to `__sync_sub_and_fetch_4' utils.o: In function `ast_atomic_fetchadd_int': /usr/src/asterisk-1.8.3/include/asterisk/lock.h:589: undefined reference to `__sync_fetch_and_add_4' collect2: ld returned 1 exit status make[1]: *** [asterisk] Error 1 make: *** [main] Error 2 Credible people in the Asterisk list believe that it's because the configure script is somehow determining that my CPU provides atomic instructions but it fails to find it when it tries to link. Does anyone know what options can be provided to the "configure" script via CFLAGS or CXXFLAGS etc to tell make/compiler about this or to fix this? Thanks so much \RR
Re: Installing Debian from NFS
On Thu, Feb 17, 2011 at 6:12 PM, Martin Habets < errandir_n...@mph.eclipse.co.uk> wrote: > > The way my boot server is setup is, that it has tftp, /etc/ethers and > > /etc/hosts files all setup. > > You'll also need either bootparamd or dhcpd set up. > I don't believe that's required by Debian. Bootparamd is required by Solaris for a jumpstart. Also, I have installed Debian previously over the network without a DHCPd running, purely using rarp and then assigning a manual IP address which is what I needed to assign to it anyway > > > I have the boot.img from Debian Lenny for sparc > > in /tftpboot and also have the hex and decimal/AF_INET format of the > > intended IP Address soft-linked to this boot.img in the /tftpboot > directory > > i.e. 0A01030B -> boot.img. > > I've go this as > C0A8000F.SUN4M -> sparcroot/boot/tftpboot.img > The debug log of the daemons above will tell you exactly whan name the SUN > machine is looking for. > This is specific to the machine architecture. Ultrasparc machines with the Sun4U architecture do not require an extension and can simply be installed with the filename as shown above > > I have tried: > > ok> boot net > > Should be enough to get thing started. > I hope it prints out that it's trying to in touch with a bootp server. > > yes, it does get the machine installed, and it IS currently up and running. The only problem is that I had to install it using the Internet as opposed to a local repo. It's ok for 1 machine but when I need to install a bunch of them, it'll be an unnecessary waste of our data download budget, which is why apt-cacher-ng seemed such a good solution, but I can't get it to compile on Solaris 8 on Sparc. Still waiting on Eduard to find the time to be able to play it himself to see if he can make it work in a VM or something :(
Configuring QLogic QLA4010c on Debian on Sparc
Hello All, So I have a QLA4010c on my V240 running Debian. Debian seems to have picked the existance of the adapter in the machine and pre-loaded some kernel modules already: # lsmod | grep -i qla qla4xxx58248 0 scsi_transport_iscsi34328 1 qla4xxx scsi_mod 167432 6 sd_mod,libata,sym53c8xx,qla4xxx,scsi_transport_spi,scsi_transport_iscsi But I need to setup an IP address and obviously other configuration for it to be able to see the LUNs/ Volume etc on the SAN it's connected to. On the QLogic website, there are only rpms available for the SANSurfer configuration utility. Or they have the .Z files for Solaris. Does anyone happen to have experience with configuring these bad boys on Debian? Any help/guiadance will be greatly appreciated :) Thanks so much. So far the Debian community has been stellar in helping out :) Cheers, \R
Re: Overwritten ALOM runtime image during Debian Net install - HELP :(
On Wed, Feb 2, 2011 at 10:08 PM, RR wrote: > > On Wed, Feb 2, 2011 at 5:55 PM, Richard Mortimer > wrote: > >> >> >> On 02/02/2011 17:55, RR wrote: >> >>> Hi All, >>> >>> We think we have ruined the image that comes with the SC or something >>> but we were trying to install Debian Linux on this V240. On the OBP we >>> typed >>> >>> /ok boot new linux root=/dev/nfs nfsroot=10.1.3.1:/mnt/iso >>> ip=10.1.3.11:10.1.3.1:10.1.3.254:255.255.255.0:SPARC01/ >>> >>> Try adding one of the following to your boot commandline. >> >> console=ttyS0,19200 >> or >> console=ttyS0,9600 >> or >> console=ttyS0,115200 >> > > Hi Richard. > Thanks for the response. The problem is we have no clue where to actually > type ANYTHING anymore as we never get to a point to be able to type > anything. Note that ALL of this garbage appears before we can even get into > the ALOM, so we're not even at the OBP to be able to give the machine any > instructions re: serial port settings etc. We believe that upgrading the > ALOM version could have been our salvation but even before this had > happened, we'd spent time looking for the newer ALOM version but Oracle has > now made all these things available ONLY to people with a support contract. > These used to be freely available through sunsolve before. We've created a > ticket in the Oracle support forums but no response so far :( > Richard, OMG!! You're a Genius!! So, we'd changed the Serial port settings at the OBP to 19,200 but had seen NO change to anything. Typically, a mismatch of console port settings, just makes the console non-responsive till you get the settings at both end (the PC console port OR a Serial/Console Server) the same. However, since we kept seeing the effect of key presses on the screen (even though it was all garbage) we thought the change didn't do anything. Anyhow, just to test your theory, we figured, OK, so we did change the ttysa settings a while ago, let us try and change the client side settings too again and see if that does anything and Voila!! We have clear text on the screen again!! OMG, we spent4-5 hrs on trying to figure this out!! Thank you thank you thank you! > > >> >>> /Loading the runtime image... ¡¼å!ØÖ/ >>> /½ç/ >>> /Gûb/ >>> >> This looks to me like the serial port settings that the kernel is using >> are wrong. I don't remember what speed the ALOM uses for the serial port but >> it is probably one of 19200, 9600 or 115200 as above. >> > > > > It uses 9,600 by default. But we'd tried changing it to 19,200 but it > didn't make any difference. > > > >> Its a long time since I used a V240 so you may have to play around to find >> the right settings. >> The settings are documented in Documentation/serial-console.txt in the >> Linux kernel sources. See >> >> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=blob;f=Documentation/serial-console.txt;h=9a7bc8b3f479b2b82dbfa1056df060366dbafdec;hb=HEAD >> >> Regards >> >> Richard >> > >
Re: Overwritten ALOM runtime image during Debian Net install - HELP :(
On Wed, Feb 2, 2011 at 5:55 PM, Richard Mortimer wrote: > > > On 02/02/2011 17:55, RR wrote: > >> Hi All, >> >> We think we have ruined the image that comes with the SC or something >> but we were trying to install Debian Linux on this V240. On the OBP we >> typed >> >> /ok boot new linux root=/dev/nfs nfsroot=10.1.3.1:/mnt/iso >> ip=10.1.3.11:10.1.3.1:10.1.3.254:255.255.255.0:SPARC01/ >> >> Try adding one of the following to your boot commandline. > > console=ttyS0,19200 > or > console=ttyS0,9600 > or > console=ttyS0,115200 > Hi Richard. Thanks for the response. The problem is we have no clue where to actually type ANYTHING anymore as we never get to a point to be able to type anything. Note that ALL of this garbage appears before we can even get into the ALOM, so we're not even at the OBP to be able to give the machine any instructions re: serial port settings etc. We believe that upgrading the ALOM version could have been our salvation but even before this had happened, we'd spent time looking for the newer ALOM version but Oracle has now made all these things available ONLY to people with a support contract. These used to be freely available through sunsolve before. We've created a ticket in the Oracle support forums but no response so far :( > >> /Loading the runtime image... ¡¼å!ØÖ/ >> /½ç/ >> /Gûb/ >> > This looks to me like the serial port settings that the kernel is using are > wrong. I don't remember what speed the ALOM uses for the serial port but it > is probably one of 19200, 9600 or 115200 as above. > It uses 9,600 by default. But we'd tried changing it to 19,200 but it didn't make any difference. > Its a long time since I used a V240 so you may have to play around to find > the right settings. > The settings are documented in Documentation/serial-console.txt in the > Linux kernel sources. See > > http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=blob;f=Documentation/serial-console.txt;h=9a7bc8b3f479b2b82dbfa1056df060366dbafdec;hb=HEAD > > Regards > > Richard >
Installing Debian from NFS
Hello, this may be a very obvious one of those things that I should just "Google" but given my last experience, and unsuccessful Googling, I figured maybe I should ask the community as to what the CORRECT way to install Debian on a Sun machine such that it uses the ISO/Distribution on my local NFS server as opposed to just picking up the boot.img and then have the rest of it be downloaded from the Internet. I have a LOT of SUN machines to install and it'd be cool if I can just install them off the distro on the nfs server. The way my boot server is setup is, that it has tftp, /etc/ethers and /etc/hosts files all setup. I have the boot.img from Debian Lenny for sparc in /tftpboot and also have the hex and decimal/AF_INET format of the intended IP Address soft-linked to this boot.img in the /tftpboot directory i.e. 0A01030B -> boot.img. I also have the entire debian-DVD-lenny.iso available and is mounted on /mnt/iso by way of lofiadm so that /mnt/iso has the contents of the ISO and not the bundled iso image. Now, how do I tell the installer to go pick it up from there? I have done a bit of research and all I see everywhere is mentions of some file called root.tar.gz and debian-installer and what not...but I can't figure out where do I get that from. I have tried: ok> boot net and ok> boot net - install nfsroot=10.1.3.1:/mnt/iso and ok> boot net install Any one wish to comment? Thanks so much \RR
Overwritten ALOM runtime image during Debian Net install - HELP :(
Hi All, We think we have ruined the image that comes with the SC or something but we were trying to install Debian Linux on this V240. On the OBP we typed *ok boot new linux root=/dev/nfs nfsroot=10.1.3.1:/mnt/iso ip=10.1.3.11:10 .1.3.1:10.1.3.254:255.255.255.0:SPARC01* Where: /mnt/iso is where we mounted the Debian ISO via lofiadm 10.1.3.11 is the IP we wanted to assign this machine etc. After it went through this, we got a lot of garbage on the screen. So we recycled power (Cold reboot) the machine and now this happens: *ALOM BOOTMON v1.5.1* *ALOM Build Release: 001* *Reset register: e000 EHRS ESRS LLRS* *ALOM POST 1.0* *Dual Port Memory Test, PASSED.* *TTY External - Internal Loopback Test* *TTY External - Internal Loopback Test, PASSED.* *TTYC - Internal Loopback Test* *TTYC - Internal Loopback Test, PASSED.* *TTYD - Internal Loopback Test* *TTYD - Internal Loopback Test, PASSED.* *Memory Data Lines Test* *Memory Data Lines Test, PASSED.* *Memory Address Lines Test* *Slide address bits to test open address lines* *Test for shorted address lines* *Memory Address Lines Test, PASSED.* *Memory Parity Test* *Memory Parity Test, PASSED.* *Boot Sector FLASH CRC Test* *Boot Sector FLASH CRC Test, PASSED.* *Return to Boot Monitor for Handshake* *ALOM POST 1.0* *Status = 7fff* *Returned from Boot Monitor and Handshake* *Clearing Memory Cells* *Memory Clean Complete* *Loading the runtime image... ¡¼å!ØÖ* *½ç* *Gûb* *î* *¢* *¼* *röÂC¬* *¥* *** *Ǿ* *¤D¦î* *($* *ؽ* *C0* *ÑbCÏÀ¤èÜäC8Á8* Please help! We're actually not physically at the server and it's sitting 10,000 miles away. We have access to remote power boot and a serial access into the machine however. Thank you in advance
Re: Missing Disk Space or Partition
> > Honestly, I'd rather just rebuild this machine, but I'm not there >> physically anymore and given the problems I had in installing Debian on >> that Sparc machine while I was actually there, if I have those again, >> when I'm now 8,000 miles away, that's going to be bad! On EVERY Sparc >> system that I have tried to install Debian on, I've had random issues >> and most of them have been fixed by removing/disconnecting physical >> hardware, the drivers of which could have been freezing up / crashing >> the system. Even the V100 I have in the lab here only worked after I >> disconnected the CD-ROM drive from the system. If I have that issue with >> one of the remote machines, I can't really conect/disconnect physical >> hardware being 8.000 miles away :( So I need to have a way to fix this >> manually if someone can help :( >> > Do you have the setup to net boot this system or boot from cdrom? I > wouldn't even attempt the sort of open heart surgery you are gonna need > without having an emergency boot fallback. Indeed rewriting the label would > be best done from a standalone system so that you can test it before > rebooting. > > Richard > I don't have a netboot setup there but that would take only about 15-20 mins to setup. That's not the worry though. The worry like I explained is that these Sparc machines have so far been a pain to cheerfully let me install Debian on them. In each case I've had to do somersaults and cartwheels of sorts mostly involving physically disconnecting hardware components, HBAs, CD-ROM drives etc for them to get through the Installs and subsequent reboots. So even if I setup a net boot setup there from here, how would I get past these hiccups if it freezes mid-way and needs some hardware to be disconnected etc? But i do have another machine here OR I could just create a VM and then try to see what happens if I re-create the disk label and then manually build the parition table. Was rather hoping someone can give me the steps / faq/ how-to / gotchas etc before I attempt that and try to pioneer it so I can save some time and anguish :)
Re: Missing Disk Space or Partition
On Mon, Jan 24, 2011 at 1:08 PM, Carl Johnson wrote: > RR writes: > > > On Mon, Jan 24, 2011 at 12:07 AM, Carl Johnson wrote: > > > >> RR writes: > >> > >> > I see as more messages are pouring in, this message is getting pushed > >> down > >> > further and people won't even see it anymore. Does anyone have a > personal > >> > doco, blog , cheatsheet for modifying the disk label (and then I'm > >> assuming > >> > I'll have to recreate my partition table) but not losing my data? I > have > >> > done this sort of stuff of destroying the partition table and > re-creating > >> it > >> > by hand before without losing the data but I'm just very unfamiliar > with > >> > this LVM beast and was wondering if someone could help at all? > >> > >> If it is just a lvm problem, then you should first try running pvs, vgs, > >> and lvs. Those will tell you what LVM thinks that it has. Also you > >> should run 'fdisk -l /dev/sda' (or whatever disks you have) to see what > >> partitions your system thinks it has. Man lvm should give you some > >> general information on the lvm commands, but you will probably need to > >> read the individual man pages for more detail on the commands. > >> > > Hello Carl, > > I've posted all of that in the past emails in this thread, however for > the > > benefit of new people seeing this message (esp. those not using gmail > with > > the conversation mode set on) here's the info again > > Sorry, I must have missed that before. > > > lvm> pvs > > PV VG Fmt Attr PSize PFree > > /dev/sda2 DebSparcx64-01 lvm2 a- 43.21G0 > > shows the main partition to be 43.21GB and if /dev/sda1 is boot and > > /dev/sda2 is the lvm volume and /dev/sda2 is the "whole disk", then > > how/where do I extend this volume to? > > > > # lvs > > LV VG Attr LSize Origin Snap% Move Log Copy% > Convert > > home DebSparcx64-01 -wi-ao 30.47G > > root DebSparcx64-01 -wi-ao 264.00M > > swap_1 DebSparcx64-01 -wi-ao 4.66G > > tmpDebSparcx64-01 -wi-ao 380.00M > > usrDebSparcx64-01 -wi-ao 4.66G > > varDebSparcx64-01 -wi-ao 2.79G > > > > # fdisk -l /dev/sda > > Disk /dev/sda (Sun disk label): 24 heads, 424 sectors, 8922 cylinders > > Units = cylinders of 10176 * 512 bytes > >Device FlagStart EndBlocks Id System > > /dev/sda1 019 966721 Boot > > /dev/sda219 8924 45308640 8e Linux LVM > > /dev/sda3 0 8924 454053125 Whole disk > > > > > > as per the above, /sda2 is extending from cylinder 19 to the last > cylinder > > but it's coming u to only 43.21GB? Where did the rest of it go? > > Everything looks entirely consistent, but it appears that your disk is > only about 45GB. > > sda = 24*424*8922 = 90790272 sectors (512 bytes) = 45395136KB = 43.29GB > sda2 = 24*424*8905 = 90617280 sectors = 45308640KB = about 43.21GB > > I do see a couple of thing that might cause problems other than that. > Using overlapping partitions could cause problems, but I am surprised > that is even allowed. You currently have sda3 which overlaps (contains) > both sda1 and sda2. It also appears that sda1 ends on cylinder 19, but > sda2 also starts on cylinder 19. If they are actually using partial > cylinders that might make sense, but I have never seen it before. I > also see that fdisk reports 8922 cylinders for the disk but assigns 8925 > cylinders (0-8924) to the partitions. > > So, in summary I don't see any missing disk space. If your disks are > actually 72GB it appears that you will have to tell fdisk what the > actual size is, but I would be very careful about doing that. If you > really can do that, then you can resize lvm (pvresize and lvresize) and > ext3 filesystems. If you make any mistakes on any of those you will > almost certainly have damaged filesystems and likely lost data. > Hi Carl, yes, it's all very weird and not sure how it's letting any other program even do this like overlapping cylinders and partial cylinders and what not. But rest assured, the disks are in fact 72G # dmesg | grep -i seagate [ 87.602318] scsi 0:0:0:0: Direct-Access SEAGATE ST373207LSUN72G 045A PQ: 0 ANSI: 3 [ 92.432095] scsi 0:0:1:0: Direct-Access SEAGATE ST373307LSUN72G 0707 PQ: 0 ANSI: 3 Now, from what I understand with these things, all of this could be a one big mess up of
Re: Missing Disk Space or Partition
On Fri, Jan 21, 2011 at 5:42 AM, Richard Mortimer wrote: > > > On 21/01/2011 10:31, RR wrote: > >> Please specify either size or extents but not both. >> even weirder is that when I try to see the physical parameters of >> the disk, which is clearly a 68.37GB. Further >> lvm> pvs >> PV VG Fmt Attr PSize PFree >> /dev/sda2 AUASTMRCP-01 lvm2 a- 43.21G0 >> shows the main partition to be 43.21GB and if /dev/sda1 is boot and >> /dev/sda2 is the lvm volume and /dev/sda2 is the "whole disk", then >> how/where do I extend this volume to? >> /# fdisk -l /dev/sda >> Disk /dev/sda (Sun disk label): 24 heads, 424 sectors, 8922 cylinders >> Units = cylinders of 10176 * 512 bytes >> > > Are you sure that it really is a 72G disk? The label above says 8922 > cylinders > and this translates to > > 8922 * 10176 * 512 = 46484619264 which is around 44GB and that matches > what your partitions are. > > If that is the case then your disk label is wrong. > > Regards > > Richard > > Hi Richard, yes, I am pretty sure, unless the firmware on the HDD is also reporting the wrong model. Here's the dmesg output of when the system detects the disks # dmesg | grep -i seagate [ 87.602318] scsi 0:0:0:0: Direct-Access SEAGATE ST373207LSUN72G 045A PQ: 0 ANSI: 3 [ 92.432095] scsi 0:0:1:0: Direct-Access SEAGATE ST373307LSUN72G 0707 PQ: 0 ANSI: 3 Thanks \RR
Re: Missing Disk Space or Partition
Hi Brian, Thanks for that. Yes, you're absolutely right, I used LVM in the hope that I will be able to control the size of the partitions. So, I kind of figured the same thing as you have suggested, but after having going through various LVM settings, I am stil confused as to how I can't find the remaining space when I had consciously created these partitions. When I get into LVM, I see the following: lvm> lvmdiskscan /dev/ram0 [ 16.00 MB] /dev/sda [ 68.37 GB] /dev/dm-0 [ 264.00 MB] /dev/ram1 [ 16.00 MB] /dev/sda1 [ 94.41 MB] /dev/dm-1 [4.66 GB] /dev/ram2 [ 16.00 MB] /dev/sda2 [ 43.21 GB] LVM physical volume /dev/dm-2 [2.79 GB] /dev/ram3 [ 16.00 MB] /dev/sda3 [ 43.30 GB] /dev/dm-3 [4.66 GB] /dev/ram4 [ 16.00 MB] /dev/dm-4 [ 380.00 MB] /dev/ram5 [ 16.00 MB] /dev/dm-5 [ 30.47 GB] /dev/ram6 [ 16.00 MB] /dev/ram7 [ 16.00 MB] /dev/ram8 [ 16.00 MB] /dev/ram9 [ 16.00 MB] /dev/ram10 [ 16.00 MB] /dev/ram11 [ 16.00 MB] /dev/ram12 [ 16.00 MB] /dev/ram13 [ 16.00 MB] /dev/ram14 [ 16.00 MB] /dev/ram15 [ 16.00 MB] /dev/sdb [ 68.37 GB] /dev/sdb1 [ 67.46 GB] /dev/sdb2 [ 914.25 MB] /dev/sdb3 [ 68.35 GB] and when I do an lvextend, I get this: lvm> lvextend Please specify either size or extents but not both. even weirder is that when I try to see the physical parameters of the disk, which is clearly a 68.37GB. Further lvm> pvs PV VG Fmt Attr PSize PFree /dev/sda2 AUASTMRCP-01 lvm2 a- 43.21G0 shows the main partition to be 43.21GB and if /dev/sda1 is boot and /dev/sda2 is the lvm volume and /dev/sda2 is the "whole disk", then how/where do I extend this volume to? /# fdisk -l /dev/sda Disk /dev/sda (Sun disk label): 24 heads, 424 sectors, 8922 cylinders Units = cylinders of 10176 * 512 bytes Device FlagStart EndBlocks Id System /dev/sda1 019 966721 Boot /dev/sda219 8924 45308640 8e Linux LVM /dev/sda3 0 8924 454053125 Whole disk as per the above, /sda2 is extending from cylinder 19 to the last cylinder but it's coming u to only 43.21GB? Where did the rest of it go? I swear I'm really not this bad with Linux/Unix admin stuff but this is really weird. Any ideas? Thanks so much in advance, RR On Thu, Jan 20, 2011 at 6:23 PM, brian m. carlson < sand...@crustytoothpaste.net> wrote: > On Thu, Jan 20, 2011 at 05:49:06PM -0500, RR wrote: > > /dev/mapper/DebSparcx64--01-root 256M 78M 166M 32% / > > tmpfs 2.0G 0 2.0G 0% /lib/init/rw > > udev 10M 1.1M 9.0M 11% /dev > > tmpfs 2.0G 0 2.0G 0% /dev/shm > > /dev/mapper/DebSparcx64--01-home 30G 177M 29G 1% /home > > /dev/mapper/DebSparcx64--01-tmp 368M 11M 339M 3% /tmp > > /dev/mapper/DebSparcx64--01-usr 4.6G 372M 4.0G 9% /usr > > /dev/mapper/DebSparcx64--01-var 2.8G 189M 2.5G 8% /var > > > > The question now is, if you look carefully, I only have ~37GB showing as > > partitioned. Where is the remaining (72-37 GB) space? This was easy to > see > > in 'format' command in Solaris but doing all sort of cart-wheels in > > Debian/Linux, I don't know what the heck these dm-* partitions are, which > > seem to be where this missing space is, and how do I get to it to create > a > > valid partition out of it and mount it and use it? > > Let me guess: you used LVM. If you did, you can use "vgdisplay -v > DebSparcx64-01" (more generically, "vgdisplay -v name-of-volume-group") > as root to see how much space is allocated and free. The dm-* devices > are device mapper devices; LVM uses device mapper, so one of those will > be created for each logical volume. > > To expand a logical volume (such as one of the /dev/mapper devices > listed above), use lvextend to increase the size of the logical volume, > and then use resize2fs to increase the size of the filesystem on that > device. If you are simply increasing the size (and not decreasing it), > you needn't provide a size to resize2fs; it will automatically determine > the correct size itself. If the filesystems have been created with a > recent enough version of e2fsprogs, you can perform the resizing online; > that is, while the filesystem is mounted and in use. > > -- > brian m. carlson / brian with sandals: Houston, Texas, US > +1 832 623 2791 | http://www.crustytoothpaste.net/~bmc | My opinion only > OpenPGP: RSA v4 4096b: 88AC E9B2 9196 305B A994 7552 F1BA 225C 0223 B187 >
Re: Disk Errors on 2nd Disk in Dual-Boot Debian/Solaris System
Hi Ivan, Thanks for your comments. Please see responses below On Thu, Jan 20, 2011 at 5:49 PM, Ivan Jager > wrote: > On Thu, Jan 20, 2011 at 05:03:40PM -0500, RR scribbled: > > On Thu, Jan 20, 2011 at 4:47 PM, brian m. carlson < > > sand...@crustytoothpaste.net> wrote: > > > You need to fix /etc/fstab so that your /boot partition is properly > > > referenced. Otherwise, when you upgrade your kernel, the data will be > > > written in the wrong place and you won't be able to use the new kernel. > > > If you can boot Debian, then your /etc/silo.conf probably contains the > > > correct location of your /boot partition, so you should use that. > > > > > Right, so that's what I figured as it's complaining about it not being an > > ext2 FS, which it obviously isn't, so we're ok there. > > No, you still need to fix that. > > > w.r.t to silo.conf, it's really bizarre. As per your instructions, once > In > > debian, I went into /etc and found the following: > > > > DebSparcx64:/etc# ls -l silo.conf > > lrwxrwxrwx 1 root root 17 2010-12-26 05:49 silo.conf -> ../boot/silo.conf > > > > But we already know that my /boot is empty. So where the hell is > silo.conf?? > > and when I mount my Solaris Disk i.e. /dev/sdb1 on to /mnt within Debian, > I > > still can't find either the bootloader for Debian OR silo.conf. I'm > really > > confused! > > Remember how you were having errors mounting /boot? Of course you > can't find things in /boot if it's not mounted. And why would you > be looking for it on the Solaris disk? Did you forget you swapped > the two disks? > I did, and I didn't, see comment below as to what I mean :( > > Now, remember how you said you swapped disk1 and disk2 "for > convenience"? I don't really see how it is more convenient if it > didn't work. If your /boot used to be /dev/sdb1 it would now be > /dev/sda1, so if you want to keep the disks in this configuration > you should probably update /etc/fstab to reflect that. > Alternately you could put the disks back in the order they were > when you installed the system. > > OMG Ivan, you're so smart!! (and I don't mean that sarcastically :) So I didn't forget that I swapped the disks when I was "talking" about it! But I did forget about it, since it didn't occur to me that sdb1 is now sda1 and when my fstab says, /dev/sdb1 /boot ext2defaults0 2 it REALLY is saying that it's on the disk which WAS Disk2 coz it's not auto-magiclaly gonna edit itself when I go swapping disks!!. So after your comment, I did this mount /dev/sda1 /bootand guess what??? DebSparcx64-01:/# cd /boot DebSparcx64-01:/boot# ls -ltr total 10192 -rw-r--r-- 1 root root 512 2008-08-24 19:26 ultra.b -rw-r--r-- 1 root root 71858 2008-08-24 19:26 silotftp.b -rw-r--r-- 1 root root7720 2008-08-24 19:26 isofs.b -rw-r--r-- 1 root root 692 2008-08-24 19:26 ieee32.b -rw-r--r-- 1 root root1024 2008-08-24 19:26 generic.b -rw-r--r-- 1 root root 512 2008-08-24 19:26 first.b -rw-r--r-- 1 root root1024 2008-08-24 19:26 fd.b -rw-r--r-- 1 root root 56992 2010-11-21 19:43 config-2.6.26-2-sparc64-smp -rw-r--r-- 1 root root 1807389 2010-11-21 22:05 vmlinuz-2.6.26-2-sparc64-smp -rw-r--r-- 1 root root 1137070 2010-11-21 22:05 System.map-2.6.26-2-sparc64-smp drwxr-xr-x 2 root root 12288 2010-12-26 05:13 lost+found lrwxrwxrwx 1 root root 28 2010-12-26 05:16 vmlinuz -> vmlinuz-2.6.26-2-sparc64-smp -rw-r--r-- 1 root root 7203342 2010-12-26 05:16 initrd.img-2.6.26-2-sparc64-smp lrwxrwxrwx 1 root root 31 2010-12-26 05:16 initrd.img -> initrd.img-2.6.26-2-sparc64-smp -rw-r--r-- 1 root root 193 2010-12-26 05:49 silo.conf -rw-r--r-- 1 root root 74240 2010-12-26 05:49 second.b -rw-r--r-- 1 root root7680 2010-12-26 05:49 old.b lrwxrwxrwx 1 root root 1 2010-12-26 05:49 etc -> . lrwxrwxrwx 1 root root 1 2010-12-26 05:49 boot -> . Champion!!! Ok, I will now edit fstab so it mounts /boot properly. I just don't understand how the system was booting up properly though. It must have something to do with the debian installer writing something at a level lower than the OS and Disk partitions??? > I don't know how Solaris will deal with it, but I wouldn't be too > suprised if you need to update something in your Solaris install > too. Have you tried booting it since you swapped the disks? > > Last of all, what is this "Debian x64" thing you installed? > haha, umm it's like the 64-bit Sparc port of Debian lenny: http://www.debian.org/ports/sparc/ Thank You SO Much!! Now if you could read the other posts and help me figure out the missing parition disk space that would be awesome :)
Missing Disk Space or Partition
Hello All, firstly, apologies for cross-posting! Please let me know if this is frowned upon and I will stop this behaviour :) Now, for those who've been following my adventures with Installing Debian Lenny 5.0.7 64-bit on a Sparc machine which already had Solaris 8 on one of the disks, I have additional observations and concerns. The disks in the machine are 72GB. However, after following the section regading Section 6.3.2, “Partitioning and Mount Point Selection”<http://www.debian.org/releases/stable/sparc/ch06s03.html.en#di-partition>, I observe the following during boot-up: Checking file systems...fsck 1.41.3 (12-Oct-2008) fsck.ext2: Bad magic number in super-block while trying to open /dev/sdb1 /dev/sdb1: The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock: e2fsck -b 8193 /dev/mapper/DebSparcx64--01-home: recovering journal /dev/mapper/DebSparcx64--01-home: clean, 16/1998848 files, 170528/7987200 blocks /dev/mapper/DebSparcx64--01-tmp: recovering journal /dev/mapper/DebSparcx64--01-tmp: clean, 13/97536 files, 22602/389120 blocks /dev/mapper/DebSparcx64--01-usr: recovering journal /dev/mapper/DebSparcx64--01-usr: clean, 15539/305216 files, 114625/1220608 blocks /dev/mapper/DebSparcx64--01-var: recovering journal /dev/mapper/DebSparcx64--01-var: clean, 1579/183264 files, 59952/732160 blocks fsck died with exit status 8 failed (code 8). File system check failed. A log is being saved in /var/log/fsck/checkfs if that location is writable. Please repair the file system manually. failed! A maintenance shell will now be started. CONTROL-D will terminate this shell and resume system boot. (warning). Give root password for maintenance DebSparcx64-01:~# exit exit Setting kernel variables (/etc/sysctl.conf)...done. Mounting lo[ 5608.111431] VFS: Can't find an ext2 filesystem on dev sdb1. cal filesystems...mount: wrong f[ 5608.213904] kjournald starting. Commit interval 5 seconds s type, bad opti[ 5608.309930] EXT3 FS on dm-5, on, bad superblointernal journal ck on /dev/sdb1,[ 5608.390272] EXT3-fs: mounted filesystem with ordered data mode. missing[ 5608.497014] kjournald starting. Commit interval 5 seconds codepage or hel[ 5608.579045] EXT3 FS on dm-4, per program, or internal journal other error [ 5608.664245] EXT3-fs: mounted filesystem with ordered data mode. In some cases useful info is[ 5608.781223] kjournald starting. Commit interval 5 seconds found in syslog[ 5608.873900] EXT3 FS on dm-1, - try dinternal journal mesg | tail or [ 5608.954854] EXT3-fs: mounted filesystem with ordered data mode. so [ 5609.082190] kjournald starting. Commit interval 5 seconds [ 5609.097021] EXT3 FS on dm-2, internal journal [ 5609.097032] EXT3-fs: mounted filesystem with ordered data mode. failed. Activating swapfile swap..[ 5609.323560] Adding 4886512k swap on /dev/mapper/DebSparcx64--01-swap_1. Priority:-1 extents:1 across:4886512k .done. Once the system gets to the login prompt and I login and run 'df -h', I see /dev/mapper/DebSparcx64--01-root 256M 78M 166M 32% / tmpfs 2.0G 0 2.0G 0% /lib/init/rw udev 10M 1.1M 9.0M 11% /dev tmpfs 2.0G 0 2.0G 0% /dev/shm /dev/mapper/DebSparcx64--01-home 30G 177M 29G 1% /home /dev/mapper/DebSparcx64--01-tmp 368M 11M 339M 3% /tmp /dev/mapper/DebSparcx64--01-usr 4.6G 372M 4.0G 9% /usr /dev/mapper/DebSparcx64--01-var 2.8G 189M 2.5G 8% /var The question now is, if you look carefully, I only have ~37GB showing as partitioned. Where is the remaining (72-37 GB) space? This was easy to see in 'format' command in Solaris but doing all sort of cart-wheels in Debian/Linux, I don't know what the heck these dm-* partitions are, which seem to be where this missing space is, and how do I get to it to create a valid partition out of it and mount it and use it? Thanks so much in advance, \RR
Re: Disk Errors on 2nd Disk in Dual-Boot Debian/Solaris System
Hi Brian, Thanks for your insights. Please see response below: On Thu, Jan 20, 2011 at 4:47 PM, brian m. carlson < sand...@crustytoothpaste.net> wrote: > On Thu, Jan 20, 2011 at 04:37:56PM -0500, RR wrote: > > During boot-up however, I see these errors: > > > > Checking file systems...fsck 1.41.3 (12-Oct-2008) > > fsck.ext2: Bad magic number in super-block while trying to open /dev/sdb1 > > /dev/sdb1: > > The superblock could not be read or does not describe a correct ext2 > > filesystem. If the device is valid and it really contains an ext2 > > filesystem (and not swap or ufs or something else), then the superblock > > is corrupt, and you might try running e2fsck with an alternate > superblock: > > e2fsck -b 8193 > > You'll get this message in one of a few cases: > > * the device in question (here /dev/sdb1) does not, in fact, contain an > ext2 filesystem (this is most likely); > * the device is encrypted and it was not decrypted properly (bad > password or such); > * something overwrote the beginning of the partition; or > * the system is in a really bad shape and the data is seriously > corrupted. > > Based on what you said in your earlier post (about /dev/sdb being your > Solaris disk), the first choice is likely correct. You probably need to > figure out where your /boot partition is located and update /etc/fstab. > > > This is obviously on the Disk with Solaris on it and that is NOT an ext3 > FS. > > Should I just ignore these errors? > > You need to fix /etc/fstab so that your /boot partition is properly > referenced. Otherwise, when you upgrade your kernel, the data will be > written in the wrong place and you won't be able to use the new kernel. > If you can boot Debian, then your /etc/silo.conf probably contains the > correct location of your /boot partition, so you should use that. > Right, so that's what I figured as it's complaining about it not being an ext2 FS, which it obviously isn't, so we're ok there. w.r.t to silo.conf, it's really bizarre. As per your instructions, once In debian, I went into /etc and found the following: DebSparcx64:/etc# ls -l silo.conf lrwxrwxrwx 1 root root 17 2010-12-26 05:49 silo.conf -> ../boot/silo.conf But we already know that my /boot is empty. So where the hell is silo.conf?? and when I mount my Solaris Disk i.e. /dev/sdb1 on to /mnt within Debian, I still can't find either the bootloader for Debian OR silo.conf. I'm really confused!
Disk Errors on 2nd Disk in Dual-Boot Debian/Solaris System
Hello All, I'm running Debian x64 on a Sparc based V240 Sun Server. The situation is the following: I had Solaris 8 Installed on this machine on Disk1. I then decided to try installing Debian x64 on the 2nd Disk following instructions I found in the FAQ or the Debian Comprehensive manual on the Debian Website. I was also able to successfully boot into Debian. And just for convenience sake, I exchanged the disk with debian on it with the disk with Solaris on it so Disk1 was now Disk2 and vice-versa. This happened about 3 weeks ago and I actually have really bad memory so I can't tell if I tried booting Solaris and was able to boot into it as well. So far, so good! During boot-up however, I see these errors: Checking file systems...fsck 1.41.3 (12-Oct-2008) fsck.ext2: Bad magic number in super-block while trying to open /dev/sdb1 /dev/sdb1: The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock: e2fsck -b 8193 /dev/mapper/DebSparcx64--01-home: recovering journal /dev/mapper/DebSparcx64--01-home: clean, 16/1998848 files, 170528/7987200 blocks /dev/mapper/DebSparcx64--01-tmp: recovering journal /dev/mapper/DebSparcx64--01-tmp: clean, 13/97536 files, 22602/389120 blocks /dev/mapper/DebSparcx64--01-usr: recovering journal /dev/mapper/DebSparcx64--01-usr: clean, 15539/305216 files, 114625/1220608 blocks /dev/mapper/DebSparcx64--01-var: recovering journal /dev/mapper/DebSparcx64--01-var: clean, 1579/183264 files, 59952/732160 blocks fsck died with exit status 8 failed (code 8). File system check failed. A log is being saved in /var/log/fsck/checkfs if that location is writable. Please repair the file system manually. failed! A maintenance shell will now be started. CONTROL-D will terminate this shell and resume system boot. (warning). Give root password for maintenance This is obviously on the Disk with Solaris on it and that is NOT an ext3 FS. Should I just ignore these errors? Thanks in advance, \RR
Re: Where is the BootLoader/Silo in a Dual-Boot Debian/Solaris System?
Hi Anatoly, On Thu, Jan 20, 2011 at 8:07 AM, Anatoly Pugachev wrote: > Hi! > > On Thu, Jan 20, 2011 at 10:40 AM, RR wrote: > > However, I have two questions: > > a) While doing a check on something, I realised that my /boot is empty. > > Could anyone help me understand this installation and tell me where does > > Silo/bootloader etc sit in this kind of a situation? > > > AFAIK, sparc bootloader is called silo, and it's configuration file > located under /etc/ : > http://packages.debian.org/lenny/sparc/silo/filelist > > /etc/silo.conf > > Thanks for that. Yes, I knew that but I have no idea where the actual bootloader is esp. in my configuration which is a messed up dual-boot configuration even though the bootloader may or may not be aware of it. I think since Silo is able to read / boot off of SunOS disks, the bootloader is still sitting on that partition but I don't know how to find it. I needed to check something in it but I don't need to touch it right now. I wonder though how this will work when I need to upgrade the kernel. The changes for that need to be written in the /boot directory and maybe in Silo.conf and if the upgrade will know where to find that Any more help would be appreciated. Thanks \RR
Where is the BootLoader/Silo in a Dual-Boot Debian/Solaris System?
Hello All, I take the liberty of welcoming myself to this mailing list that I joined a day or two ago and have taken the step to try out running Debian x64 on a Sparc based V240 Sun Server. The situation is the following: I had Solaris 8 Installed on this machine on Disk1. I then decided to try installing Debian x64 on the 2nd Disk following instructions I found in the FAQ or the Debian Comprehensive manual on the Debian Website. I was also able to successfully boot into Debian. This happened about 3 weeks ago and I actually have really bad memory so I can't tell if I tried booting Solaris and was able to boot into it as well. So far, so good! However, I have two questions: a) While doing a check on something, I realised that my /boot is empty. Could anyone help me understand this installation and tell me where does Silo/bootloader etc sit in this kind of a situation? When I do a df -h I get: /dev/mapper/DebSparcx64--01-root 256M 78M 166M 32% / tmpfs 2.0G 0 2.0G 0% /lib/init/rw udev 10M 1.1M 9.0M 11% /dev tmpfs 2.0G 0 2.0G 0% /dev/shm /dev/mapper/DebSparcx64--01-home 30G 177M 29G 1% /home /dev/mapper/DebSparcx64--01-tmp 368M 11M 339M 3% /tmp /dev/mapper/DebSparcx64--01-usr 4.6G 372M 4.0G 9% /usr /dev/mapper/DebSparcx64--01-var 2.8G 189M 2.5G 8% /var when I do a cat /etc/fstab, I see a line: /dev/sdb1 /boot ext2defaults0 2 However, I know that sdb is my Solaris Disk and when I try to mount it, it just gives me the whole Solaris / contents (that system is not partitioned at all and everything is on the / partition). How can I access the /boot for Debian if I want to modify/check something there? b) How can I make the system such that during bootup I see a menu which presents me a grub type menu so I can simply pick the OS I want to boot into? Thank you so much in advance \RR
