Re: [arch-general] Supermicro cd/dvd inst error: ARCH_201603 device did not show up after 30 seconds
On 09/20/2016 10:30 PM, Dave via arch-general wrote: > Did you check this? > > Installation problems: I/O erro: dev sr0 / Installation / Arch Linux Forums > https://bbs.archlinux.org/viewtopic.php?id=195763 > Thank you for the link, There is much discussion but little solution there. This seems like a bug that has plagued whoever it should go to for quite some time. I don't think this is a dao/tao issue. I get the same error with ARCH_201603 (which I've installed Arch from several times w/o issue) and ARCH 201609 and openSuSE 13.1. All cd's were md5/shasum verified (before and after burning), all burning was done from the command line per https://wiki.archlinux.org/index.php/Optical_disc_drive#Burning_an_ISO_image_to_CD.2C_DVD.2C_or_BD (the ARCH_201609 was to DVD since it finally exceeded the overburn of my discs). So the forum thread discusses in 43 posts at least a dozen theories as to why this continues to reoccur, but it doesn't seem that anybody actually has a handle as to the exact cause. Me, I've probably installed arch 30 times over the past 7 years and I've never seen this before. The post https://bbs.archlinux.org/viewtopic.php?pid=1608432#p1608432 probably captures the current thinking/experimentation as it stands now. I'll try and experiment with a couple of additional ATA and SATA based cd/dvd drives and if I find anything new I'll add this to the forum thread. If anyone has any additional thoughts on this, I (and apparently many others) would appreciate your thoughts. I can't believe my search didn't turn up that formum thread, (StartPage is usually dead on). However, I was surprised at the litany of different times and situations this has apparently occurred over the past year or so. Glad to know there is still a little mystery left in computing :) -- David C. Rankin, J.D.,P.E.
Re: [arch-general] Supermicro cd/dvd inst error: ARCH_201603 device did not show up after 30 seconds
Did you check this? Installation problems: I/O erro: dev sr0 / Installation / Arch Linux Forums https://bbs.archlinux.org/viewtopic.php?id=195763 On Tue, Sep 20, 2016 at 11:24 PM, David C. Rankin < drankina...@suddenlinkmail.com> wrote: > All, > > First let me explain I have search through the forums, StackExchange site > (SuperUser & Linux Unix StackExhange) and read the problems with similar > title, > 90% of which were USB install and related to failure to have the proper > iso name > (e.g ARCH_201603) as the image name, the other 10% were related to > /dev/disk/by-label not being created and suggest the creation of the > directory > and symlink of the install device (e.g. /dev/sr0 to > /dev/disk/by-label/ARCH_201603) and exiting the maintenance shell to have > the > install pickup and continue. Neither of these are a solution. > > I have one Supermicro server (similar but slightly older) where the > install > went without issue (H8QM8-2 w/4 Opteron 8360SE). This server is the > H8DME-2-LS006 Rev 1.10 w/2 Opteron 8382 processors. (specs: > http://www.supermicro.com/Aplus/motherboard/Opteron2000/MCP55/H8DME-2.cfm) > > Initially, the boot would hang during pci activation with the line > > pci 000:00:1a.0: [1a:1e:1100] type -- class 0x06 > > I reset the bios to the failsafe defaults, still no joy. > > The Hardware Detection Tool showed a 3Leaf Systems, Inc.|unknown device > at > that address, the details of which were: > > Vendor : 3Leaf Systems, Inc. > Product : unknown > Class: Host bridge > Location : 00:1a.0 > PCI ID : 1a1e:1100[:] > Latency : 0 > Module : unknown > > Looking though all the bios options, trying one at a time, I found an > option > for something related to AQUA (? This board an AQUA were apparently the > brainchild of 3Leaf, Inc. now out of business > http://www.eetimes.com/document.asp?doc_id=1172150 which allowed you to > link 32 > Opteron processors into a single server) > > So disabling AQUA completely in the bios allowed the box to boot > normally all > the way though: > > :: running hook [archiso_pxe_nfs] > :: Mounting '/dev/disk/by-label/ARCH_201603' to '/run/archiso/bootmnt' > Waiting 30 seconds for devices > > then the error and I'm dropped to the maintenance shell (e.g. [rootfs > /]# ). > I've tried the solutions shown at the beginning but I still can't proceed > with > the remainder of the install. When I create the /dev/disk/by-label > directory, > create the symlink, and exit the maintenance shell, I get the following > error: > > Buffer I/O error on dev sr0 logical block 0, async page read > sr 6:0:1:0 [sr0] tag#0 UNKNOWN(0x2003) Result:hostbyte-0x00 > driverbyte=0x08 > sr 6:0:1:0 [sr0] tag#0 Sense Key : 0x4 [current] > sr 6:0:1:0 [sr0] tag#0 ASC=0x8 ASCQ=0x3 > sr 6:0:1:0 [sr0] tag#0 CDB: opcode: 0x28 28 00 00 00 00 00 00 00 02 00 > blk_update_request: I/O error, dev sr0, sector 0 > isofs_fill_super: bread failed, dev=sr0, iso_blknum=16, block=16 > > So I need help from the smart folks here. I'm not entirely sure what this > error is telling me other than there is some UNKNOWN result that prevents > the > archiso mount. With this AQUA setting completely disabled in the bios, I > don't > know if this error is related to that setting, but I suspect it is. What > could I > try to get past this error? Is there some kernel parameter I coud try to > pass at > boot that might help? Has anyone else seen this or found another solution? > > Thanks for any advise you can give.. > > -- > David C. Rankin, J.D.,P.E. >
[arch-general] Supermicro cd/dvd inst error: ARCH_201603 device did not show up after 30 seconds
All, First let me explain I have search through the forums, StackExchange site (SuperUser & Linux Unix StackExhange) and read the problems with similar title, 90% of which were USB install and related to failure to have the proper iso name (e.g ARCH_201603) as the image name, the other 10% were related to /dev/disk/by-label not being created and suggest the creation of the directory and symlink of the install device (e.g. /dev/sr0 to /dev/disk/by-label/ARCH_201603) and exiting the maintenance shell to have the install pickup and continue. Neither of these are a solution. I have one Supermicro server (similar but slightly older) where the install went without issue (H8QM8-2 w/4 Opteron 8360SE). This server is the H8DME-2-LS006 Rev 1.10 w/2 Opteron 8382 processors. (specs: http://www.supermicro.com/Aplus/motherboard/Opteron2000/MCP55/H8DME-2.cfm) Initially, the boot would hang during pci activation with the line pci 000:00:1a.0: [1a:1e:1100] type -- class 0x06 I reset the bios to the failsafe defaults, still no joy. The Hardware Detection Tool showed a 3Leaf Systems, Inc.|unknown device at that address, the details of which were: Vendor : 3Leaf Systems, Inc. Product : unknown Class: Host bridge Location : 00:1a.0 PCI ID : 1a1e:1100[:] Latency : 0 Module : unknown Looking though all the bios options, trying one at a time, I found an option for something related to AQUA (? This board an AQUA were apparently the brainchild of 3Leaf, Inc. now out of business http://www.eetimes.com/document.asp?doc_id=1172150 which allowed you to link 32 Opteron processors into a single server) So disabling AQUA completely in the bios allowed the box to boot normally all the way though: :: running hook [archiso_pxe_nfs] :: Mounting '/dev/disk/by-label/ARCH_201603' to '/run/archiso/bootmnt' Waiting 30 seconds for devices then the error and I'm dropped to the maintenance shell (e.g. [rootfs /]# ). I've tried the solutions shown at the beginning but I still can't proceed with the remainder of the install. When I create the /dev/disk/by-label directory, create the symlink, and exit the maintenance shell, I get the following error: Buffer I/O error on dev sr0 logical block 0, async page read sr 6:0:1:0 [sr0] tag#0 UNKNOWN(0x2003) Result:hostbyte-0x00 driverbyte=0x08 sr 6:0:1:0 [sr0] tag#0 Sense Key : 0x4 [current] sr 6:0:1:0 [sr0] tag#0 ASC=0x8 ASCQ=0x3 sr 6:0:1:0 [sr0] tag#0 CDB: opcode: 0x28 28 00 00 00 00 00 00 00 02 00 blk_update_request: I/O error, dev sr0, sector 0 isofs_fill_super: bread failed, dev=sr0, iso_blknum=16, block=16 So I need help from the smart folks here. I'm not entirely sure what this error is telling me other than there is some UNKNOWN result that prevents the archiso mount. With this AQUA setting completely disabled in the bios, I don't know if this error is related to that setting, but I suspect it is. What could I try to get past this error? Is there some kernel parameter I coud try to pass at boot that might help? Has anyone else seen this or found another solution? Thanks for any advise you can give.. -- David C. Rankin, J.D.,P.E.
[arch-general] Error when starting Opera
Hi. Just installed Opera 40.0.2308.54-1. Upon starting Opera, a dialog box pops up saying: --- "Enter password to unlock you login keyring The password you use to log in to your computer no longer matches that of your login keyring." Password: < password input field >" - After about 5 seconds, a grey window pops up, saying: - "“Loading... - Opera” is not responding. You may choose to wait a short while for it to continue or force the application to quit entirely." ... followed by two buttons, "Force quit" and "Wait". Clicking "Force quit" exits Opera; clicking "Wait" simply makes the window go away, with Opera started as expected. --- Putting in my user password results in the message "The unlock password was incorrrect." If I click cancel, whether or not I enter a password, either way, Opera starts up, with no other (apparent) problem. Changing the user password, and even changing it back, does noting to change the login error message. I did a lengthy configuration of Opera, then re-started it. Same error. I re-installed Opera using pacman -Rsn. Same error. I cound not find any reference to this error in the forums, or any bug report. (Not saying it might not exist, it just did not see it.) This error does not occur for any other application program, including those that require entering a password for elevated privileges, to start. Any ideas?
Re: [arch-general] What happened to the Beginner's Guide?
On 20/09/16 at 01:58am, David C. Rankin wrote: On 09/20/2016 12:00 AM, D C via arch-general wrote: TBH, the main install guide looks almost identical to the beginner guide that I used about two years ago, check it out. We should consider the beginner's guide again -- it was invaluable to new and beginner users to help them get a feel for arch. Even for those versed in Linux, and with Arch, for the guys like me that do an install on a biennial basis, that guide was a savior. It was a major pain to maintain, among other things. It is far better to have a single, authoritative source for an Arch install than two, often divergent, guides. It requires less effort to maintain, reduces confusion about how to do a supported install, and encourages people to understand what they are doing, rather than hastily copy and pasting there way through an install so they can rush to tell people they are running Arch… Did no one want to maintain it? Why was the full beginner's guide deleted? https://wiki.archlinux.org/index.php?title=Talk:Beginners%27_guide=443725#Unification /J -- http://jasonwryan.com/ GPG: 7817 E3FF 578E EEE1 9F64 D40C 445E 52EA B1BD 4E40 signature.asc Description: PGP signature
Re: [arch-general] What happened to the Beginner's Guide?
On 09/20/2016 12:00 AM, D C via arch-general wrote: > TBH, the main install guide looks almost identical to the beginner guide > that I used about two years ago, check it out. I guess I've been using a different beginner's guide for the past 8 years. The installation guide that is currently on the wiki is about 1/10 the size and depth of the original beginners guide. I have fairly good notes on the steps, and my subset of notes alone is 3-4 times the length of the current "install" guide. The beginner's guide always provided an expanded section on each topic in the install where different cards and potential pitfalls were discussed. There was the varying network configuration options, netctl, etc., RAID setup was addressed, etc.. Now - nothing. We should consider the beginner's guide again -- it was invaluable to new and beginner users to help them get a feel for arch. Even for those versed in Linux, and with Arch, for the guys like me that do an install on a biennial basis, that guide was a savior. Did no one want to maintain it? Why was the full beginner's guide deleted? -- David C. Rankin, J.D.,P.E.
