How do I avoid the “S to Skip” message on boot?

1

How to avoid the “S to Skip” message on boot. This is most common question now a days, if you are an Ubuntu user. Let’s see a trick to play around it. it occurs, when your boot is waiting for the `/etc/fstab`. you can try add the following one to boot it.So that it looks like:

UUID=1234-5678 /osshare vfat utf8,auto,rw,user,nobootwait 0 0

From `fstab(5):`

The` mountall(8)` program that mounts file-system during boot also recognizes additional options that the ordinary `mount(8)` tool does not.

These are `bootwait` which can be applied to remote filesystems mounted outside of `/usr` or `/var`, without which `mountall(8)` would not hold up the boot for these `nobootwait`

Which can be applied to non-remote file-systems to explicitly instruct `mountall(8)` not to hold up the boot for...

0 0
2

I created a partition called /dev/sdb1 in my Ubuntu VM. But I didn’t create a filesystem for this partition and so of course it will not get mounted.

Then put following entry in fstab.

/dev/sdb1 /mnt/ auto defaults,nobootwait 0 2

And rebooted VM. Server got rebooted with following error msg in syslog

suku@ubuntu-vm:~$ grep sdb1 /var/log/syslog Jan 11 16:32:58 ubuntu-vm kernel: [ 2.263540] sdb: sdb1 Jan 11 16:32:59 ubuntu-vm kernel: [ 4.403527] EXT3-fs (sdb1): error: can't find ext3 filesystem on dev sdb1. Jan 11 16:32:59 ubuntu-vm kernel: [ 4.410341] EXT4-fs (sdb1): VFS: Can't find ext4 filesystem Jan 11 16:32:59 ubuntu-vm kernel: [ 4.413978] FAT-fs (sdb1): bogus number of reserved sectors Jan 11 16:32:59 ubuntu-vm kernel: [ 4.414073] FAT-fs (sdb1): Can't find a valid FAT filesystem

What is nobootwait:

nobootwait can be applied to non-remote filesystems to explicitly instruct mountall(8) not to hold up the boot for...

0 0
3
Mint 14 Nadia with Gala and Slingshot, and without Cinnamon

location: ubuntuforums.com - date: December 4, 2012
Yesterday, I wrote about Mint 14 becoming, Mint Elementary, but the thread had been moved to "December screenshots." http://ubuntuforums.org/showthread.p...2#post12386212 I thought the photos would say more than words, so the screenshots. I had made SolusOS 2 Alpha, a Debian distro to take in Ubuntu ppas and work with Gala and old Slingshot. I like SolusOSvery much, and that's why I did that. This time, I took Mint 14 and made it work with Gala and new Slingshot of eOS and while still working in "Cinnamon session" work without Cinnamon. I am not very keen on Mint. Now, it is nothing, but Cinnamon and Mate. The engine is Ubuntu Quantal. It is a simple Ubuntu based distro. So, this Mint 14 is not Cinnamon, not Mate, but Elementarished Mint. And, if I drop all the Mint applications, it becomes another Ubuntu-Elementary distribution. If I install all the new applications...

0 0
4

After upgrading my laptop from karmic to lucid, my fat32 partition won't mount automatically. I get the message:

The disk drive for /osshare is not ready yet or not present Continue to wait; or Press S to skip mounting or M for manual recovery

Funny thing is, if I skip, then /osshare/ is mounted once I log in.

I've a similar setup on my desktop, and it works fine. Fstab on desktop:

UUID=4663-6853 /osshare vfat utf8,umask=007,gid=46 0 1

/etc/fstab on laptop:

UUID=1234-5678 /osshare vfat utf8,auto,rw,user 0 0

You should add the option nobootwait to your /etc/fstab. So that it looks like:

UUID=1234-5678 /osshare vfat utf8,auto,rw,user,nobootwait 0 0

From fstab(5):

The mountall(8) program that mounts filesystem during boot also recognises additional options that the ordinary mount(8) tool does not. These are: bootwait which can be applied to remote filesystems mounted outside of /usr or /var, without which mountall(8) would not...

0 0
5

How to fix Press S to Skip Mount message on boot, The disk drive for /sharedevice or uuid=…. is not ready yet or not present, Continue to wait; or Press S to skip mounting or M for manual recovery

by: Revengksky Joseph D. Reyes (a.k.a rjdreyes – jcyberinux.com)

(Note: For this event you may need an internet connection, in case of need to install or download available updates on your Ubuntu OS.)

When you tried to Mount certain drive and for some reason, after you reboot or restart your computer, then at the Ubuntu Boot you see an error message like Press S to Skip Mount message or so on… It happens on the certain condition on the mount and unmount certain drive. To able to fix this follow the certain steps below:

(Note: For GNOME GUI, I’m not certain on other GUI Environment such as Unity, :D, you may try if you want, to see the results.)

Here’s the Steps / Instructions on How to fix Press S to Skip Mount message on boot, The disk drive for...

0 0
6

After following the steps in my XBMC Live Drives Mounted as Odd IDs article, wherein the user modifies the label of the drive and sets it to be recognized as part of the fstab process, I found myself occasionally seeing the message that indicates that Ubuntu can't find the drive. I found it frustrating that I would occasionally reboot my XBMC setup and the Seagate USB harddrives would have issues until I power cycled them.

With a bit of quick research, I found that there is an option as part of the fstab setup called nobootwait which lets the operating system continue to boot up even if the drive isn't present. In order to add this option, take the following steps.

Open the fstab file in your favorite editor:

sudo nano /etc/fstab

Modify the line for your hard drive to add the nobootwait parameter:

UUID=1234-5678 /media/SeagateHDD ntfs-3g defaults,umask=002,gid=users,nobootwait 0 0

That's all it should take. Next time you reboot, the...

0 0
7

On 512B versus 4K (Advanced Format, AF) sectors

More technically

More practically

On Hard drive size barriers

In the past, there were some hardware constrains, related to addressing.

Initiall BIOS CHS and int13 stuff -- 99% irrelevant these days since you won't have a motherboard that old.


The one that you may still run into today is the 2.2TB limit.

This one is largely a software limit, due to 32-bit LBA - 232 times 512-byte sectors is 2.2TB.

Keep in mind that in some cases, the it's only the BIOS that won't understand the disk, showing it as a smaller size), but the OS driver actually talk to the controller properly.

So if it does show properly in the OS, (and preferably you're not booting off it - that can be troublesome) you're likely fine.

If it does not show properly in the OS, it will typically show up as its real size modulo 2.2TB, e.g. 3TB as 0.8TB (3TB - 2.2TB), 6TB as 1.6TB (6TB - 4.4TB)....

0 0
8
...
0 0
9

"Disks" is just a buggy mess. It may get fixed eventually but ......

The biggest culprit are all these whoopidy do da udisks2 options: x-gvfs-show and x-gvfs-name. Actually there are a whole family of these daffy things like x-gvfs-hide, x-gvfs-icon, x-gvfs-symbolic-icon, etc....

All of them are designed to do something that was never intended so they cause issues. You could have probably fixed your situation simply by removing them but I figured the best way was to go back to the Jedi way of mounting partitions:

UUID=7298E5FE98E5C0A9 /mnt/WinXP ntfs defaults,nls=utf8,umask=000,uid=1000,windows_names 0 0

*** UUID specifies the partition and /dev/disk/by-uuid is the long form of the same thing. Either one will work.
*** /mnt/7298E5FE98E5C0A9 isn't very helpfull so I just gave it a name you can easily identify: /mnt/WinXP
*** I specified the filesystem ( ntfs ) rather than using "auto". Why expend system resources to have it figure it out...

0 0
10

I have two spring-boot applications. in receiver-application's Application.java I have:

@Bean public JmsListenerContainerFactory myFactory(ConnectionFactory connectionFactory, DefaultJmsListenerContainerFactoryConfigurer configurer) { DefaultJmsListenerContainerFactory factory = new DefaultJmsListenerContainerFactory(); configurer.configure(factory, connectionFactory); return factory; }

and in Receiver.java ...

@JmsListener(destination = "myQueue", containerFactory = "myFactory") public void receiveMessage(String tradeString) throws JSONException, IOException { tradeImpl = new ObjectMapper().readValue(tradeString, TradeImpl.class); }

In sender-application I simply use:

public void send(trade) { String queueName = "myQueue"; String tradeString = new ObjectMapper().writeValueAsString(trade); jmsTemplate.convertAndSend(queueName, tradeString); }

So I'm just sending the message to the queue name specified in receiver-application. I get the following in...

0 0
11

Hi, first sorry for my poor english.

My original configuration of my server have a set of two 40 gigs ide hard disks mounted on a promise Raid (Mirror mode), with Windows 2000 server installed on it. The system is very stable, and works without problems since a couple of years.

I want to upgrade my hard disks because I run in low disk space. I just buyed two identical 120 gigs hard disks to replace my two 40 gigs. I stopped my server and replaced one of my 40 gigs with a 120 gigs, and rebuilt my array without any error. After the successful message, I stopped my server again, and replaced my second 40 gigs with my second and unused 120 gigs drive, and rebuilt my array again to make a mirror of my first 120 gigs drive. After the successful message, I rebooted my server. Windows 2000 starts to load and suddenly - bang! A blue screen with the mention "***STOP 0x0000007B
INACCESSIBLE_BOOT_DEVICE...

I also tried a recent version of symantec Ghost...

0 0
12
//

OK, so CHKDSK ran when my machine rebooted, and displayed some stuff. Problem is I have no idea what it displayed, since it then proceeded to

rebootA reboot is the process of shutting down all running software on a machine, including the operating system itself, and then immediately reloading as if the machine had just been powered on.

A reboot differs from actually powering down the machine and turning it back on only in that the power is never turned off. The software simply acts as if the computer was shutting down completely, and then immediately acts as if it had just been powered on.

Reboots are common debugging and system-stabilization techniques, as they force the entire system back to a known initial state. (A power-off shutdown also includes resetting the hardware to a known initial state as well.) More information: Why do so many tech support solutions start with “reboot” or “turn it off”?">reboot

the machine when it was done. How do I get...

0 0